Scalable 4 lines telephone system for the small-medium business (2 pages)
Summary of Contents for Aastra SIP-DECT
Page 1
Aastra Telecom 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 Aastra.
1.2.2 Definitions Aastra DECT 142 Aastra DECT 142 Handset Handset In the context of the Aastra SIP-DECT solution, an Aastra DECT 142 handset and Portable Part (PP) are interchangeable. Access Point Access Point In the context of the Aastra SIP-DECT solution, an Access Point and a Radio Fixed Part (RFP) are interchangeable.
Page 5
Generic Access Profile • • • • Aastra Telecom The standard (ETS 300 175) essentially specifies the air interface, known as the radio interface. Voice and data can both be transmitted via this interface. Its technical key characteristics for Europe are: •...
Access code for the Portable Part. This code determines whether a PP can access a particular DECT system. Used for unique selection of the system at handset enrolment/subscription time. Provided with the Aastra OMM Activation Kit and unique to each SIP-DECT deployment. Roaming Roaming While in motion, the PP performs ongoing measurements to determine which RFP is best received.
Page 7
Event Package for the Session Initiation Protocol (SIP), August 2004 /16/ RFC 3891, The Session Initiation Protocol (SIP) “Replaces” Header, September 2004 /17/ RFC 3892, The Session Initiation Protocol (SIP) Referred-By Mechanism, September 2004 /18/ OpenMobility Diagnostic Tools Aastra Telecom Page: 7 (47)
Introduction About the Aastra SIP-DECT solution The Aastra SIP-DECT solution comprises the following components: • Aastra SIP-DECT Access Points (also known as Radio Fixed Parts (RFP’s)) being distributed over an IP network and offering DECT wireless and IP interfaces. • A SIP Call Manager/IP PBX/Media Server platform (e.g. Asterisk).
5 carrier frequencies Transmit Power 20 dBm One RFP within a SIP-DECT installation must be declared to operate as the OpenMobility Manager (OMM). The RFP acting as the OMM may also act as a regular RFP as well if it is included into a DECT Cluster.
Page 10
TFTP server but only one RFP activates the OMM services. Note: 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. Aastra Telecom RFP32 Unused LED LED green (Application)
The OpenMobility Manager (OMM) runs on one of the RFP’s. IP signalling and media stream To establish a call between an IP Phone and a PP (Aastra DECT 142 Handset), the following IP streams must be established: • A signalling channel to and from the SIP phone.
Page 12
LAN traffic, signal packets will. It is also be possible to direct the media stream to connect directly the IP phone and the RFP, as shown in the following figures. Aastra Telecom Media Server Media Gateway Page: 12 (47)
Page 13
RFP has a better signal strength. Again the media stream from the SIP phone cannot move to the secondary RFP, so the primary RFP uses the LAN to direct the voice to the new secondary RFP. Aastra Telecom Media Server Media Gateway...
If a RFP loses the synchronization the RFP does not accept new calls (“busy bit”). There is a delay of maximum 3 minutes until the active calls on this RFP are finished. Then it tries to get synchronized again. Aastra Telecom Media Server Media Gateway...
Whenever the busy state is announced a log entry is made to the system logs. If the announcement of busy raises in a specific area, a further RFP should be installed to double the number of media streams available for calls. Aastra Telecom Unreliable Installation R 103...
100 mW (maximum output per active channel) 5 mW (average output per active channel) In addition to the Aastra DECT 142 Handset, standard 3rd party DECT GAP phones may operate on the SIP-DECT solution. But the functionality may be limited by the characteristics of the 3rd party DECT phone.
IP interface from the configuration settings in the internal flash memory. If no settings are available or these settings are disabled, the RFP tries to determine these settings via DHCP. The RFP gets the application image file from the TFTP server. Aastra Telecom Page: 17 (47)
Therefore the flags field is 0x0000. The DHCP request contains the well-known magic cookie (0x63825363) and the end option (0xFF). The following parameters will be supported within this step: Option / Field Aastra Telecom Meaning Mandatory Page: 19 (47)
Taiwan North America France 3.1.4.1 Booter update 3.1.4.1.1 Automatic booter update Aastra Telecom IP-Address of the IP-RFP Parameter named Boot Server Host Name with value as the IP-Address of the TFTP server Parameter named Bootfile Name with value of the path (optional) and name of the application image.
The RFP32 IP has three separate LEDs for red, orange and green to show the different states during start up. State Booter (Start up) Booter DHCP Aastra Telecom RFP32 Unused LED LED green (Application) LED orange (Application) LED red (Booter) Ethernet jack Power supply in line with Power over LAN™...
Page 22
Installation, Administration and Maintenance State Booter (TFTP) Application (DHCP) Application (init) Application (init) Application (init) Application (init) Aastra Telecom LED state Remarks Red flashing 2.5 Hz Downloading the application image Orange on Launching DHCP request and waiting for DHCP reply Green flashing 0.5 Hz...
2 seconds Application on / 50ms off Synchronize DECT LED green Application Up & running Aastra Telecom BOOTER LED red flashing 0,25 Hz DHCP no answer / offer not o.k. TFTP failed Kernel DHCP no answer; offer not o.k.
RFP from outside the local LAN segment. Optional. To set additional parameters, press the “Add parameter” button and choose the desired parameter. IMPORTANT: Select the “yes” checkbox for the RFP to “Use local configuration” otherwise DHCP will be used. Aastra Telecom Page: 24 (47)
Page 25
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. Aastra Telecom Page: 25 (47)
Installation, Administration and Maintenance Configuring the OpenMobility Manager The OMM runs on a designated RFP within a SIP-DECT deployment. The OMM is designated via DHCP options or statically declared via the OM Configurator tool. All other RFPs in the deployment are configured to point back to the OMM in the deployment.
Installation, Administration and Maintenance After login there are the following options available: Configuration of general SIP-DECT system parameters. Administration of the attached RFPs. Administration of the PPs. If no user action takes place the OMM logs out the user after 5 minutes.
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.
OMM is reachable again. 3.3.2.1.2 Encryption Encryption is only available on RFP32/34 products. Therefore it can only be enabled on the “System Settings” web page if there are no other Aastra RFP variants connected to the OMM. Aastra Telecom...
IP address or name of the SIP registrar. Enables the PPs to be registered with a Registrar. If a hostname and domain are used for the proxy server parameter, ensure that a DNS server and domain are specified for your SIP-DECT system via DHCP or the OMM Configurator tool. • Registrar Port SIP Registrar’s port number.
Page 31
Some Media Server such as the Asterisk support Message Waiting Indication (MWI) based on /15/. A MWI icon will be presented on an Aastra DECT 142 if the user has received a voice message on his voice box which is supported by the Media Server.
“ changed on the “User Account” web page. 3.3.2.4 Time zones A time and date resynchronization of the Aastra Phone 142 devices is described in chapter 3.3.2.1. In the time zone section the OpenMobility Manager provides all available time zones.
Page 33
(begin of standard time and begin of daylight savings time) have to be specified exactly. Therefore a certain day in the month or a certain week day in a month can be used. See the following screen shots as an example: Aastra Telecom Page: 33 (47)
The OpenMobility Manager will not try to synchronize RFPs over cluster borders. All used clusters are displayed in the navigation bar on the left side and the OMM RFP is marked with a bold font. Aastra Telecom Page: 34 (47)
Page 35
The same popup window could be opened for an existing RFP by pressing the tool icon of the appropriate RFP. An RFP could be deleted by pressing the trash can icon . A similar popup window asks for confirmation showing the current configuration of this RFP. Aastra Telecom Page: 35 (47)
OMM SW version the RFP connection attempt is rejected. This could happen when using several DHCP servers with different OpenMobility SW versions. In this case the RFP is marked with an error Aastra Telecom Page: 36 (47)
Page 37
Installation, Administration and Maintenance message. Moreover a global error message is displayed on the RFP list web page if at least one version mismatch has been found. Aastra Telecom Page: 37 (47)
IPEI. Adding Portable Parts to the SIP-DECT system A new PP can be added to the system by pressing the “New” button. The following popup window appears allowing the configuration of a new PP.
Page 39
On each PP handset, the administrator or user must subscribe to the SIP- DECT system through the System/Subscriptions menu. The specific PARK code for the SIP-DECT system must be entered in order to subscribe to the system. IMPORTANT: the PARK code in numeric format can be found at the top-right corner of the Portable Parts OMM web page.
Page 40
If a handset with the specified number and/or IPEI was found then a list is displayed which has this handset as the first entry. The search function can also be used to get to the right sub list in one step. Aastra Telecom Page: 40 (47)
“UPDATE” (see chapter 3.1.4.1). Site survey measurement equipment If an SIP-DECT installation has to be planned, a sufficient distribution of the RFPs is necessary, which fulfills the requirements for reliable synchronization and connectivity to the Portable Parts. The site survey kit may help you. It comprises: •...
4.4.2 Aastra DECT 142 auto call test mode You can set the Aastra DECT 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 on the charger.
Installation, Administration and Maintenance Appendix 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.
Page 45
(1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Modifications not expressly approved by this company could void the user's authority to operate the equipment. Aastra Telecom Page: 45 (47)
Page 46
Privacy of communications may not be ensured when using this telephone. Exposure to Radio Frequency (RF) Signals: The wireless phone is a radio transmitter and receiver. It is designed and manufactured not to exceed the emission limit for exposure to radio Aastra Telecom Page: 46 (47)
The radiating element of the RFP should be installed during operating at a separation distance greater than 20 cm between user and device. This device comply with the requirements for routine evaluation limits. Aastra Telecom Page: 47 (47)
Need help?
Do you have a question about the SIP-DECT and is the answer not in the manual?
Questions and answers