Product Document OpenMobility SIP Installation, Administration and Maintenance Document ID: pm-0504 Aastra DeTeWe Zeughofstr. 1 10997 Berlin, Germany 2006 - All Rights Reserved No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval system, for any purpose without the express written permission of Winfinity. Aastra DeTeWe Doc-ID: pm-0504 30.11.
OpenMobility SIP Installation, Administration and Maintenance History Version Reason / Version Date Author 1/0 Initial release. 30.11.2006 H. Zander 1/2 Draft removed 30.11.2006 Tielmann Additional Information: Tool: Print Date: Aastra DeTeWe Microsoft Office 2000 SP3 30.11.2006 Doc-ID: pm-0504 28.11.
OpenMobility SIP Installation, Administration and Maintenance Table of contents 1 OVERVIEW ....................................................................................................................................................... 5 1.1 PURPOSE .................................................................................................................................................... 5 1.2 ABBREVIATIONS AND DEFINITIONS ....................................................................
OpenMobility SIP Installation, Administration and Maintenance 4.4.2 4.4.3 4.4.4 4.4.5 Aastra Phone 142 auto call test mode........................................................................................ 41 Aastra Phone 142 auto answer test mode .................................................................................. 41 Syslog........................................................................................................................................ 41 Telnet user shell ........
OpenMobility SIP Installation, Administration and Maintenance 1 Overview 1.1 Purpose This document describes the service interfaces of the OpenMobility Manager. In this version only the DECT relevant service issues are described. 1.2 Abbreviations and definitions 1.2.
OpenMobility SIP Installation, Administration and Maintenance • • • • GAP Handover time slots each) Doubling the number of time slots (to 24) using the TDMA process Net data rate per channel of 32 kbps (for voice transmission using ADPCM) Voice coding using the ADPCM method Maximum transmission power of 10 mW Generic Access Profile • GAP is the abbreviation for Generic Access Profile • The GAP standard (ETS 300 444) is based on the same technology as DECT, but is limited to the most important basic fe
OpenMobility SIP Installation, Administration and Maintenance to determine which RFP is best received. The one that can be best received is defined as the active RFP. To prevent the PP from rapidly switching back and forth between two RFPs that can be almost equally well received, certain threshold values are in effect. (similar to a Schmitt trigger circuit) 1.
OpenMobility SIP Installation, Administration and Maintenance 2 Introduction 2.1 About the IP DECT wireless solution The DECT over IP system comprises the following components: • DECT Radio Fixed Parts (RFP) being distributed over an IP network and offering DECT as a wireless interface. • Media server / media gateway as telephony system platforms (e.g. Asterisk). • Portable Parts (PP): Aastra Phone 142.
OpenMobility SIP Installation, Administration and Maintenance 2.2 About the RFPs In general all RFPs have the same hardware and software capabilities. But please mind the differences in regulatory domains which exist for North America and all other areas of the world . These domains lead to different RFP variants which use specific frequency bands and field strengths: • • RFP 32 IP or RFP 34 IP (EMEA) - Frequency Band 1.880 to 1.
OpenMobility SIP Installation, Administration and Maintenance RFP only mode Within this mode the RFP converts IP protocol to DECT protocol and then transmits the traffic to and from the handsets over a DECT time slot. On air the RFP has 12 available time slots, 8 can have associated DSP resources for media streams, the remaining 4 time slots are used for e.g. control signalling between RFPs and the PPs. Groups of RFPs have to be built which are named clusters.
OpenMobility SIP Installation, Administration and Maintenance 2.3 OpenMobility Manager The OpenMobility Manager (OMM) performs the following tasks: • Signalling gateway (SIP <-> DECT). • Media stream management. • Managing sync-over-air functions between RFPs. • Facilitating system configuration modifications. The OpenMobility Manager (OMM) may run on one of the RFPs or on a dedicated Linux server. 2.
OpenMobility SIP Installation, Administration and Maintenance Media Server Media Gateway OMM (RFP in OMM mode) Signalling RFP Control Interface RTP/RTCP A call from one PP to another that resides on the same RFP will loop back within the RFP, if no media gateway is involved. So the call will not pass through to the Local Area Network (LAN). Although the voice packets will not impact LAN traffic, signal packets will.
OpenMobility SIP Installation, Administration and Maintenance If the PP user is moving, the PP detects that another RFP has a better signal strength and, therefore, it starts the handover process. The media stream from the IP phone cannot move to the secondary RFP, so the primary RFP uses the LAN to direct the voice to the secondary RFP, as shown in the following figure.
OpenMobility SIP Installation, Administration and Maintenance 2.5 RFP Synchronization To guarantee a seamless handover if a caller moves from one RFP zone of coverage to another RFP zone of coverage, an accurate synchronization of the RFPs is necessary. The RFPs are synchronized over the air interface. During start up one RFP will be the first, which transmits a signal on the air. The other RFPs only receive the signal until their are synchronous.
OpenMobility SIP Installation, Administration and Maintenance Unreliable Installation R 101 R 102 R 103 R 104 R 105 Don‘t R 111 R 110 R 109 R 108 R 107 R 106 Reliable Installation R 101 R 111 R 110 R 102 R 103 R 104 R 109 R 108 R 107 R 105 R 106 The sync-over-air solution is very reliable, because all existing redundant paths are used for synchronization. Thus, hardware tolerances have only very little influence. No RFP has a key position.
OpenMobility SIP Installation, Administration and Maintenance 2.7 About the Portable Parts Please mind the differences in regulatory domains which exist for North America and all other areas of the world . These domains lead to different PP variants which use specific frequency bands and field strengths: • • Aastra Phone 142 (EMEA) - Frequency Band 1.880 to 1.900 Mhz - 120 duplex channels - 10 mW (average output per active channel) Aastra Phone 142 US (NA) - Frequency Band 1.920 to 1.
OpenMobility SIP Installation, Administration and Maintenance An IP DECT system is operational, if it is set up with a license and the RFPs, which are encoded in the license are part of the system so that the OMM can communicate with these License RFPs. Depending on the size of the IP DECT system, it will still work if some License RFPs are out of service.
OpenMobility SIP Installation, Administration and Maintenance 2.9 System capacities There is only one OpenMobility Manager (OMM) in the system. The OMM capacities are: • Up to 256 RFPs can be controlled. • Up to 512 PPs are handled. It is possible to deactivate the DECT part of a RFP. If the DECT interface is deactivated then the resources (CPU and memory) are available for the OMM only. Aastra DeTeWe Doc-ID: pm-0504 28.11.
OpenMobility SIP Installation, Administration and Maintenance 3 Installation and configuration To establish and maintain an IP DECT installation, a network infrastructure is assumed, which comprises at least the following components: • • • RFPs PPs media server (e.g. Asterisk) The following services should be provided: • • • TFTP DHCP Syslog daemon 3.1 OpenMobility start up 3.1.
OpenMobility SIP Installation, Administration and Maintenance are available or if they are disabled it starts a DHCP client to determine the IP address of the ADMM and other startup settings. 3.1.2 Start up of the OpenMobility Manager There is no difference in booting that RFP, which is chosen to be running in OMM mode from those which are in the RFP only mode. The decision is driven by the OMM IP address, which is read • within the local network settings, if active. • via DHCP request.
OpenMobility SIP Installation, Administration and Maintenance 3.1.3.1.2 DHCP offer The DHCP client selects the DHCP server according to the following rules: • the public options (code 224) has a value equal to the string “OpenMobility”. or • the file field in the DHCP message has a sub string equal to “ip_rfp.cnt”. If none of the two rules above match the DHCP offer is ignored. Information retrieved from the DHCP offer: • The IP address to use is taken from the yiaddr field in the DHCP message.
OpenMobility SIP Installation, Administration and Maintenance code 1 Subnet mask yes code 3 Default Gateway yes code 6 Domain Name Server no code 15 Domain Name no code 42 IP-Address of a NTP server no code 43 Vendor Specific Options yes public option 224 Must set to "OpenMobility".
OpenMobility SIP Installation, Administration and Maintenance The update of booters with a major release number change will be performed automatically when the DHCP client in the application receives an DHCP offer with the public option 254 with a value “UPDATE”. 3.1.4.2 Selecting the right DHCP server The DHCP client requests its own IP address using code 50. The DHCP client will select the DHCP server that offers the currently used IP address.
OpenMobility SIP Installation, Administration and Maintenance 3.1.6 State LED state Remarks Application (init) Green flashing (2 sec on, 0.5 sec off) The DECT part of the RFP does not work (either not configured or not synchronized with other RFP’s) Application (init) Green RFP is up and running State graph of the start up phases LED RED ON Start-up wait for link up BOOTER LED red flashing 0,5 Hz LED red flashing 0,25 Hz retry DHCP no answer / offer not o.k.
OpenMobility SIP Installation, Administration and Maintenance 3.2 Static local configuration of the IP DECT Base Station For a static local configuration you must use the java configuration tool OpenMobility Configurator (requires Java Runtime Environment version 1.4 or higher). The settings, which are configured on the IP DECT Base Station with the tool OM Configurator, will be saved permanently in the internal flash memory of an IP DECT Base Station.
OpenMobility SIP Installation, Administration and Maintenance If you want to read the configuration parameters from an IP DECT Base Station set the MAC address and the IP address additionally and press the “List configuration” button. All parameters will be listed in the OM Configurator tool. Press the “Reset configuration" button to clean all input fields and additional parameters. 3.3 Configuring the OpenMobility Manager The OMM can be configured via HTTP.
OpenMobility SIP Installation, Administration and Maintenance After login there are the following options available: Configuration of general IP DECT system parameters. Administration of the attached RFPs. Administration of the PPs. Administration of the licence options. If no user action takes place the OMM logs out the user after 5 minutes. To logout from the system click at “Logout”.
OpenMobility SIP Installation, Administration and Maintenance 3.3.2 Licensing Within the initial configuration of the IP DECT system, the license is missing and a warning occurs. 3.3.2.1 Definition of the License RFPs' The License RFPs' have to be defined in that manner as described in chapter 2.8. Press the “New” button and add the MAC addresses of the License RFPs': If that has been done please wait for the green tick(s) as shown in the next image. Aastra DeTeWe Doc-ID: pm-0504 28.11.
OpenMobility SIP Installation, Administration and Maintenance 3.3.2.2 Get and add the licence key and PARK number The second step is to go to the Aastra - DeTeWe License web site and enter the serial number generated by the first step along with a TAN from your documentation. This will generate a license key that has to be entered in the 3rd step. If the license is valid, the warning “Missing License” disappears and the OMM restarts. 3.3.3 System 3.3.3.
OpenMobility SIP Installation, Administration and Maintenance If SNTP is not used, date and time can be configured at the OMM. This has to be done to provide date and time to the Aastra Phone 142. The time zone, which is shown on this web page, has been configured at the IP region section of the web service. Please note, that in the case that SNTP is not used, the date and time has to be configured after every restart of the IP DECT Base Station, where the OpenMobility Manager is running.
OpenMobility SIP Installation, Administration and Maintenance 3.3.3.1.2 Encryption Encryption is only available if RFP32/34 IP (not RFP 31/33 IP) are used. Therefore it can only be enabled on the “System Settings” web page if no RFP31/33 IP has been connected to the OMM. If encryption is enabled and an RFP31/33 IP connects to the OMM, its DECT air interface will not be activated. The user always has the possibility to disable encryption. In this case all connected RFP31/33 IP are restarted.
OpenMobility SIP Installation, Administration and Maintenance • Explicit MWI Subscription Some Media Server such as the Asterisk support Message Waiting Indication (MWI) based on /15/. A MWI icon will be presented on a Aastra Phone 142 if the user has received a voice message on his voice box which is supported by the Media Server. If Explicit MWI Subscription is enabled the OMM sends explicit for each PP a MWI Subscription message to the Proxy or Outbound Proxy Server.
OpenMobility SIP Installation, Administration and Maintenance 3.3.3.3 User account After initial installation or after removing the configuration file the OpenMobility service is accessible via a build-in user account with user “omm” and password “omm”. These settings which are case sensitive can be changed on the “User Account” web page. 3.3.3.4 Time zones A time and date resynchronization of the Aastra Phone 142 devices is described in chapter 3.3.3.1.
OpenMobility SIP Installation, Administration and Maintenance 3.3.3.5 Backup The web service interface allows to save a copy of the current configuration on the local host (host where the browser application is executed) as well as to restore an older configuration. Aastra DeTeWe Doc-ID: pm-0504 28.11.
OpenMobility SIP Installation, Administration and Maintenance Restoring a previously saved configuration will lead to a reset of the OMM to take effect. 3.3.4 RFP configuration All configured RFPs are listed in tables grouped to clusters by its topographic relations. The RFPs are sorted by their Ethernet addresses. To ensure correct handover of a PP during a call, all involved RFPs must deliver the same clock signal to the PP.
OpenMobility SIP Installation, Administration and Maintenance 3.3.4.1 DECT configuration The DECT functionality for each RFP can be switched on/off. If DECT is active the RFP can be added to a cluster. 3.3.4.2 States of a RFP For each RFP the state of the DECT subsystem is displayed. The states are: Synchronous The RFP is up and running. The RFP recognizes and is recognized by other RFPs in its cluster through its air interface and delivers a synchronous clock signal to the PPs.
OpenMobility SIP Installation, Administration and Maintenance 3.3.5 Configuration of Portable Parts At the Portable Parts web page all configured DECT handsets are sorted by their number. To keep the list concise, the complete list is split up into sub lists containing up to 100 handsets. The user can move back and forth in steps of 100 handsets.
OpenMobility SIP Installation, Administration and Maintenance Note: The authentication code can only be changed if the PP is not subscribed. The PP name can be changed, but this will not take effect until the PP is subscribed again. Deleting of a PP can be done by pressing the trash can icon . A popup window appears and asks for confirmation. After adding a PP to the OMM the PP must be subscribed. This is done by pressing the “Subscribe” button.
OpenMobility SIP Installation, Administration and Maintenance 4 Maintenance 4.1 Booter The booter may be handled via the DHCP option 254 “UPDATE” (see chapter 3.1.4.1) automatically. In any case you may have direct control to the booter SW, if you use a telnet user session. A complete description of the usage of the user shell, you can find in /18/. 4.1.1 Checking the RFP booter version You can display the version information of the RFP booter using the telnet interface of an RFP.
OpenMobility SIP Installation, Administration and Maintenance • • • 4.3 Two reference PPs with chargers. Battery chargers. A measuring handset, which can monitor other makers DECT radio sources. Checking the Aastra Phone 142 firmware version You can display the version information of the Aastra Phone 142 with a few keystrokes. Check the firmware version to determine whether an update is required to overcome any user issues. 1. Press the “Menu” soft key 2. Select “System” (only to highlight) 3.
OpenMobility SIP Installation, Administration and Maintenance upper right side refers to the PARK 1F-10-F2-21 of the IP DECT system and to the RFP to which the phone is currently connected to. 4.4.2 Aastra Phone 142 auto call test mode You can set the Aastra Phone 142 to “auto call test mode” with a few keystrokes. In this mode the phone will call a specified number cyclically. You can use this feature to generate traffic for test purposes. This mode is also active if the phone is an the charger.
OpenMobility SIP Installation, Administration and Maintenance • DHCP using the public options 227 and 228. • Setting the syslog daemon server and port via the web interface. To set up the syslog via DHCP or OM Configurator has the advantage, that syslogs are available in earlier states of the RFP start up. The level of syslog messages in the default state allows the user, to have control over the general system state and major failures.
OpenMobility SIP Installation, Administration and Maintenance 4.4.5 Telnet user shell Each RFP (OMM included) offers a lot of commands within the telnet shell. Most of them are useful for diagnostics and may help experts to resolve failures. Note: Some commands can harm the systems operation. 4.4.5.1 Login The procedure is: • • Open a telnet session to the RFP. Enter user “iprfp” and password “ommsip/987”. Welcome to IP RFP OpenMobility SIP Version x.y.
OpenMobility SIP Installation, Administration and Maintenance 4.4.5.
OpenMobility SIP Installation, Administration and Maintenance 4.4.6 DECT monitor of the OpenMobility system For a better error detection in the OpenMobility system the DECT monitor can be used. The DECT monitor is an MS Windows based standalone application. It provides the possibility to give a real time overview of the current RFP and PP states in the DECT OpenMobility system. The following features are provided by the DECT monitor: • Reading out of the DECT configuration of a OpenMobility system.
OpenMobility SIP Installation, Administration and Maintenance Next, the defined trace options (event mask) are sent to the OMM. The options which are sent to the OMM are always those which were active the last time the application was exited. If the trace option “Transaction establish/release” is activated, the OMM will deliver all existing transactions. Following this, the OMM system delivers the desired trace data.
OpenMobility SIP Installation, Administration and Maintenance Following this initialization, the user can carry out the following modifications: • The trace settings can be modified using the menu item “Options-Event Mask”. Transmissions to the OMM take place after confirming the settings with “OK’”. • A “Config Request” can be sent again to the OMM. • A log file can be activated.
OpenMobility SIP Installation, Administration and Maintenance Aastra DeTeWe Doc-ID: pm-0504 28.11.
OpenMobility SIP Installation, Administration and Maintenance 5 Appendix 5.1 Communications Regulation Information for Aastra Phone 142 US FCC Notices (U.S. Only) This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
OpenMobility SIP Installation, Administration and Maintenance This EUT has been shown to be capable of compliance for localized specific absorption rate (SAR) for uncontrolled environment/general population exposure limits specified in ANSI/IEEE Std. C95.1-1992 and had been tested in accordance with the measurement procedures specified in FCC/OET Bulletin 65 Supplement C (2001) and IEEE 1528-2003.
OpenMobility SIP Installation, Administration and Maintenance limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation.
OpenMobility SIP Installation, Administration and Maintenance safety standards previously set by international standard bodies. These standards include a substantial safety margin designed to assure the safety of all persons, regardless of age and health. This device and its antenna must not be co-located or operating in conjunction with any other antenna or transmitter.
