Avaya Communication Manager IP DECT, IP DECT Installation, Administration And Maintenance Manual
Avaya Communication Manager
Avaya IP DECT Installation,
Administration, and Maintenance
16-601625
Issue 1
August 2006
© 2006 Avaya Inc.
All Rights Reserved.
Notice
While reasonable efforts were made to ensure that the infor mation in this
document was complete and accurate at the time of printing, Avaya Inc. can
assume no liability for any errors. Changes and corrections to the information
in this document may be incorporated in future releases.
For full support information, please see the complete document,
Avaya Support Notices for Software Documentation, document number
03-600758.
To locate this document on our Web site, simply go to
http://www.avaya.com/support
the search box.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, addition s, or deletions to
the original published version of this documentation unless such modifications,
additions, or deletions were performed by Avaya. Customer and/or End User
agree to indemnify and hold harmless Avaya, Avaya's agents, servants and
employees against all claims, lawsuits, demands and judgments arising out of,
or in connection with, subsequent modifications, additions or deletions to this
documentation to the extent made by the Customer or End User.
Link disclaimer
Avaya Inc. is not responsible for the contents or reliability of any linked Web
sites referenced elsewhere within this documentation, and Avaya does not
necessarily endorse the products, services, or informa tion described or o ff ered
within them. We cannot guarantee that these links will work all of the time and
we have no control over the availability of the linked pages.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warran ty. In addition, Avaya’s
standard warranty language, as well as information regarding support for this
product, while under warranty, is available through the following Web site:
http://www.avaya.com/support
Copyright
Except where expressly stated otherwise, the Product is protected by copyrigh t
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense un der the
applicable law.
Avaya support
Avaya provides a telephone number for you to use to report pro blems or t o ask
questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Web site: http://www.avaya.com/support
and search for the document number in
.
.
Contents
Chapter 1: Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Abbreviations and Definitions . . . . . . . . . . . . . . . . . . . . . . . . 7
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About the Avaya IP DECT Solution. . . . . . . . . . . . . . . . . . . . . . . . . . 11
About the IP DECT base stations. . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Avaya DECT Mobility Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
IP signalling and media stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
IP DECT base station Synchronisation. . . . . . . . . . . . . . . . . . . . . . . . 17
IP DECT base station channel capacity . . . . . . . . . . . . . . . . . . . . . . . 20
About the Handsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
About Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
System Capacities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 3: Installation and Configuration . . . . . . . . . . . . . . . . . 23
Avaya IP DECT system start up. . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Startup of the IP DECT base stations . . . . . . . . . . . . . . . . . . . . . . 23
Booting Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Startup of Avaya IP DECT Mobility Manager. . . . . . . . . . . . . . . . . . . 24
ADMM in IP DECT base station mode . . . . . . . . . . . . . . . . . . . . 24
ADMM in Host-Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installing the ADMM software. . . . . . . . . . . . . . . . . . . . . . . . . 25
Configure Start Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . 25
To maintain the running ADMM on PC . . . . . . . . . . . . . . . . . . . . 26
Booter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Booter versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
DHCP client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
DHCP REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
DHCP OFFER. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
TFTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Booter update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Mandatory options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Optional options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
IP DECT base station LED Status. . . . . . . . . . . . . . . . . . . . . . . . . 31
State graph of the start up phases . . . . . . . . . . . . . . . . . . . . . . . . 32
Issue 1 August 2006 3
Contents
Static local configuration of the IP DECT base station . . . . . . . . . . . . . . . 33
802.1Q Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Avaya DECT Mobility Manager Requirements. . . . . . . . . . . . . . . . . . 35
ADMM running on an IP DECT base station . . . . . . . . . . . . . . . . . 35
ADMM running on a Linux Server . . . . . . . . . . . . . . . . . . . . . . 36
Principles and Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Why not VLAN ID 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
VLAN and the Boot Phase of a IP DECT base station. . . . . . . . . . . . . . 36
DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Local configuration of the IP DECT base stations. . . . . . . . . . . . . . 37
Configuring the Avaya DECT Mobility Manager . . . . . . . . . . . . . . . . . . . 37
Service Login procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Definition of the License IP DECT base stations . . . . . . . . . . . . . . 40
Get and add the License Key and PARK number . . . . . . . . . . . . . . 41
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
System settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Rebooting the ADMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
User Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Time zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
IP Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
IP DECT base station Configuration . . . . . . . . . . . . . . . . . . . . . . . 50
DECT configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
States of an IP DECT base station . . . . . . . . . . . . . . . . . . . . . . 52
IP Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Configuration of IP DECT handsets . . . . . . . . . . . . . . . . . . . . . . . 55
System Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Voice Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Media Server System Features . . . . . . . . . . . . . . . . . . . . . . . . 60
Digit Treatment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
TFTP based Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . 64
WML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Chapter 4: Avaya Communication Manager . . . . . . . . . . . . . . . . 67
Usage and Important Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
ACM system administration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4 Avaya IP DECT Installation, Administration, and Maintenance
Chapter 5: Functional description . . . . . . . . . . . . . . . . . . . . . 73
Registration of Avaya 3701 and Avaya 3711 . . . . . . . . . . . . . . . . . . . . . 73
WML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Pre-configured URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
User Input of URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
LDAP based Corporate Directory. . . . . . . . . . . . . . . . . . . . . . . . . 74
TFTP based Corporate Directory . . . . . . . . . . . . . . . . . . . . . . . . . 75
Message Waiting Indication for the 20DT Handset . . . . . . . . . . . . . . . . . 76
Avaya system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Avaya DECT Mobility Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Message sequence chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Chapter 6: Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Booter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Checking the IP DECT base station Booter Version . . . . . . . . . . . . . . 79
Manual Update of the IP DECT base station Booter. . . . . . . . . . . . . . . 80
Static local configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Checking the local configuration. . . . . . . . . . . . . . . . . . . . . . . . . 80
Removing the local configuration . . . . . . . . . . . . . . . . . . . . . . . . 81
Contents
Avaya 3701 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Checking the Avaya 3701 Firmware Version. . . . . . . . . . . . . . . . . . . 81
Upgrading the Avaya 3701 Firmware. . . . . . . . . . . . . . . . . . . . . . . 82
Avaya 3711 maintenance and diagnostic . . . . . . . . . . . . . . . . . . . . . . 85
Avaya 3711 Auto Call Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . 85
Avaya 3711 Auto Answer Test Mode . . . . . . . . . . . . . . . . . . . . . . . 86
Avaya 3711 Site Survey Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Avaya 3711 Master Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Change the Avaya 3711 Security PIN. . . . . . . . . . . . . . . . . . . . . . . 88
Avaya 3711 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Checking the Avaya 3711 Firmware Version. . . . . . . . . . . . . . . . . . . 88
Upgrading the Avaya 3711 Firmware. . . . . . . . . . . . . . . . . . . . . . . 89
Site Survey Measurement Equipment . . . . . . . . . . . . . . . . . . . . . . . . 92
Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Syslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Telnet user shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Command overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Issue 1 August 2006 5
Contents
IP DECT base station console commands . . . . . . . . . . . . . . . . . . 96
ADMM console commands . . . . . . . . . . . . . . . . . . . . . . . . . . 97
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
DECT Monitor of the Avaya IP DECT System . . . . . . . . . . . . . . . . . . 98
Appendix A: Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Supported Codecs and Codec negotiation . . . . . . . . . . . . . . . . . . . . . 103
MIB-II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
system (1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
interfaces (2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
at (3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
ip (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
icmp (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
tcp (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
udp (7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
egp (8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
cmot (9). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
transmission (10) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
snmp (11). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
WML Tags and Attributes supported. . . . . . . . . . . . . . . . . . . . . . . . . 121
Detailed overview:
Avaya IP Phones and the ADMM/Avaya 3711. . . . . . . . . . . . . . . . . . . . 122
Protocols and Ports used by Avaya IP DECT System. . . . . . . . . . . . . . . . 125
6 Avaya IP DECT Installation, Administration, and Maintenance
Chapter 1: Overview
Purpose
This document describes the installation and administration of the Avaya IP DECT solution
using Avaya DECT Mobility Manager version 1.x.x.
Abbreviations and Definitions
Abbreviations
AC Authentication Code
ACM Avaya Communication Manager
ADMM Avaya IP DECT Mobility Manager
ADPCM Adaptive Differential Pulse Code Modulation
CM Communication Manager
DECT Digital Enhanced Cordless
Telecommunication
DHCP Dynamic Host Configuration Protocol
DSP Digital Signal Processor
GAP Generic Access Profile
IPEI International Portable Equipment Identity
IP Base Station IP DECT Base Station
HTTP Hyper Text Transfer Protocol
MSSF Media Server System Features
OMM Open Mobility Manager (same as ADMM)
PARK Portable Access Rights Key
PP Portable Part (same as IP DECT handset)
RFP Radio Fixed Part (same as IP Base Station)
RTCP Real Time Control Protocol
Issue 1 August 2006 7
Overview
Definitions
RTP Real Time Protocol
TFTP Trivial File Transfer Protocol
VLAN Virtual Local Area Network
DECT Digital Enhanced Cordless Telecommunication
● 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 key technical characteristics are:
- Frequency range: approx. 1,880 – 1,900 GHz
(approx. 20 MHz bandwidth)
- 10 carrier frequencies (1,728 MHz spacing) with 12
time slots each *)
- Doubling the number of time slots (to 24) using the
TDMA process
- Net data rate per channel of 32 kbit/s (for voice
transmission using ADPCM)
- Voice coding using the ADPCM method
- Maximum transmission power of 10 mW
GAP 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 features. This standard was created in
order to allow telephones of different vendors to be
used on any type of DECT system. It thus represents
the smallest common denominator of all
manufacturer-specific variants of the DECT standard.
● An important limitation in the GAP standard is that
external handover is not possible. For this reason
connection handover is used, which is supported by
GAP terminals.
● The operation of GAP-capable telephones is
comparable to that of analogue terminals. For e xample,
features can be called up via ‘*’ and ‘#’ procedures.
Handover Handover
A handover is similar to roaming, but occurs during an
ongoing call. A handover normally takes place ”in the
background,” without disrupting the call (seamless handover).
8 Avaya IP DECT Installation, Administration, and Maintenance
IPEI International Portable Equipment Identity
● 13-digit identification code for telephones
● Example: 00019 0592015 3 (the final digit is the
checksum).
● The code is represented in decimal form.
● This code is globally unique.
PARK Portable Access Rights Key
Access code for the handset. This code determines whether a
telephone can access a particular DECT system. Used for
unique selection of the system at enrolment.
Handover DECT base station networking
While in motion, the telephone performs ongoing
measurements to determine which base station is best
received. The one that can be best received is defined as the
active base station. To prevent the telephone from rapidly
switching back and forth between two base stations that can
be almost equally well received, certain threshold values are
in effect. (similar to a Schmitt trigger circuit )
Purpose
References
1. The TFTP Protocol (Revision 2), RFC 1350, July 1992
2. Avaya – Open Mobility configuration settings; KI CTB006259
3. Product Requirements and System Architecture; Integrating DeTeWe IP DECT wireless into
Avaya Multi Vantage Solution utilising an IP infrastructure
4. Product Requirements and System Architecture; Integrating DeTeWe IP DECT wireless into
Avaya IP Office utilising an IP infrastructure
5. RFC 1156, Management Information Base for Network Management of TCP/IP-based
internets, May 1990
6. RFC 1213, Management Information Base for Network Management of TCP/IP-based
internets: MIB-II, March 1991
7. RFC 1450, Management Information Base for version 2 of the Simple Network
Management Protocol (SNMPv2), April 1993
8. http://www.simpleweb.org/ietf/mibs/index.html?sel=IETF
9. Avaya 3711 User Guide
10. Avaya 3701 User Guide
11. Avaya IP Telephone LAN Administrators Guide
Issue 1 August 2006 9
Overview
10 Avaya IP DECT Installation, Administration, and Maintenance
Chapter 2: Introduction
About the Avaya IP DECT Solution
The DECT over IP system comprises the following components :
● IP DECT Base Stations distributed over an IP network and offering DECT as a wireless
interface.
● ACM Media Server/Media Gateway as telephony system platforms
● DECT telephone: Avaya 3701 and Avaya 3711 wireless phones
● Avaya DECT Mobility Manager (ADMM): management interface for IP DECT Solution,
which runs on either one of the IP DECT Base stations or on a dedicated LINUX server
The following pictures give a graphical overview of the architecture of the Avaya IP DECT
solution:
Media Server
Media Gateway
Web B rowser for
administration purposes
IP DECT Base
Stations
256 max.
The Media Server, Media Gateway, ADMM and the IP DECT base stations communicate
through the IP infrastructure. The IP DECT base stations and the IP DECT handsets
communicate over air, where the DECT GAP protocol is used or DECT GAP with proprietary
enhancements.
Issue 1 August 2006 11
Introduction
About the IP DECT base stations
All IP DECT base stations have the same hardware and software capabilities.
One of the IP DECT base stations within an IP DECT installation may be chose n to opera te not
in the IP DECT base station only mode but in the Avaya DECT Mobility Manager (ADMM)
mode. During installation, you will set one of the IP DECT base stations to ADMM mode, or you
will use a dedicated LINUX server running as an ADMM. The others are in the IP DECT base
station only mode.
IP DECT base station only mode:
Within that mode, the IP DECT base station converts IP protocol to DECT protocol and then
transmits the traffic to and from the Handsets over a DECT timeslot. On air the IP DECT base
station has 12 time slots, eight can have associated DSP resources for media streams, the
remaining four time slots are used for example for control signalling between IP DECT base
stations and the Handsets or for bearer handover.
Groups of IP DECT base stations have to be built which are named Cluste r. Within a Cluster IP
DECT base stations are synchronised to enable a seamless hand over when a user crosses
from one IP DECT base station’s zone of coverage to another. For synchronisation it is not
necessary for an IP DECT base station to communicate directly with all other IP DECT base
stations in the system. Each IP DECT base station only needs to be able to communicate with
the next IP DECT base station in the chain. But it is preferable for an IP DECT base station to
see more than one IP DECT base station to guarantee synchronisation in the event that one of
the IP DECT base stations fails.
The four control signalling channels are also used to carry bearer signals that signal the
Handset to start the hand over process. If the radio signal of another IP DECT base station is
stronger than that of the current IP DECT base station, then the Handset starts the hand over
process to the IP DECT base station that has the stronger signal as the user moves around the
site.
Avaya IP DECT Mobility Manager (ADMM) mode:
In this mode, an IP DECT base station functions as a regular IP DECT base station. Additionally
it is responsible for H.323 signalling between the IP DECT system and the telephony or media
server. Further on it takes management part of the IP-DECT solution. You designate an IP
DECT base station as the ADMM by assigning an IP address to the IP DECT base st ation in the
DHCP scope (see Mandatory options
(see S t atic local configuration of the IP DECT base stat ion
station is designated as the ADMM, it starts the extra services on board (for example, the Web
Service that supports the management interface).
on page 29) or by setting the data via OM Configurator
on page 33). After an IP DECT base
12 Avaya IP DECT Installation, Administration, and Maintenance
Avaya DECT Mobility Manager
Note:
Note: It is possible to deactivate the DECT part of a IP DECT base station. If the DECT
Interface is deactivated then the resources (CPU and memory) are available for
the ADMM.
Light emitting diode (LED)
signalling of current operating state on the IP DECT Base Station
Ethernet jack
Power supply in line with Power over LAN™ standard IEEE 802.3af
Power jack (110 V/240 V AC adapter)
Avaya DECT Mobility Manager
The Avaya DECT Mobility Manager (ADMM) performs the following tasks:
● signalling gateway (H.323 <-> DECT GAP)
● media stream management
● manages synch over air functions between IP DECT base stations
● facilitates system configuration modifications
● provides additional services e.g.
- Corporate Directory (LDAP or TFTP based)
- WML browser
The Avaya DECT Mobility Manager (ADMM) may run on on e of the IP DECT base stat ion or on
a dedicated Linux Server.
Issue 1 August 2006 13
Introduction
IP signalling and media stream
To establish a call between an IP Phone and an DECT handset, the following IP streams must
be established:
● a signalling channel to and from the IP phone
● a signalling channel to and from the ADMM
● a control interface between the ADMM and the IP DECT base station that has a
connection to the DECT handset (known as the primary IP DECT base station)
a Real Time Protocol (RTP) / Real Time Control Protocol (RTCP) connection between the IP
Phone and the Media Gateway and then a RTP/RTCP connection between the Me dia Gateway
and the IP DECT base station.The following figure illustrates this scenario.
IP-Phone
Media Gateway
Media Server
ADMM
(IP DECT Base Station
in ADMM mode)
Primary Base
Station
Signalling
Base Station Control
RTP/RTCP
14 Avaya IP DECT Installation, Administration, and Maintenance
IP signalling and media stream
)
To establish a call between two DECT handsets the same IP streams must be established like
in the scenario before, except the IP phone is not involved. The following figure illustrates this
scenario.
Media Server
Media Gateway
ADMM
(IP DECT Base Station
in ADMM mode
Signalling
Base Station Control
RTP/RTCP
A call from one DECT handset to another that resides on the same IP DECT base station will
loop back within the IP DECT base station, 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.
It is also be possible to direct the media stream to connect directly the IP phone and the IP
DECT base station, as shown in the following figures.
Issue 1 August 2006 15
Introduction
If the DECT handset user is moving, the handset detects that anot her IP DECT base station has
a better signal strength and, therefore, it starts the hand over process. The media stream from
the IP Phone cannot move to the secondary IP DECT base station, so the primary IP DECT
base station uses the LAN to direct the voice to the secondary IP DECT base station, as shown
in the following figure.
IP-Phone
Media Server
Media Gateway
ADMM
(IP DECT Base Station
in ADMM mode)
Signalling
Base Station Control
RTP/RTCP
Secondary Base
Station
Primary Base
Station
16 Avaya IP DECT Installation, Administration, and Maintenance
IP DECT base station Synchronisation
As the DECT set user moves into the next IP DECT base station zone of coverage, the DECT
set detects that the IP DECT base station has a better signal strength. Ag ain, the media stream
from the IP phone cannot move to the secondary IP DECT base station, so the primary IP
DECT base station uses the LAN to direct the voice to the new secondary IP DECT base
station.
IP-Phone
Media Server
Media Gateway
New secondary Base
Station
ADMM
(IP DECT Base Station
IP DECT base station Synchronisation
To guarantee a seamless hand over if a caller moves from one IP DECT base station zone of
coverage to another IP DECT base station zone of coverage, an accurate synchronisation of
the IP DECT base stations is necessary.
The IP DECT base stations are synchronised over the air interface. During start-up, one IP
DECT base station will be the first, which transmits a signal on the air. The other IP DECT base
stations only receiving the signal until their are synchronous. If a IP DECT base station gets in
synch then it will transmit a signal on the air and will be the synch source for the next IP DECT
base stations. Only IP DECT base stations which can receive each other will be synchronised.
Primary Base
Station
Signalling
Base Station Control
RTP/RTCP
For the IP DECT base station to sync to another IP DECT base station the signal strength
cannot drop below –70 dBm. You must consider this requirement during the site survey.
Issue 1 August 2006 17
Introduction
The first active IP DECT base station will be chosen by the ADMM as the Master for the
synchronisation. If a specific IP DECT base station shall be used, for example to speed-up the
synchronisation phase, then a IP DECT base station can be marked with ‘Act as Master during
startup’ on the IP DECT base station Web page.
Unsynchronised RFP,
which does not receive a
R 101 R 102 R 103 R 104 R 105
signal from another RFP
Unsynchronised RFP,
which receives a signal
from another RFP and
tries to get synchronised
Synchronised RFP,
which receives and
transmits a signal on the
air interface
R 111 R 110 R 109 R 108
R 107
R 106
As long as a IP DECT base station is not in synch, no calls can be established using this IP
DECT base station.
If a IP DECT base station loses the synchronisation the IP DECT base station does not accept
new calls ("Busy-Bit"). There is a delay of max. 3 minutes until the active calls on this IP DECT
base station are finished. Then it tries to get synchronised again.
18 Avaya IP DECT Installation, Administration, and Maintenance
IP DECT base station Synchronisation
An IP DECT installation is more reliable if a IP DECT base station can receive the signal from
more than only one IP DECT base station, because the other signals are also used for
synchronisation.
Unreliable Installation
R 101 R 102 R 103 R 104 R 105
Don‘t
R 111 R 110 R 109 R 108
R 107
Reliable Installation
R 101 R 102 R 103 R 104 R 105
R 106
R 111 R 110 R 109 R 108
R 107
R 106
The synch-over-air solution is very reliable, because all existing redundant paths are used for
synchronisation. Thus, hardware tolerances have only very little influence. No IP DECT base
station has a key position. Example: If the Initial Master does not start up, another IP DECT
base station will be chosen by the ADMM.
Only unfavourable setups without redundant synchronisation paths can cause problems.
Sometimes IP DECT base stations do not need to be synchronized, e.g. if they are in different
buildings. These IP DECT base stations can be put into different clusters. IP DECT base
stations in different clusters will not be synchronised with each other. Different cluster start up
independent at the same time.
Issue 1 August 2006 19
Introduction
IP DECT base station channel capacity
The IP DECT base station has 12 available airtime slots:
● eight can have associated DSP resource for media streams
● the remaining four time slots are used for example for control signalling b etween IP DECT
base stations and the Handsets or for bearer handover
If all eight Media Stream channels are used IP DECT announces a ‘Busy Bit’. In that case the
DECT sets determine whether another IP DECT base station has an appropriate signal
strength. If so, the DECT set will hand over to that IP DECT base station. Once the hand over
has been completed, the IP DECT base station will then lower its Busy Bit.
When ever 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 IP DECT base station should be
installed to double the number of media streams available for calls.
About the Handsets
There are two models of Handsets: the Avaya 3711 and the Avaya 3701. A detailed description
of the two phones an their local features is available with Avaya 3711 User Guide and Avaya
3701 User Guide.
Also Avaya Kirk DECT phones (WT9620 and DT20) and st andard 3
function on the IP DECT solution. But the functionality may be limited by the characteristics of
rd
the 3
administration.
party DECT phone. The 3rd party DECT phones need to provide the IPEI for
rd
party DECT GAP phones
20 Avaya IP DECT Installation, Administration, and Maintenance
About Licensing
The ADMM needs to be enabled with a license key, which depends on the MAC address of
some IP DECT base stations in the DECT system. The license key needs to be entered /
administered via the ADMM web administration interface.
There are a sets of licenses with additional upgrade licenses .
● License for 1 IP DECT base station
● License for 2 IP DECT base stations
● License for 3 to 5 IP DECT base stations
● License for more than 5 IP DECT base stations
As mentioned above the license key depends on the MAC addresses of some IP DECT base
stations of the DECT system (License-IP DECT base stations). Each IP DECT base station can
be an License-IP DECT base station independently where the IP DECT base station is located.
The number of IP DECT base station MAC addresses encoded in the license depends on the
size of the DECT installation.
About Licensing
System size
(# of IP DECT base
stations)
Number of IP DECT base station MAC addresses
encoded in the license (License-IP DECT base
stations)
11
22
3 to 5 3
6 or more (6+) 3
Additionally to the MAC addresses the PARK (Portable Access Rights Key), which identifies the
DECT installation, is also by part of the license. Because a DECT system can only be operated
with a valid PARK, a DECT installation without a license will be inactive on the DECT site.
An IP DECT system is operational, if it set up with a license and the IP DECT base stations,
which are encoded in the license are part of the system so that the ADMM can communicate
with these License-IP DECT base stations.
Issue 1 August 2006 21
Introduction
Depending on the size of the IP DECT system, it will still work if some License-IP DECT base
stations are out of service.
System size
(# of IP
Number of License-IP DECT
base stations
DECT base
stations)
11 1
22 1
3 to 5 3 2
6 or more
32
(6+)
If the minimum number of License-IP DECT base stations can not be reached by the ADMM or
more IP DECT base stations are administered than licensed the DECT system will block the
voice streams.
System Capacities
There is only one Avaya DECT Mobility Manager (ADMM) in the system. The capacities are
depending on the platform, the ADMM is running on.
Number of License-IP DECT base
stations available at minimum
ADMM running on a IP DECT base station:
● up to 256 IP DECT base stations can be controlled
● up to 400 handsets are handled
● up to 100 handsets can be active simultaneously
It is possible to deactivate the DECT part of a IP DECT base station. If the DECT Interface is
deactivated then the resources (CPU and memory) are available for the ADMM only.
ADMM running on a Linux Server:
● up to 256 IP DECT base stations can be controlled
● up to 16.320 handsets are handled
● up to 1500 handsets can be active simultaneously (theoretical maximum is 2048 but this is
not practical because of handovers)
22 Avaya IP DECT Installation, Administration, and Maintenance
Chapter 3: Installation and Configuration
To establish and maintain a IP DECT installation, a network infrastructure is assumed, which
comprises at least the following components:
● IP DECT base stations, IP DECT handsets and ACM Media Server
● a Redhat Enterprise 4.0 ES Linux Server, if it is decided not to run the Avaya DECT
Mobility Manager on a IP DECT base station
● a TFTP Server
Depending on the operational modes the following services should be provided:
● DHCP
● SNTP
● DNS
● WML/HTTP
● LDAP
● Syslog daemon
Avaya IP DECT system start up
Startup of the IP DECT base stations
For booting an IP DECT base station there must at least a TFTP-Server on the attached
network to load the application software.
The essential network settings can be given alternatively
● given by a DHCP Server at startup time.
● can be configured on the IP DECT base station with the tool OM-Configurator. The
settings made by OM-Configurator will be saved permanently in the internal flash memory.
The IP DECT base station gets the boot image file from a TFTP server. The used TFTP server
needs to support RFC 1350, The TFTP Protocol (Revision 2), July 1992.
The used DHCP server needs to support RFC 2131, Dynamic Host Configuration Protocol,
March 1997.
The TFTP and DHCP server need not to reside on the same host.
Issue 1 August 2006 23
Installation and Configuration
Booting Overview
Booting can be in two steps:
● Starting the boot process
● Starting the application
Booter:
The IP DECT base station has only a little standalone application built into the flash. This
software realises the so called NETBOOT process.
On start up each IP DECT base station try to determine its own IP address and other settings of
the IP interface from the configuration settings in the internal flash memory. When no settings
are available or these settings are disabled, the IP DECT base station try to determine this
settings via DHCP.
The IP DECT base station gets the application image file from the TFTP server.
Application:
After starting the application image the IP DECT base station checks the local network settings
in his internal flash memory once again. When no settings are available or they are disabled it
starts a DHCP client to determine the IP address of the ADMM and other start up settings.
Startup of Avaya IP DECT Mobility Manager
ADMM in IP DECT base station mode
There is no difference in booting that IP DECT base station, which is chosen to be running in
ADMM mode from those which are in the IP DECT base station only mode.
The decision is driven by the ADMM IP address, which is read:
● within the local network settings, if active.
● via DHCP request.
That IP DECT base station which has the same IP address as the ADMM IP address, is running
as the ADMM.
ADMM in Host-Mode
In this case the ADMM Software has to be installed on PC running with Linux Red Hat. The
essential network settings the ADMM is working with are depending on the configuration of the
PC Kernel.
24 Avaya IP DECT Installation, Administration, and Maintenance
Once started, the ADMM is running permanently while not stopped and when ever the PC is
running. In case of fatal errors or PC reboot, the OM recovers automatically.
!
CAUTION:
CAUTION: Be sure that the versions of the ADMM and the IP DECT base station software
within your IP DECT installation are the same.
Installing the ADMM software
The ADMM software is available as a Red Hat Package File (RPM). You have to login as root
user, if you are going to install the ADMM.
● For first installation of the ADMM type: rpm –i
omm_avaya-<version-date>.i586.rpm.
● To ugrade the ADMM by a new version type: rpm –U
omm_avaya-<version-date>.i586.rpm.
● To delete the ADMM installation type: rpm –e omm_avaya.
● If you like to verify the installation type rpm –qi omm_avaya.
Avaya IP DECT system start up
After the install procedure you can start the ADMM with the command:
/etc/init.d/omm_avaya start
Configure Start Parameter
Some basic data for initializing the ADMM are stored in the file "/etc/sysconfig/omm_avaya”. It
has to be edited, if you like to change the interface of the ADMM :
##############################################
# OMM configuration file
##############################################
# if you use a different interface for omm_avaya activate parameter below
#OMM_IF="eth0"
OMM_CONFIG_FILE="/etc/omm_conf.txt"
Parameter Description
OMM-IF Interface for communication with IP DECT base station’s (default:eth0)
OMM_CONFIG_FILE Configuration file for ADMM (default: /etc/omm_conf.txt)
Issue 1 August 2006 25
Installation and Configuration
To maintain the running ADMM on PC
The ADMM is installed as a daemon and runs automatically at system start.
You can start and stop the ADMM on a shell as user root with the command:
/etc/init.d/omm_avaya [start|stop|restart]
You can log to the ADMM command line interface via telnet on port 8107.
T roubleshooting:
● To verify if the ADMM is running look at process table (ps –e) for the process omm_avaya.
● If the ADMM does not start, delete the lock file: "/var/lock/subsys/omm_avaya”.
● To delete ADMM configuration remove the OMM_CONFIG_FILE (default: /etc/
omm_conf.txt).
Booter
Booter versions
This documentation referring to IP DECT for Avaya is written for the Booter SW 3.2.x.
But note, in test installations there may be some different versions of the booter SW in use:
● Booter version 2.1.y
This software is using BOOTP instead of DHCP.
● Booter version 3.0.x
Replacement of the BOOTP client by a DHCP client.
● Booter version 3.1.x
Added support for VLAN.
● Booter version 3.2.x
added support for OpenMobility Configuration tool.
See Booter update
DHCP client
Within the initial boot process the DHCP client supports the following parameters:
● IP Address mandatory
● Netmask mandatory
on page 29 for details on the booter update mechanism.
● Gateway mandatory
● Boot file name mandatory
26 Avaya IP DECT Installation, Administration, and Maintenance
● TFTP server mandatory
● Public Option 224: "OpenMobility” mandatory
● Public Option 225: VLAN ID optional
Note:
Note: If local configuration via OM Configurator is set, these information will be read
from internal flash memory instead.
DHCP REQUEST
Vendor class identifier (code 60)
The DHCP client sends the vendor class identifier "OpenMobility”.
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)
Avaya IP DECT system start up
● Router option (code 3)
● Public option 224 (code 224)
● Public option 225 (code 225)
● Public option 226 (code 226)
DHCP OFFER
Mandatory options
The DHCP client selects the DHCP server according to the following rules:
● One of the public options (code 224 up to code 254) has a value equal to the string
"OpenMobility”. It is recommended to use public option 224 for this, because the DHCP
client in the application checks for this option.
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
● the IP netmask is taken from the subnet mask option (code 1)
● the default gateway is taken from the router option (code 3)
Issue 1 August 2006 27
Installation and Configuration
● the TFTP server IP address is taken from the siaddr field in the DHCP message
● the boot image filename is taken from the file field in the DHCP message, if this field is
empty the default filename "iprfp.bin” is used.
Optional options
● Public option 225 (code 225) with a length of 2 byte is interpreted as VLAN ID.
If this option is present the booter will start over with releasing the current lease and
issuing a new DHCP REQUEST, now using VLAN.
Retries
If the DHCP client does not get an appropriate DHCP OFFER a new DHCP REQUEST is send
after 1 second. After 3 DHCP REQUESTS are send the DHCP client will sleep for 60 seconds.
During this time the booter will accept local configuration from the OpenMobility Configurator
tool.
TFTP client
The TFTP client will download the application image from the TFTP server. Both TFTP server
and the name of the application image are supplied via the DHCP client. The ap plication image
is checksum protected.
Application
After successfully downloading and starting the application the IP DECT base station will
determine the IP-address of the ADMM from DHCP.
The DHCP client is capable to receive broadcast and unicast DHCP replies. The flags field is
therefore 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:
● Public Option 226: ADMM IP Address mandatory
● Public Option 227: Syslog server IP Address optional
● Public Option 228: Syslog server port optional
● DHCP Option 6: Domain Name Server optional
● DHCP Option 15: Domain Name optional
● DHCP Option 42: Network Time Protocol Server optional
28 Avaya IP DECT Installation, Administration, and Maintenance
Note:
Note: If local configuration via OM Configurator is set, these information will be read
from internal flash memory instead.
Booter update
Automatic booter update
Each application SW comes with the latest released booter SW. The applicat ion SW will update
the booter automatically as long as the major release number of the booter SW has not
changed, e.g booter SW 2.1.2 will not be automatically updated by booter SW 3.x.y, but booter
SW 3.0.0 will be automatically updated by booter SW 3.1.0.
Avaya IP DECT system start up
Details on how to check the booter SW version, see Booter
Details on how to update the booter manually, see Manual Update of the IP DECT base station
Booter on page 80.
Automatic booter update for major release changes
The booter update of booters with 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".
Selecting the right DHCP Server
The DHCP client request its own IP address using code 50. The DHCP client will selects the
DHCP server that offers the currently used IP address. Additionally the mandatory options must
be offered otherwise the DHCP OFFER is ignored by the DHCP client.
If no matching reply was received the DHCP client resends the request for 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 IP DECT base station is
rebooted.
Mandatory options
on page 26.
Magic string
● Public option 224
The value of this option must be "OpenMobility”
ADMM IP address
● Public option 226
The value is interpreted as ADMM IP address, the length must be 4 byte.
Issue 1 August 2006 29
Installation and Configuration
Optional options
Syslog server IP address and port
● Public option 227
The value is interpreted as the IP address of the syslog server, the length must be 4 byte.
● Public option 228
The value is interpreted as the port the syslog server is listening. T he length must be 2 byt e.
DHCP Option 6: Domain Name Server
The domain name server option specifies a list of Domain Name System name servers
available to the client.
Servers SHOULD be listed in order of preference. The code for the domain name server option
is 6.
The minimum length for this option is 4 octets, and the length MUST always be a multiple of 4.
Code Len Address 1 Address 2
+-----+-----+-----+-----+-----+-----+-----+-----+-| 6 | n | a1 | a2 | a3 | a4 | a1 | a2 | ...
+-----+-----+-----+-----+-----+-----+-----+-----+--
DHCP Option 15: Domain Name
This option specifies the domain name that client should use when resolving hostnames via the
Domain Name System.
The code for this option is 15. Its minimum length is 1.
Code Len Domain Name
+-----+-----+-----+-----+-----+-----+-| 15 | n | d1 | d2 | d3 | d4 | ...
+-----+-----+-----+-----+-----+-----+--
DHCP Option 42: Network Time Protocol Servers
This option specifies a list of IP addresses indicating NTP servers available to the client.
Servers SHOULD be listed in order of preference.
The code for this option is 42. Its minimum length is 4, and the length MUST be a multiple of 4.
Code Len Address 1 Address 2
+-----+-----+-----+-----+-----+-----+-----+-----+-| 42 | n | a1 | a2 | a3 | a4 | a1 | a2 | ...
+-----+-----+-----+-----+-----+-----+-----+-----+--
30 Avaya IP DECT Installation, Administration, and Maintenance
Loading...