Aastra DECToverSIP Installation, Administration And Maintenance
  1. Manuals
  2. Brands
  3. Aastra Manuals
  4. Conference System
  5. DECToverSIP
  6. Installation, administration and maintenance

Aastra DECToverSIP Installation, Administration And Maintenance

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Installation, Administration and
Maintenance
DECToverSIP
Release 1.8
Document ID: depl-0900
Version: 1.8
Aastra
Zeughofstr. 1
10997 Berlin, Germany
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.
© February 2010 - All Rights
Reserved

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DECToverSIP and is the answer not in the manual?

Questions and answers

Related Manuals for Aastra DECToverSIP

Summary of Contents for Aastra DECToverSIP

  • Page 1 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 Aastra.

  • Page 2: Table Of Contents

    Creating and Changing PPs’ ....................53 3.3.4.1.1 New, change and delete button ....................53 3.3.4.1.2 Import by configuration files ....................54 3.3.4.2 Subscription ..........................55 3.3.4.2.1 Subscription with configured IPEI ..................56 3.3.4.2.2 Wildcard Subscription ......................57 Aastra Page: 2 (104) depl-0900/0.4...
  • Page 3 IAGNOSTIC 7.3.1 Aastra DECT 142 / Aastra 142d site survey mode ..............79 7.3.2 Aastra DECT 142 / Aastra 142d auto call test mode ..............80 7.3.3 Aastra DECT 142 / Aastra 142d auto answer test mode ............80 7.3.4 Syslog ............................

  • Page 4: Overview

    Handset / Aastra In the context of the DECToverIP using SIP solution, an 142d Aastra DECT 142 Handset, Aastra 142d and Portable Part (PP) are interchangeable. In consideration of differences in regulatory requirements between North America and all other areas of the world...
  • Page 5 Installation, Administration and Maintenance • Aastra DECT 142 For use in North America. • Aastra 142d For use in all other areas. Access Point Access Point In the context of the DECToverIP using SIP solution, an Access Point and a Radio Fixed Part (RFP) are interchangeable.
  • Page 6 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 have similar signal strength, certain threshold values are in effect. Aastra Page: 6 (104) depl-0900/0.4...

  • 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 Page: 7 (104) depl-0900/0.4...

  • Page 8: Introduction

    (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). • Aastra DECT 142 Handsets / Aastra 142d (also known as Portable Parts (PP)) • OpenMobility Manager (OMM): Management interface for the DECToverIP using SIP solution, which runs on one of the Radio Fixed Parts.

  • Page 9: About The Access Points (Rfps')

    Installation, Administration and Maintenance About the Access Points (RFPs’) Aastra DeTeWe provides 3 kind of Access Points: RFP L32 DECT Access Point as indoor model RFP L34 DECT Access Point as outdoor model RFP L42 WLAN DECT + WLAN Access Point as indoor model In general the RFP 32 and RFP 34 have the same hardware and software capabilities.
  • Page 10 RFP activates the OMM services. Note: It is possible to deactivate the DECT part of a RFP. If the DECT interface is deactivated then all resources (CPU and memory) are available for the OMM. Aastra Page: 10 (104) depl-0900/0.4...
  • Page 11 RFP L42 WLAN LED for WLAN LED green (Application) LED orange (Application) LED red (Booter) Ethernet jack Power supply in line with Power over Ethernet standard IEEE 802.3af Power jack (120 V/230 V AC adapter) Aastra Page: 11 (104) depl-0900/0.4...

  • Page 12: 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 142d), the following IP streams must be established: •...
  • Page 13 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. Aastra Page: 13 (104) depl-0900/0.4...
  • Page 14 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 Page: 14 (104) depl-0900/0.4...

  • Page 15: 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 Page: 15 (104) depl-0900/0.4...

  • Page 16: 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 Page: 16 (104) depl-0900/0.4...

  • Page 17: About The Portable Parts

    Installation, Administration and Maintenance About the Portable Parts Portable Part (PP) is DECT standard terminology and in the context of the DECToverIP using SIP solution is interchangeable with handset. Aastra provides the following handsets: 142d 610d 620d 630d 142d 610d...

  • Page 18: System Capacities

    Installation, Administration and Maintenance In addition to the Aastra DECT 142 / Aastra 142d, standard 3rd party DECT GAP phones may operate on the DECToverIP using SIP solution. But the functionality may be limited by the characteristics of the 3rd party DECT phone.

  • Page 19: Installation And Configuration

    Booting is performed in two steps: 1. Starting the boot process. 2. Starting the application. Booter The RFP has only a little standalone application built into the flash. This software realizes the so called net boot process. Aastra Page: 19 (104) depl-0900/0.4...

  • Page 20: Start-Up Of The Openmobility Manager

    3.1.3.1.1.2 Parameter request list (code 55) 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) Aastra Page: 20 (104) depl-0900/0.4...
  • Page 21 Installation, Administration and Maintenance • Public option 225 (code 225) • Public option 226 (code 226) Aastra Page: 21 (104) depl-0900/0.4...

  • Page 22: Dhcp Offer

    IP address of the OMM from DHCP. 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). Aastra Page: 22 (104) depl-0900/0.4...
  • Page 23 C0 A8 00 01 = 192.168.0.1 If there is more than one option, add the next option at the end of the previous one. Depending of the DHCP server you need to end the option 43 with FF. Aastra Page: 23 (104) depl-0900/0.4...

  • Page 24: Booter Update

    If no matching reply was received the DHCP client resends the request 2 times after 1 second. Then the DHCP client will wait for 1 minute before resending 3 requests again. If the DHCP client cannot accept an DHCP offer within 3 minutes the RFP is rebooted. Aastra Page: 24 (104) depl-0900/0.4...

  • Page 25: Rfp Led Status

    RFP is up and running The RFP L42 WLAN has an additional LED describing the WLAN status: State WLAN LED state WLAN module not found Red on WLAN deactivated because OMM is running WLAN deactivated per configuration Aastra Page: 25 (104) depl-0900/0.4...
  • Page 26 LED red (Booter) Ethernet jack Power supply in line with Power over Ethernet standard IEEE 802.3af Power jack (120 V/230 V AC adapter) The RFP L42 WLAN must connect to a 100BaseT Ethernet for WLAN service. Aastra Page: 26 (104) depl-0900/0.4...

  • Page 27: State Graph Of The Start-Up Phases

    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 Change of the local configuration Aastra Page: 27 (104) depl-0900/0.4...

  • Page 28: Static Local Configuration Of Arfp

    If the RFP has already an IP address enter this address in the IP address field. In this case you can reach the RFP from outside the local LAN segment. Optional. To set additional parameters, press the “Add parameter” button and choose the desired parameter. Aastra Page: 28 (104) depl-0900/0.4...
  • Page 29 The configuration can only be set after powering up or at the retry phase (LED flashing 0,25 Hz) or in kernel mode, please see section 3.1 for details. The configurator tool waits 2 seconds and retries transmitting the data 3 times. Aastra Page: 29 (104) depl-0900/0.4...
  • Page 30 Then the MAC address will be used to address a RFP in the LAN segment of the proxy RFP. Scanning for available RFPs’ and configuration of multiple RFPs’ via a configuration file could be used also with the proxy mechanism. Aastra Page: 30 (104) depl-0900/0.4...
  • Page 31 The list of RFPs’ could be saved by using the ‘Save RFP’s’ button. This enables an administrator to edit the configuration data of multiple RFPs’ via a text editor or a spread sheet application like described in chapter 8.3.3. Aastra Page: 31 (104) depl-0900/0.4...

  • Page 32: Configuring The Openmobility Manager

    Note that the login and proxy data will be used for the whole configuration file! 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 Aastra Page: 32 (104) depl-0900/0.4...

  • Page 33: Service Login Procedure

    OpenMobility service is accessible via a default build-in user account with user “ ” and password “ ”. With the first login into a new OpenMobility version the user has to accept the End User Licence Agreement (EULA). Aastra Page: 33 (104) depl-0900/0.4...
  • Page 34 If the default build-in user account is active the administrator has to change the password of the “Full access” and “root” account. The meaning of the different account types is described in chapter 4.2 and 4.3. Aastra Page: 34 (104) depl-0900/0.4...

  • Page 35: System

    The authentication code is used during initial PP subscription as a security option (see chapter 3.3.4). A code entered here provide a default DECT Authentication Code for each new created PP (see chapter 3.3.4.1). It is optional. Aastra Page: 35 (104) depl-0900/0.4...
  • Page 36 OpenMobility Manager is running. The date and time will be provided by the OpenMobility Manager to the DECT 142 Handset / Aastra 142d if the handset initiates a DECT location registration. This will be done in the following cases: • Subscribing at the OMM •...

  • Page 37: Restarting The Omm

    3.3.2.1.2 Encryption Encryption is only available on RFP 32/34/42 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 38: Regulatory Domain

    Address of the outbound proxy server. All SIP messages originating from the OMM are sent to this server. For example, if you have a Session Border Controller in your network, then you would normally set its address here. Optional. Aastra Page: 38 (104) depl-0900/0.4...
  • Page 39 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 142d if the user has received a voice message on his voice box which is supported by the Media Server.
  • Page 40 Please Note: Possibly, the other party recognises events twice. DTMF Payload Type If Out-of-Band is enabled the Payload Type specify the payload type which is used for sending DTMF events based on Section 1.3 reference /9/. Aastra Page: 40 (104) depl-0900/0.4...

  • Page 41: User Account

    After initial installation or after removing the configuration file the OpenMobility service is accessible via a build-in user account with user “ ” and password “ ”. These settings which are case sensitive can be changed on the “User Account” web page. Aastra Page: 41 (104) depl-0900/0.4...

  • Page 42: Time Zones

    The meaning of the different account types is described in chapter 4.2 and 4.3. 3.3.2.4 Time zones A time and date resynchronization of the Aastra DECT 142 / Aastra 142d devices is described in chapter 3.3.2.1. In the time zone section the OpenMobility Manager provides all available time zones.

  • Page 43: Database Management

    See the following screen shots as an example: 3.3.2.5 Database Management The database management allows a flexible backup and restore management of the OMM database. The OMM database contains all configuration settings which are configurable via the WEB service interface. Aastra Page: 43 (104) depl-0900/0.4...
  • Page 44 The OMM database will be saved in a compressed file in a proprietary format. Any modification of this file outside the OMM is not allowed. The following protocols for the transport to or from an external server are supported: TFTP Aastra Page: 44 (104) depl-0900/0.4...

  • Page 45: Manual Database Import

    For a manual database export to an external server select the preferred protocol and enter the IP address or name of the server. If necessary, enter the account data (user name / password) of the server and select the path Aastra Page: 45 (104) depl-0900/0.4...

  • Page 46: Automatic Database Import

    The file URL configured via DHCP or OM Configurator is always displayed. WARNING: For an automatic database import at a configured time is a time synchronisation with a NTP server recommended. For NTP server configuration see chapter 3.1.4 and chapter 3.2. Aastra Page: 46 (104) depl-0900/0.4...

  • Page 47: Automatic Database Export

    If there is no configuration change then no backup will be done. A backup file will be overwritten during a day if there is more than one modification. A new file will be created when this first change occurs at the day. Aastra Page: 47 (104) depl-0900/0.4...

  • Page 48: Rfp Configuration

    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 Page: 48 (104) depl-0900/0.4...

  • Page 49: Creating And Changing Rfps

    RFP. A RFP could be deleted by pressing the trash can icon . A similar popup window asks for confirmation showing the current configuration of this RFP. 3.3.3.1.2 Import by configuration files Aastra Page: 49 (104) depl-0900/0.4...

  • Page 50: Capture Of Rfps

    All successfully stored records are marked green in the column called “Added” (failed records are get a red star, error hints can be read in the referring logfile or in a Syslog trace). 3.3.3.1.3 Capture of RFPs’ Aastra Page: 50 (104) depl-0900/0.4...

  • Page 51: States Of A Rfp

    This phase should usually last only for a few seconds after starting up the RFP or the OMM. If this state lasts longer or is re-entered after being in a synchronous state this is an indication for a bad location of the RFP. Aastra Page: 51 (104) depl-0900/0.4...

  • Page 52: Rfp Hw Type

    100 handsets. Because the browser function can not be used to search for a certain handset in all sub lists, a search function is available, which allows to find a handset by a given number or IPEI. Aastra Page: 52 (104) depl-0900/0.4...

  • Page 53: Creating And Changing Pps

    PP separately. If a global DECT authentication code is given on the “System Settings” web page this value is filled in here as default. This parameter is optional. Aastra Page: 53 (104) depl-0900/0.4...

  • Page 54: Import By Configuration Files

    Select your configuration file and press the “Import” button (see Appendix 8.3.1 to get information about file layout ). A parsing protocol can be read, if you press the referring “Logfile” button. All successfully imported data records are presented in a list: Aastra Page: 54 (104) depl-0900/0.4...

  • Page 55: Subscription

    All successfully stored records are marked green in the column called “Added” (failed records are get a red star, error hints can be read in the referring logfile or in a Syslog trace). 3.3.4.2 Subscription Aastra Page: 55 (104) depl-0900/0.4...

  • Page 56: Subscription With Configured Ipei

    Furthermore the IPEI leads to a further guarantee not to receive none authorised subscriptions even if AC is not set as a mean to achieve security. To enable subscriptions, please press the “Start” button of section “Subscription with configured IPEIs’”: Aastra Page: 56 (104) depl-0900/0.4...

  • Page 57: Wildcard Subscription

    WARNING: The input of the additional ID is only possible with Aastra DECT 142 / Aastra 142d. There is no possibility, to type that value on third party GAP phones. If GAP phones are going to subscribe wildcard, the first free PP data record without any additional ID will be selected and assigned.

  • Page 58: Wlan Configuration (Rfp L42 Wlan Only)

    Spain 0x32: FRANCE France 0x40: Japan 0x41: MKK1 Japan (MKK1) This setting depends on the country and is prescribed by the laws of that country. Only the setting prescribed for that country must be used. Aastra Page: 58 (104) depl-0900/0.4...
  • Page 59 Parameter Range Notes Beacon Period 50 – 65.535 Milliseconds The length of the intervals between beacons. DTIM Period 1 - 255 Beacons The number of beacons between two DTIM (Delivery Traffic Indication Map) transmissions. Aastra Page: 59 (104) depl-0900/0.4...

  • Page 60: Optimizing The Wlan

    At the same time, it increases the network's ability to adjust the mutually negotiated signal strength. A higher value, i.e. a longer beacon interval, indirectly reduces the power consumption of the WLAN client. Aastra Page: 60 (104) depl-0900/0.4...

  • Page 61: Securing The Wlan With Radius

    WLAN client and the Radius server. You must enter the Radius server IP address, IP port and common secret in the radius setting section. Aastra Page: 61 (104) depl-0900/0.4...
  • Page 62 Aastra age: 62 (104) epl-0900/0.4...
  • Page 63 “Sorted by” the “WLAN profiles” entry. In the ‘WLAN settings’ section of the page you can select Profile, Antenna Diversity, Antenna, Output Power Level and Channel. Antenna Diversity should generally be activated (i.e. ticked) so that the AP can automatically Aastra Page: 63 (104) depl-0900/0.4...

  • Page 64: Requirements For The Wlan

    User name (a distinguished name) and password may be filled, if requested by the LDAP Server. Otherwise an anonymous bind takes place. Please note: the DECT IP OMM supports LDAP simple bind • Search Attribute Searches will be done for one of the following attributes Aastra Page: 64 (104) depl-0900/0.4...
  • Page 65 Selection between the following two alternatives is possible: Surname (sn), first name (givenname) ->default first name (givenname) and Surname (sn) • Server Search Timeout (value range: 1 - 99 sec) The search results will be accepted within search time. Aastra Page: 65 (104) depl-0900/0.4...

  • Page 66: Digit Treatment

    Each substitute may be composed of the digit (0-9) and the characters ‘*’ and ‘’#’. 3.3.6.3 Feature Access Codes Features Access Codes allow to perform specific actions on the OMM from any subscribed DECT handset. Aastra Page: 66 (104) depl-0900/0.4...
  • Page 67 “99999*4701#” en bloc. WARNING: Overlap sending will not supported for FAC. “FAC number” and “FAC action code” must be entered en bloc. FAC functions will be confirmed by an audible indication to the user (in-band tone signals). Aastra Page: 67 (104) depl-0900/0.4...

  • Page 68: Security

    The access using this account type is not reachable from other hosts hence a login using the full access type is necessary. IMPORTANT: It is highly recomented not to use this account type. It’s meant for technical support only. The factory setting for this account is Aastra Page: 68 (104) depl-0900/0.4...

  • Page 69: Changing Account Data

    50% or more of the same character ('World11111' or 'W1o1r1l1d1') or ● the new password contains one of the following items (either upper or lower case as well as forward or backward): account name host name (IP address) old password or Aastra Page: 69 (104) depl-0900/0.4...

  • Page 70: Potential Pitfalls

    It is therefore recommended to switch of the OM Configuration before taking an RFP out of an installation. But nevertheless the OM Configurator allows to reset the permanent memory of an RFP (the Aastra DeTeWe support must be connected). Aastra Page: 70 (104) depl-0900/0.4...

  • Page 71: Omm Resiliency

    Each RFP of the DECT system have to be configured with two OMM IP addresses. This both OMM addresses can be either configured via DHCP (see chapter 3.1.1) or with the OM Configurator (see chapter 3.2). Fall Over Situations Aastra Page: 71 (104) depl-0900/0.4...

  • Page 72: Fall Over Failure Situations

    The IP connection between OMMs’ fails and the configured SIP Proxy/Registrar is unreachable. In this case the active OMM shall wait until the SIP Proxy/Registrar is reachable. The following state diagram shows the OMM–Resiliency states: Aastra Page: 72 (104) depl-0900/0.4...

  • Page 73: Specific Resilient Situations

    During this time an inconsistent OpenMobility system is working with some constraints. The WEB service will warn with the warning “No Resiliency” for both OMMs’ in this situation and possible made configuration changes are not save. Aastra Page: 73 (104) depl-0900/0.4...

  • Page 74: Two Dect Air Interfaces

    Note: Hand over between PPs’ located to RFPs’ which are controlled by different OMMs’ is not possible. When the OMMs’ get in contact again with each other this inconsistent OpenMobility system situation will end. Aastra Page: 74 (104) depl-0900/0.4...

  • Page 75: Download Over Air

    2 different software versions. During the download the new firmware is written to one partition and the PP is running from the other partition. The new firmware will not be activated until Aastra Page: 75 (104) depl-0900/0.4...

  • Page 76: How To Configure Download Over Air

    “System Settings” web page. The PP firmware is part of each OpenMobility software package which is delivered by Aastra. The PP firmware is delevered in the package file aafon6xxd.dnld. This package file must be put on the same tftp server and path where the OMM- RFP gets his boot image file (e.
  • Page 77 If the Download over Air feature is activated the status of the Download over Air service together with some statistics is presented on the “Status” web page. The individual download status of each PP is presented on the “Portable Part” web page. PP is busy. Aastra Page: 77 (104) depl-0900/0.4...
  • Page 78 The dow wnload is n not possible e because - the ha andset is no ot reachab - the ha andset is de etached The spe ecific reaso on is shown n as a toolt tip. Aastra age: 78 (104) epl-0900/0.4...

  • Page 79: Maintenance

    7.3.1 Aastra DECT 142 / Aastra 142d site survey mode You can set the Aastra DECT 142 / Aastra 142d in “site survey mode” with a few keystrokes. In this mode the phone will display the RFPs’ and the actual field strength of the receiving signal in dBm.

  • Page 80: Aastra Dect 142 / Aastra 142D Auto Call Test Mode

    7.3.2 Aastra DECT 142 / Aastra 142d auto call test mode You can set the Aastra DECT 142 / Aastra 142d to “auto call test mode” with a few keystrokes. In this mode the phone will call a specified number cyclically.

  • Page 81: Syslog

    Each RFP offers a lot of command within the ssh shell. Most of them are useful for diagnostic and may help experts, to resolve failures. Note: Some commands can harm the system operation. The ssh access of a RFP is open if Aastra Page: 81 (104) depl-0900/0.4...
  • Page 82 RFP is not connected to an OMM To activate the ssh access of a RFP which has a connection to an OMM, activate the “Remote Access” checkbox on the OMM System settings web page. Aastra Page: 82 (104) depl-0900/0.4...

  • Page 83: Login

    : well known ping traceroute : well known traceroute free : well known free : well known ps : well known top ifconfig : well known ifconfig uptime : well known uptime reboot : well known reboot Aastra Page: 83 (104) depl-0900/0.4...

  • Page 84: Rfp Console Commands

    | remote configure spy levels on IP-RFPs | displays configured RFPs | lists all created MXP semaphores | set/display spy levels: [ <key #> <level #> ] standby | displays redundant OMMs sync | commands for RFP synchronisation Aastra Page: 84 (104) depl-0900/0.4...

  • Page 85: Core File Captchering

    • Reading out of the DECT configuration of a IP DECT system • Configuration can be stored in an ASCII file. • Display of DECT transactions IP DECT Base Station-telephone in clear tabular form, with highlighting of handover situations. Real-time display. Aastra Page: 85 (104) depl-0900/0.4...
  • Page 86 When all links have been established, the DECT data of the system are automatically read out and entered in the tables "RFP-Table" and "PP- Table". This procedure is called "Config Request". Aastra Page: 86 (104) depl-0900/0.4...
  • Page 87 There is no display in the FP table if there is no column free for display. If the event has already been displayed, it can be overwritten at any time. The events are not displayed if they occur during an on-going Aastra Page: 87 (104) depl-0900/0.4...
  • Page 88 IP DECT Base Station. There are several optional child windows selectable. They are all listed below and give some more information about the IP DECT systems. Mostly they are statistics and for internal use only. Aastra Page: 88 (104) depl-0900/0.4...
  • Page 89 Installation, Administration and Maintenance Aastra Page: 89 (104) depl-0900/0.4...

  • Page 90: Appendix

    Installation, Administration and Maintenance Appendix Communications Regulation Information for Aastra DECT 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 91: Communications Regulation Information For Rfp 32 Or Rfp 34 (Na)

    (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 Page: 91 (104) depl-0900/0.4...
  • Page 92 (2) this device must accept any interference, including interference that may cause undesired operation of the device. Privacy of communications may not be ensured when using this telephone. Exposure to Radio Frequency (RF) Signals: Aastra Page: 92 (104) depl-0900/0.4...
  • Page 93 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 Page: 93 (104) depl-0900/0.4...

  • Page 94: Pre Configuration File Rules

    .csv export of Excel-Sheet and copied into the configuration file. • Instructions are only proceeded on those fields, which are left empty within the data sequence section Aastra Page: 94 (104) depl-0900/0.4...

  • Page 95: Pp Configuration File (Omm Database)

    = {<"number">, <start value for id's to be generated>} # -- SIP password = {<"number">, <start value for id's to be generated>} start_number = 5401 no_of_number = 10 ac = 1001 additional_pin = number sip_user = number sip_pw = number Aastra Page: 95 (104) depl-0900/0.4...
  • Page 96 3 : 5402;Karl May;1004;;5402;5402;5402 4 : 5403;Karl Valentin;1005;;5403;5403;5403 5 : 5404;Karl Heinz;1006;;5404;5404;5404 6 : 5405;Radi Radenkowicz;1007;;5405;5405;5405 7 : 5406;Radi Rettich;1008;;5406;5406;5406 8 : 5407;Wadi Wade;1009;;5407;5407;5407 9 : 5408;Stephan Fiedler;1010;0127105314450;5408;5408;5408 10 : 5409;Waldi Hartmann;1011;;5409;5409;5409 11 : 5410;;1012;;5410;5410;5410 Aastra Page: 96 (104) depl-0900/0.4...

  • Page 97: Rfp Configuration File/Central (Omm Database)

    RFP configuration file/central: # ---------------------# # instruction section: # ---------------------# # -- name = {<location name>} # -- active = {0,1} # -- cluster = {1..256} # -- wlan_profile = <valid reference to an existin WLAN profile>} Aastra Page: 97 (104) depl-0900/0.4...
  • Page 98 = 1 ok: cluster = 1 not set: wlan_profile not set: wlan_antenna not set: wlan_channel_bg not set: wlan_power not set: wlan_act processing of section: 0 : 00:30:42:08:31:A2;142(Mirko);1;1;;;;; 1 : 00:30:42:0D:95:E0;Lab1;1;1;;;;; 2 : 00:30:42:0A:C5:40;Lab2(kiel);1;2;;;;; Aastra Page: 98 (104) depl-0900/0.4...

  • Page 99: Rfp Configuration File/Local (Om Configurator)

    Up to two NTP server IP addresses • ntp_name Up to two NTP server names • syslog_addr IP address of syslog daemon • syslog_port Listen port of syslog daemon • broadcast_addr local broadcast address • country Country code Aastra Page: 99 (104) depl-0900/0.4...

  • Page 100: Data Section Fields

    # -------------------------------------------# # 1. MAC_ADDR ! no instruction supported ! # 2. ACTIVE_FLAG # 3. RFPADDR ! no instruction supported ! # 4. NET_MASK # 5. TFTP_SERVER # 6. TFTP_FILE # 7. OMM1 # 8. OMM2 Aastra Page: 100 (104) depl-0900/0.4...
  • Page 101 0 :added: 00-30-42-01-01-01;1;172.30.111.1;255.255.0.0;172.30.200.92; /omm_ffsip.tftp;172.30.111.188;;;;;;;;;;; 1 :added: 00-30-42-02-02-02;1;172.30.111.2;255.255.0.0;172.30.200.92; /omm_ffsip.tftp;172.30.111.188;;;;;;;;;;; 2 :added: 00-30-42-01-01-03;1;172.30.111.3;255.255.0.0;172.30.200.92; /omm_ffsip.tftp;172.30.111.188;;;;;;;;;;; RFP configuration: 0 : MAC address=00-30-42-01-01-01 : use_local_cfg=1 ip=172.30.111.1 subnet=255.255.0.0 siaddr=172.30.200.92 boot_file=/omm_ffsip.tftp ommip1=172.30.111.188 0 : MAC address=00-30-42-01-01-01 : timer expired ! ! Aastra Page: 101 (104) depl-0900/0.4...
  • Page 102 1 : MAC address=00-30-42-02-02-02 : use_local_cfg=1 ip=172.30.111.2 subnet=255.255.0.0 siaddr=172.30.200.92 boot_file=/omm_ffsip.tftp ommip1=172.30.111.188 1 : MAC address=00-30-42-02-02-02 : timer expired ! ! 2 : MAC address=00-30-42-01-01-03 : use_local_cfg=1 ip=172.30.111.3 subnet=255.255.0.0 siaddr=172.30.200.92 boot_file=/omm_ffsip.tftp ommip1=172.30.111.188 2 : MAC address=00-30-42-01-01-03 : timer expired ! ! Aastra Page: 102 (104) depl-0900/0.4...

  • Page 103: Protocols And Ports

    > 1023 port (default port (default > 1023 application 389) 389) http redirect client port client port application Web-IF / HTTPS client port client port application > 1023 > 1023 > 1023 > 1023 application Aastra depl-0900/ Page: 103 (104)
  • Page 104 OMM receive Comments SRC port DST port SRC port DST port SRC port DST port SRC port DST port client port client port application DECTnetMonitor 8106 client port client port 8106 application (TCP) Additional protocols ICMP Aastra Page: 104 (104) depl-0900/...

Table of Contents