free hit counter
Aastra SIP-DECT Installation, Administration And Maintenance Manual
  1. Manuals
  2. Brands
  3. Aastra Manuals
  4. Telephone
  5. SIP-DECT
  6. Installation, administration and maintenance manual

Aastra SIP-DECT Installation, Administration And Maintenance Manual

Hide thumbs Also See for SIP-DECT:
Table of Contents

Advertisement

Quick Links

Download this manual
Installation, Administration and
TM
Maintenance of the Aastra SIP-DECT
solution
Document ID: pm-0624
Version: 0.7
© June 2007 - All Rights Reserved
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.

Advertisement

Table of Contents
loading

Related Manuals for Aastra SIP-DECT

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.

  • Page 2: Table Of Contents

    ANDSET FIRMWARE VERSION ............................. 41 IAGNOSTIC 4.4.1 Aastra DECT 142 site survey mode ..................41 4.4.2 Aastra DECT 142 auto call test mode ..................42 4.4.3 Aastra DECT 142 auto answer test mode.................. 42 4.4.4 Syslog............................43 APPENDIX ............................... 44...
  • Page 3 Installation, Administration and Maintenance DECT 142..........44 OMMUNICATIONS EGULATION NFORMATION FOR ASTRA RFP 32 RFP 34 (NA) ........45 OMMUNICATIONS EGULATION NFORMATION FOR Aastra Telecom Page: 3 (47)

  • Page 4: Overview

    Real Time Control Protocol Real Time Protocol 1.2.2 Definitions Aastra DECT 142 Aastra DECT 142 Handset / Aastra Phone 142 Handset / Aastra In the context of the Aastra SIP-DECT solution, an Phone 142 Aastra DECT 142 Handset, Aastra Phone 142 and Portable Part (PP) are interchangeable.
  • Page 5 Installation, Administration and Maintenance Access Point Access Point In the context of the Aastra SIP-DECT solution, an Access Point and a Radio Fixed Part (RFP) are interchangeable. Asterisk Asterisk Asterisk is a complete Open Source PBX in software. It runs on Linux, BSD and MacOSX and provides many features.
  • Page 6 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: References

    /15/ RFC 3842, A Message Summary and Message Waiting Indication 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 Aastra Telecom Page: 7 (47)

  • Page 8: Introduction

    The Aastra SIP-DECT solution comprises the following components: • Aastra SIP-DECT Access Points (also known as Radio Fixed Parts (RFPs)) 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).

  • Page 9: About The Access Points (Rfps)

    10 carrier frequencies Transmit Power 24 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 RFP L32 IP Unused LED LED green (Application) LED orange (Application) LED red (Booter) Ethernet jack Power supply in line with Power over LAN™ standard IEEE 802.3af class 0 Power jack (120 V/230 V AC adapter) Aastra Telecom Page: 10 (47)

  • Page 11: Openmobility Manager

    The OpenMobility Manager (OMM) runs on one of the RFPs. IP signalling and media stream To establish a call between an IP Phone and a PP (Aastra DECT 142 Handset / Aastra Phone 142), the following IP streams must be established: •...
  • Page 12 Local Area Network (LAN). Although the voice packets will not impact 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 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 Page: 13 (47)

  • Page 14: Rfp Synchronization

    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 Page: 14 (47)

  • Page 15: Rfp Channel Capacity

    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 Page: 15 (47)

  • Page 16: About The Portable Parts

    250 mW (maximum output per active channel) 10 mW (average output per active channel) In addition to the Aastra DECT 142 Handset / Aastra Phone 142, standard 3rd party DECT GAP phones may operate on the Aastra SIP-DECT solution. But the functionality may be limited by the characteristics of the 3rd party DECT phone.

  • Page 17: Installation And Configuration

    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)

  • Page 18: Start Up Of The Openmobility Manager

    The DHCP client in the booter requests the following options in the parameter request list: • Subnet mask option (code 1) • Router option (code 3) • Public option 224 (code 224) • Public option 225 (code 225) • Public option 226 (code 226) Aastra Telecom Page: 18 (47)

  • Page 19: Dhcp Offer

    The DHCP client is capable of receiving broadcast and unicast DHCP replies. 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: Aastra Telecom Page: 19 (47)
  • Page 20 11 02 00 01 0a 04 C0 A8 00 01 where C0 A8 00 01 represents 192.168.0.1 for the OMM IP Tones for the following countries are supported: country country code Germany Great Britain Suisse Spain Italy Russia Belgium Netherlands Czechia Finland Poland Taiwan North America France Aastra Telecom Page: 20 (47)

  • Page 21: Booter Update

    RFP L32 IP Unused LED LED green (Application) LED orange (Application) LED red (Booter) Ethernet jack Power supply in line with Power over LAN™ standard IEEE 802.3af class 0 Power jack (120 V/230 V AC adapter) Aastra Telecom Page: 21 (47)
  • Page 22 Application (init) Green flashing (2 sec on, 0.5 The DECT part of the RFP sec off) does not work (either not configured or not synchronized with other RFP’s) Application (init) Green RFP is up and running Aastra Telecom Page: 22 (47)

  • Page 23: State Graph Of The Start Up Phases

    Connection attempt to OMM failed Connect to OMM LED green flashing 2 seconds Application on / 50ms off Failure, i.e. connection to OMM lost Synchronize DECT LED green Application Failure, i.e. connection to OMM lost Up & running Aastra Telecom Page: 23 (47)

  • Page 24: Static Local Configuration Of Arfp

    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)

  • Page 26: Configuring The Openmobility Manager

    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.

  • Page 27: System

    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.

  • Page 28: System Settings

    OpenMobility Manager is running. The date and time will be provided by the OpenMobility Manager to the DECT 142 Handset / Aastra Phone 142 if the handset initiates a DECT location registration. This will be done in the following cases: •...

  • Page 29: Restarting The Omm

    ‘Restart’. There is also the option to reset the configuration data. A reset web page is loaded then displaying a progress bar and the login web page is loaded automatically if the OMM is reachable again. Aastra Telecom Page: 29 (47)

  • Page 30: Encryption

    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. If encryption is enabled and another RFP variant connects to the OMM, its DECT air interface will not be activated.

  • Page 31: Outbound Proxy

    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 Handset / Aastra Phone 142 if the user has received a voice message on his voice box which is supported by the Media Server.

  • Page 32: User Account

    ”. These settings which are case sensitive can be changed on the “User Account” web page. 3.3.2.4 Time zones A time and date resynchronization of the Aastra DECT 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)

  • Page 34: Backup

    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)

  • Page 36: Dect Configuration

    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)

  • Page 38: Configuration Of Portable Parts

    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)

  • Page 41: Maintenance

    “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: •...

  • Page 42: Aastra Dect 142 Auto Call Test Mode

    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.

  • Page 43: Syslog

    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. Aastra Telecom Page: 43 (47)

  • Page 44: Appendix

    Installation, Administration and Maintenance Appendix Communications Regulation Information for Aastra DECT 142 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)

  • Page 47: Aastra Telecom Page

    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)

Table of Contents