Avaya Communication Manager IP DECT Instruction 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 information 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 and search for the document number in
the search box.
Documentation disclaimer
Avaya Inc. is not responsible for any modifications, additions, 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 information described or offered
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 warranty. 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 copyright
and other laws respecting proprietary rights. Unauthorized reproduction,
transfer, and or use can be a criminal, as well as a civil, offense under the
applicable law.
Avaya support
Avaya provides a telephone number for you to use to report problems or to 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.

Issue 1 August 2006 3
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
Contents

Contents
4 Avaya IP DECT Installation, Administration, and Maintenance
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

Contents
Issue 1 August 2006 5
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
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

Contents
6 Avaya IP DECT Installation, Administration, and Maintenance
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

Issue 1 August 2006 7
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

Overview
8 Avaya IP DECT Installation, Administration, and Maintenance
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 example,
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).

Purpose
Issue 1 August 2006 9
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
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 )

Overview
10 Avaya IP DECT Installation, Administration, and Maintenance

Issue 1 August 2006 11
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:
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.
IP DECT Base
Stations
256 max.
Web Browser for
administration purposes
Media Server
Media Gateway

Introduction
12 Avaya IP DECT Installation, Administration, and Maintenance
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 chosen to operate 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 Cluster. 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 station in the
DHCP scope (see Mandatory options on page 29) or by setting the data via OM Configurator
(see Static local configuration of the IP DECT base station on page 33). After an IP DECT base
station is designated as the ADMM, it starts the extra services on board (for example, the Web
Service that supports the management interface).

Avaya DECT Mobility Manager
Issue 1 August 2006 13
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.
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 one of the IP DECT base station or on
a dedicated Linux Server.
Power jack (110 V/240 V AC adapter)
Ethernet jack
Power supply in line with Power over LAN™ standard IEEE 802.3af
Light emitting diode (LED)
signalling of current operating state on the IP DECT Base Station

Introduction
14 Avaya IP DECT Installation, Administration, and Maintenance
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 Media Gateway
and the IP DECT base station.The following figure illustrates this scenario.
Media Server
Media Gateway
Signalling
Base Station Control
If
RTP/RTCP
IP-Phone
ADMM
(IP DECT Base Station
in ADMM mode)
Primary Base
Station

IP signalling and media stream
Issue 1 August 2006 15
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.
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.
Media Server
Media Gateway
Signalling
Base Station Control
If
RTP/RTCP
ADMM
(IP DECT Base Station
in ADMM mode
)

Introduction
16 Avaya IP DECT Installation, Administration, and Maintenance
If the DECT handset user is moving, the handset detects that another 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.
Media Server
Media Gateway
Signalling
Base Station Control
If
RTP/RTCP
IP-Phone
ADMM
(IP DECT Base Station
in ADMM mode)
Primary Base
Station
Secondary Base
Station

IP DECT base station Synchronisation
Issue 1 August 2006 17
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. Again, 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 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.
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.
Media Server
Media Gateway
Signalling
Base Station Control
It f
RTP/RTCP
IP-Phone
ADMM
(IP DECT Base Station
in ADMM mode)
Primary Base
Station
New secondary Base
Station

Introduction
18 Avaya IP DECT Installation, Administration, and Maintenance
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.
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.
R 111 R 110 R 109 R 108 R 106
R 101 R 102 R 103 R 104 R 105
R 107
Unsynchronised RFP,
which does not receive a
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

IP DECT base station Synchronisation
Issue 1 August 2006 19
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.
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.
R 111 R 110 R 109 R 108 R 106
R 101 R 102 R 103 R 104 R 105
R 107
Unreliable Installation
R 111 R 110 R 109 R 108 R 106
R 101 R 102 R 103 R 104 R 105
R 107
Reliable Installation
Don‘t

Introduction
20 Avaya IP DECT Installation, Administration, and Maintenance
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 between 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 standard 3rd party DECT GAP phones
function on the IP DECT solution. But the functionality may be limited by the characteristics of
the 3rd party DECT phone. The 3rd party DECT phones need to provide the IPEI for
administration.