Avaya SIP DECT Fundamentals - Communication Server 1000 User Manual

SIP DECT Fundamentals
A

vaya Communication Server 1000

NN43120-123, Standard 04.06

7.5

October 2012

©

Avaya Inc.

2010

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.

Documentation disclaimer

Avaya shall not be 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.
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 End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation(s) provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.

Warranty

Avaya 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 to Avaya
customers and other parties through the Avaya Support Web site:

http://www.avaya.com/support. Please note that if you acquired the

product from an authorized
and Canada, the warranty is provided to you by said Avaya reseller and
not by Avaya.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE,
APPLICABLE
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN A V A Y A, AN A V A Y A AFFILIA TE OR AN
AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE
RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE
ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.
BY INST ALLING, DOWNLOADING OR USING THE SOFTW ARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABL Y AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).

Copyright

Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation(s) and Product(s) provided
by Avaya. All content on this site, the documentation(s) and the
product(s) provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is

HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE

TO ANYONE WHO DOWNLOADS, USES AND/OR

Avaya reseller outside of the United States

protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases.
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software. Unauthorized reproduction, transmission, dissemination,
storage, and or use without the express written consent of Avaya can
be a criminal, as well as a civil, offense under the applicable law.

Third-party components

Certain software programs or portions thereof included in the Product
may contain software distributed under third party agreements (“Third
Party Components”), which may contain terms that expand or limit
rights to use certain portions of the Product (“Third Party Terms”).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the Avaya Support
Web site:

Preventing toll fraud

“T
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there can be a risk of toll fraud associated with
your system and that, if toll fraud occurs, it can result in substantial
additional charges for your telecommunications services.

Avaya fraud intervention

If you suspect that you are being victimized by toll fraud and you need
technical assistance or support, call Technical Service Center Toll
Fraud Intervention Hotline at [phone] for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site:
vulnerabilities with
sending mail to: [e-mail].

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in this
site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the documentation(s) and product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.
All other trademarks are the property of their respective owners.

Downloading documents

For the most current versions of documentation, see the Avaya Support
Web site:

Contact

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:

support

http://www.avaya.com/support/Copyright/.

oll fraud” is the unauthorized use of your telecommunications system

http://www.avaya.com/support/. Suspected security

Avaya products should be reported to Avaya by

http://www.avaya.com/support

Avaya Support

http://www.avaya.com/

You may not

2 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Contents

Chapter 1: New in this release...........................................................................................

Features....................................................................................................................................................

Revision History........................................................................................................................................

Chapter 2: Product overview.............................................................................................

Navigation.................................................................................................................................................

Overview of Avaya SIP DECT...................................................................................................................

Universal extension support......................................................................................................................

DECT Handset features............................................................................................................................

CallPilot and Message Waiting Indication support....................................................................................

SIP DECT capacity limitations..................................................................................................................

Chapter 3: Site planning and hardware deployment.......................................................

Navigation.................................................................................................................................................

Components of SIP DECT systems..........................................................................................................

Types of SIP DECT configuration.............................................................................................................

Site planning.............................................................................................................................................

System deployment...................................................................................................................................

Chapter 4: Software requirements....................................................................................

Navigation.................................................................................................................................................

Call Server and SIP Line Gateway software.............................................................................................

DAP controller software............................................................................................................................

Chapter 5: System configuration.......................................................................................

Navigation.................................................................................................................................................

Basic (simple) SIP DECT configuration with Communication Server 1000 SIP Line Gateway................

Branch Office configuration..............................................................................................................

Routed Head Quarter configuration..........................................................................................................

Routed Head Quarter Configuration with Branch Office...................................................................

Multiple-site mobility network configuration...............................................................................................

Multiple Gatekeepers Configuration.................................................................................................

Chapter 6: System administration.....................................................................................

Navigation.................................................................................................................................................

DAP manager overview............................................................................................................................

Subscription management........................................................................................................................

DAP management.....................................................................................................................................

Add a DN range........................................................................................................................................

System backup..........................................................................................................................................

Subscription export and import.................................................................................................................

DAP reboot history....................................................................................................................................

System archive..........................................................................................................................................

Handset firmware update..........................................................................................................................

Central Directory access tool....................................................................................................................

Chapter 7: System maintenance........................................................................................

Navigation.................................................................................................................................................

DAP Web interface....................................................................................................................................

C4710 DAP LED indications.....................................................................................................................

7
7
7

9
9
9
12
13
14
15

17
17
17
28
33
40

75
75
75
75

93
93
93
107
109
111
113
117

121
121
121
123
129
132
133
134
137
137
138
142

147
147
147
149

SIP DECT Fundamentals October 2012 3

4720 DAP LED indications........................................................................................................................

DAP firmware update................................................................................................................................

Remove and replace a DAP (if a new DAP is available)..........................................................................

Remove and replace a DAP (if a new DAP is not available)....................................................................

System synchronization analysis..............................................................................................................

Export and import SIP DECT system........................................................................................................

DAP Controller deactivation......................................................................................................................

Uninstalling DAP Controller software...............................................................................................

DAP Controller software update.......................................................................................................

Troubleshooting........................................................................................................................................

If you have problems.................................................................................................................................

Appendix A: G.729 daughterboard and DAP wall mounting...........................................

Navigation.................................................................................................................................................

Mount the G.729 daughterboard...............................................................................................................

Adjusting the antenna position..................................................................................................................

Mounting the 4720 DAP on a wall.............................................................................................................

Appendix B: Location builder tool....................................................................................

Use the Location builder tool....................................................................................................................

Create a location file.................................................................................................................................

Maintenance..............................................................................................................................................

Appendix C: Site survey example.....................................................................................

Site planning example: Able-Studio..........................................................................................................

Appendix D: Deployment tool............................................................................................

Prepare the tool for deployment................................................................................................................

How the deployment tool works................................................................................................................

Using the deployment tool........................................................................................................................

Appendix E: Install the external housing..........................................................................

Installing 4720 DAP with internal antennas..............................................................................................

Installing a 4720 DAP with external antennas..........................................................................................

Installing a C4710 DAP in an external housing.........................................................................................

Installing a C4710E DAP in an external housing with an external antenna..............................................

Mounting the cabinet on a wall.................................................................................................................

Mounting the cabinet on a pole.................................................................................................................

Appendix F: Upgrade a SIPN connection to a SIPL connection.....................................

SIPL deployment.......................................................................................................................................

Convert SIPN/SIP3 TNs to SIPL UEXT TNs.............................................................................................

SIP DECT system upgrade.......................................................................................................................

Appendix G: Third Party Software.....................................................................................

SRTP.........................................................................................................................................................

TLS............................................................................................................................................................

Appendix H: DECT Handset Configurator Tool................................................................

Requirements............................................................................................................................................

Installation.................................................................................................................................................

Main operations.........................................................................................................................................

Operations with an image file...........................................................................................................

Operations with a MEM card............................................................................................................

Handset subscription........................................................................................................................

149
150
151
152
153
165
166
167
168
169
171

175
175
175
177
180

183
191
193
198

199
199

205
207
214
215

217
217
222
228
230
232
233

235
236
237
237

239
239
240

243
243
243
244
244
245
247

4 SIP DECT Fundamentals October 2012

Feature configuration................................................................................................................................

Messaging........................................................................................................................................

Contacts...........................................................................................................................................

Settings............................................................................................................................................

Calls.................................................................................................................................................

Calendar and Accessories...............................................................................................................

Feature selection.......................................................................................................................................

Broadcast Groups.....................................................................................................................................

Appendix I: DAP multicast group membership................................................................

DECT Access Point network interface......................................................................................................

Multicast configuration..............................................................................................................................

The IGMP snooping problem....................................................................................................................

The IGMP snooping solution.....................................................................................................................

Multicast host behavior of a DAP..............................................................................................................

Appendix J: DECT Messaging and Location Service......................................................

Installation.................................................................................................................................................

Configuration.............................................................................................................................................

Index.....................................................................................................................................

249
249
250
251
253
253
253
257

259
259
260
261
261
262

267
267
268
269

SIP DECT Fundamentals October 2012 5

6 SIP DECT Fundamentals October 2012

Chapter 1: New in this release

The following sections describe what’
Communication Server 1000 Release 7.5.

Features on page 7

•

• Revision History on page 7

s new in this document for DECT Release 5.2 and Avaya

Features

Release 5.20.091 for Communication Server 1000 Release 7.5 introduces the following:

DECT

• additional information about G.729 codec

• new Messaging and Location Service

Revision History

Date Description

October 2012 Standard 04.06. This document is up-issued to update configuration

information for optional SIP

configuration settings.

October 2011 Standard 04.05. This document is up-issued to support SIP DECT

5.20.091 and Avaya Communication Server 1000 Release 7.5.

June 2011 Standard 04.04. This document is up-issued to support SIP DECT 5.2

and Avaya Communication Server 1000 Release 7.5.

November 2010 Standard 04.03. This document is published to support Avaya

Communication Server 1000 Release 7.5.

November 2010 Standard 04.01 and 04.02. This document is up-issued to support Avaya

Communication Server 1000 Release 7.5.

June 2010 Standard 03.01. This document is up-issued to support Avaya

Communication Server 1000 Release 7.0.

March 2010 Standard 02.02. This document is up-issued with information for SIP

DECT on SIP LINE, and to support Communication Server 1000 (CS

1000) Release 6.0.

SIP DECT Fundamentals October 2012 7

New in this release

October 2009 Standard 02.01. This document is up-issued to reflect changes in

January 2009 Standard 01.07. This document is up-issued for Communication Server

December 2008 Standard 01.06. This document is up-issued for Communication Server

July 2008 Standard 01.05. This document is up-issued in response to change

July 2008 Standard 01.04. This document is up-issued in response to change

May 2008 Standard 01.03. This document is up-issued in response to change

March 2008 Standard 01.02. This document is up-issued in response to change

Date Description

technical content stemming from SIP

DECT 4.2, and to support

Communication Server 1000 Release 6.0.

1000 Release 5.5 with editorial changes.

1000 Release 5.5, in response to change requests for content related to
SIP DECT 4.1.

requests.

requests.

requests.

requests.

February 2008 Standard 01.01. This is a new document issued to support

Communication Server 1000 Release 5.5. Some of the information in this
new document was previously contained in the following document:
DECT Fundamentals, NN43120-114.

8 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Chapter 2: Product overview

This section describes the capabilities, configuration, and design of
Communication Server 1000 (Avaya CS 1000).

Navigation

• Overview of Avaya SIP DECT on page 9

Overview of Avaya SIP DECT

ou can use Avaya Session Initiation Protocol (SIP) Digital Enhanced Cordless

Y
T elecommunications (DECT) to move without restriction about your work site while conducting
telephone conversations, using wireless handsets. The Avaya SIP DECT system includes one
or more DECT access points (DAPs or basestations) connected to the TLAN.

The system supports the following connection types for SIP DECT configuration:

• SIPL configuration, which uses SIP Line Gateway

A minimal SIP DECT system has the following main components.

Avaya SIP DECT for Avaya

• Call Server

• SIP Line Gateway

• PC with DAP controller software installed

• DAP

• DECT Handset

Use the following tools to configure SIP DECT.

• Element Manager or overlay program for Call Server

• Element Manager for SIP Line Gateway

• IP DECT Configurator—used to enter SIP DECT configuration

• DAP Manager (IP DECT Manager)—a Web interface used for SIP DECT administration
tasks such as adding a handset or removing a subscription.

The IP DECT Configurator and the DAP manager IP DECT are available as a part of the DAP
controller software package.

SIP DECT Fundamentals October 2012 9

Product overview

The following software releases are required for the main system components:

You can connect IP Deskphones to the TLAN, and you can connect TDM telephones to the
Call Server, Voice Gateway Media Cards, and other required cards in the Call Server. Use
Voice Gateway Media Cards for IP-to-TDM calls and for conference calls involving IP
Deskphones or DECT Handsets on basestations. The configuration can also include a PC with
DECT Messenger to provide the DECT messaging service on SIP DECT.

Use the Dynamic Host Control Protocol (DHCP) server or the Trivial File Transfer Protocol
(TFTP) server unless you use a DAP configuration without DHCP or TFTP. You can configure
the system to use two separate servers: one for DHCP and the other for TFTP. If the system
requires DAP configuration without DHCP or TFTP, the DHCP or TFTP server is required
during installation or configuration changes.

The following figure shows a general SIP DECT configuration.

Call Server, Release 7.5 or later

•

• SIP Line Gateway application, Release 7.5 or later

• DAP software 4910b524.dwl or later

• DAP controller 5.2 or later (PC software)

10 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Overview of Avaya SIP DECT

Figure 1: SIP DECT configuration

ou can install the DHCP or TFTP services, DECT Messenger , and DAP controller on a single

Y
server or PC. However, you can also install them on separate servers to enhance performance
or facilitate administration.

Y ou connect the DAP to the Communication Server 1000 (CS 1000) using the SIP Line trunks
that you configure for SIP Line Gateway

Each DAP communicates with the subscribed DECT handsets in the coverage area, and each
DAP interacts with the CS 1000 and with other configured DAPs in the company network.

You can run SIP DECT on the following configurations:

• Communication Server 1000M or Communication 1000E

• SIP Line Gateway

SIP DECT Fundamentals October 2012 11

Product overview

Universal extension support

Handsets subscribed on DAPs are external to CS 1000. The CS 1000 does not control

DECT
the state of DECT Handsets. Therefore, the CS 1000

• cannot detect individual key presses on DECT Handsets

• cannot control cadences on DECT Handsets

• cannot control the DECT Handset display content

A DECT Handset subscribed on a DAP cannot use the same range of features available to
analog, digital, or UNIStim IP Deskphones on the CS 1000.

The Universal Extension (UEXT) feature on the Call Server provides Configuration and status
information for subscribed DECT Handsets.

There is limited support for Associated Telephone (AST) or Computer-Telephone Integration
(CTI) capabilities on SIPL for Presence on OCS.

Each DECT Handset has a local Directory Number (DN) in CS 1000. Use this local DN to
subscribe the corresponding DECT Handsets on the SIP DECT system through DAP Manager.
DAP manager is available on the server where you installed the DAP controller.

Configure the UEXT associated with a DECT Handset as follows:

• For the Primary DN of the UEXT (key 0 SCR), enter the local DN associated with the
DECT Handset.

• For SIPL configuration for the Target DN of the UEXT (key 1 HOT U), enter the digits of
the User agent prefix (SIP Line configuration item) plus the local DN of the DECT
Handsets.

A UEXT corresponding to a DECT Handset on the SIP DECT system reflects the idle or busy
status of the associated handset by a check for a call processed between the handset and a
DAP.

The Integrated SIP DECT provides the following UEXT features.

• Make and receive simple calls

• Call Hold. Only one active call and one call on hold can exist for a handset

• Consultative or Announced Call Transfer

• Blind Call Transfer

• Conference call participation if another party adds the DECT Handset to the conference

• Start a three-way call

12 SIP DECT Fundamentals October 2012

Comments? [e-mail]

DECT Handset features

• Calling Line ID (CLID) and Calling Party Name Display (CPND) for simple calls not
involving call transfer

• CLID and CPND for an internal line (digital or IP phone with display) calling to or receiving
a call from a DECT Handset

• Sending DTMF tones through the established connection to interact with the called line
(party), for example, to work with CallPilot

• Support for a voice mailbox on CallPilot and Message Waiting Indication (MWI)

• Call Forward No Answer

• Call Forward By Time of Day

• Call Forward Busy

• Hunting

• Call Restrictions applicable to a UEXT

• Twinned configuration (typically a desk phone plus a DECT Handset)

• Call Waiting

DECT Handset features

The user of a DECT

• Make calls to DNs except restricted or blocked DNs.

• Receive and answer calls from the Call Server. If CPND is available, the name of the
caller and DN appear on the Handset display. The position and appearance of the name
DN on the display depend on the firmware installed on the Handset. You must configure
the required CLS in the UEXT block (CNIA/CNDA/DNDA) and username in LD 95. SIP
DECT also supports CLID restrictions (for example, CLBA, NAMD, DDGD). SIP DECT
Handsets support display update during established calls; this allows SIP DECT on SIP
Line to show a new display name for the connected party. During transfers (both Blind
and Consultative), this provides the new party’s name on the DECT Handset after the
transfer is complete. The display name is taken from the CPND block created for SIPL
UEXT.

Note:

During a transfer

• Place the active call on hold by pressing the R key on the Handset. Return to the held
call by pressing the R key . If a call is on hold, another call can be made from the Handset.
After the second call is established, the user can switch between the two calls with the R
key.

Handset subscribed on SIP DECT can perform the following actions:

, only the display name updates, not the connected number.

SIP DECT Fundamentals October 2012 13

Product overview

• Transfer a call to another DN

- To perform a Blind Transfer, place the current call on hold, call the required DN, and
immediately release from the call.

- To perform a Consultative Transfer, place the current call on hold, call the required
DN, wait for the answer, and release the call after the DN answers.

• Press digit keys on the Handset during an established call to transmit DTMF tones to the
other party on the call.

• Initiate a three-way call. Place an active call on hold, call the third party , and wait until the
call is answered. Press the star (*) key to start the conference.

• Receive a second incoming call (call waiting): When a second call is waiting, a message
"2nd call from <Directory Number>" (the text of the message can be configured)
displays on the screen and a beep emits every 3 seconds. The second calling party hears
a ring back tone instead of a busy tone.

You can use the "*" to toggle between calls. When you toggle between calls, the on­screen messages changes from <Directory Number> to "Waiting <Directory Number>".

• Observe SIP DECT user status (OCS interaction); if a SIP DECT user has Multiple
Appearance Directory Numbers (MADN), then you must configure the SIP DECT Handset
as an OCS-controlled device (AST 0, CLS t87a). The presence status is updated based
on the busy status of either DN.

If a SIP DECT user does not have MADNs, then you must configure the SIP Line UEXT
as AST 0, CLS t87a. If a user for the primary DN is configured in OCS, the presence
status is updated based on the SIP DECT Handset use (busy/available).

• Activate FFC features such as Call Forward, Make Set Busy , Ring Again, Call Park, which
are available for SIP Line users from a DECT Handset. For more information, see Avaya

SIP Line Fundamentals, NN43001-508

Note:

Some of the described features require Call Server configuration.

CallPilot and Message Waiting Indication support

Handsets subscribed on SIP DECT can use CallPilot.

DECT
You can configure Call Forward No Answer for the Primary DN of the UEXT so that the

unanswered calls on the corresponding DECT handset or IP Deskphone (in the case of a
twinned configuration) are forwarded to CallPilot. Calls can also be forwarded to CallPilot as
busy treatment for the Primary DN.

14 SIP DECT Fundamentals October 2012

Comments? [e-mail]

SIP DECT capacity limitations

A user can call the CallPilot system from a DECT Handset and log on to the voice mailbox with
the corresponding DN and password. The user can then use the voice menus of the system
as usual.

Note:

If a voice mail number contains a login (DN) and password for accessing the mailbox, then
the 4027, 4070 and 4075 DECT Handsets send digits to the voice mail system at a rate of
40 msec (for RTP stream only). To recognize the password and login correctly, your voice
mail system must support this rate

The system can send MWI to the DECT Handset through the SIP Trunk; you can enter the
MWI primary DN of the SIP DECT user.

CS 1000 supports only the Unsolicited MWI NOTIFY model. An external SIP UA cannot
SUBSCRIBE to MWI NOTIFY messages and cannot request the current status of MWI for the
DN from the system (by sending SUBSCRIBE messages). Instead, a SIP UA must be ready
to receive MWI NOTIFY messages from the system even if it did not SUBSCRIBE, and it must
update MWI according to those messages only.

If you use a twinned configuration for a DECT Handset, the corresponding IP Deskphone or
TDM telephone correctly reflects the current state of MWI, if it receives MWI notifications for
the Primary DN from CallPilot.

SIP DECT capacity limitations

The following capacity limitations apply to SIP

• a maximum of 12 simultaneous calls for each DAP

• a maximum of 256 DAPs on each network (where handover and synchronization between
DAPs is possible)

• a maximum of 6000 DECT Handsets on each SIP DECT system (potentially, several
isolated SIP DECT systems can connect to CS 1000)

• a maximum of 1000 simultaneous calls on each network

• a maximum of 25 subscription records for each DAP If the planned number of DECT
Handsets in a SIP DECT system is equal to M, and the number of DAPs in that system
is equal to N, M must be less than or equal to N*25.

DECT:

SIP DECT Fundamentals October 2012 15

Product overview

Consider the following additional capacity limitations based on the CS 1000 configuration
characteristics.

• The number of available UEXTs is limited by the number of available virtual Telephone
Numbers (TN) in the system.

• The number of DNs available for DECT Handsets depends on the configured dialing plan
and the availability of the Directory Number Expansion (DNXP) package 150.

16 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Chapter 3: Site planning and hardware

deployment

Navigation

• Components of SIP DECT systems on page 17

• Deployment requirements on page 19

• Types of SIP DECT configuration on page 28

• Site planning on page 33

• System deployment on page 40

Components of SIP DECT systems

This section contains information about the following topics.

• Call Server, Signaling Server, and SIP Line Gateway on page 17

• PC (DAP controller) on page 18

• DECT Access Points on page

Call Server, Signaling Server, and SIP Line Gateway

Before you install SIP
1000 (Avaya CS 1000) system, as follows:

• Install Call Server and SIP Line Gateway.

For more information about SIP Line Gateway, see Avaya SIP Line Fundamentals,
NN43001-508.

The A vaya Communication Server 1000 CP PM Co-resident Call Server and Signaling Server
(CP PM Co-res CS and SS) can run the Call Server software, the Signaling Server software,
and the System Management software on the same hardware platform operating under the
RedHat Linux operating system.

DECT, you must install and configure an Avaya Communication Server

18

SIP DECT Fundamentals October 2012 17

Site planning and hardware deployment

For more information about CS 1000 installation, see Avaya Communication Server 1000E
Installation and Commissioning, NN43041-310.

PC (DAP controller)

Minimum specifications for the DAP

• 2.4 GHz CPU

• 512 MB RAM

• CD-ROM drive

• 1GB free hard disk space

DECT Access Points

Four models of DECT
and C4710E, 4720 and 4720E. The C4710E and 4720E are special versions of C4710 and
4720 Access Points that provide an alternative with an external antenna connection for outdoor
use.

• C4710 DAP

• C4710E DAP

• 4720 DAP

• 4720E DAP

controller PC are as follows.

Access Points (DAP) are currently available for Avaya SIP DECT : C4710

Important:

The only audio codec supported on the C4710 and C4710E DAPs is the G.71
codec is supported on the 4720 and 4720E DAPs only in case the G.729 daughterboard is
installed. For more information, see

Note:

If G.729 codec is not supported by your DAPs, ensure that the G.71
your system. It is not possible to make calls between the Avaya 2050 IP Softphone and
DECT handsets when you select the I use a modem to connect to the network check box
in the Audio settings for the softphone. If you select this setting, the Avaya 2050 IP Softphone
uses the G.729 codec for all calls.

When using Multimedia PC Client, ensure that you select Medium Speed or High Speed
in the Multimedia PC Client Connection preferences if you plan to make calls between DECT
handsets and Multimedia PC Clients.

The DAPs are currently equipped only for EMEA region (only the standard 1.88 to 1.90 GHz
frequency band version is currently available for sale).

18 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Mount the G.729 daughterboard on page 175

1 codec is available in

1 codec. G.729

Ensure that the DAPs are installed according to the location recommendations. For more
information, see Deployment requirements on page

Deployment requirements

Components of SIP DECT systems

19.

This section describes SIP

Navigation

• Radio synchronization on page 19

• IP network configuration on page 23

• Location requirements on page 26

Radio synchronization

The radio network structure supports seamless handover of existing calls.
during a call, if a handset moves from the coverage area of one DAP into the coverage area
of another DAP, the new DAP can take over the call. The call is not interrupted, and the user
is not aware of the handover. In the traditional DECT system, synchronization between DAPs
occurs over the wired network. SIP DECT requires an accurate synchronization of the radio
signals in the air to support handover.

Important:

If a DAP
a single cell mode and cannot handover to other DAPs or receive handover from them.

cannot receive synchronization signals from at least one other DAP, it operates in

DECT deployment requirements.

This means that,

Represent each DAP cell as a circle indicating the radio signals around the DAP.

DAP radio signal synchronization on page 20

• an inner circle in which sufficient radio signal strength exists for acceptable voice quality

• an outer circle in which sufficient signal strength exists for synchronization, but not enough
for acceptable voice quality

SIP DECT Fundamentals October 2012 19

shows two circles around the DAP.

Figure 2:

Site planning and hardware deployment

Figure 2: DAP radio signal synchronization

Due to the cellular structure of a DECT

radio network, overlap exists in the cells with sufficient
voice quality. The wider cell limit around the DAP therefore has some overlap with the other
cell and reaches to the radio of the other cell. Consequently , the DAPs of the overlapping cells
exchange radio signals. These radio signals are weak relative the signal needed by the
handsets, but are strong enough for synchronization.

Important:

For signal strength calculation see Signal strength and frame errors on page 22

.

If one DAP receives a signal from another, the receiving DAP checks the radio signals on
Primary Access Right Identity (PARI), to ensure that the signals belong to the same DECT
system. If the signals belong to the same DECT system, the DAPs synchronize according to
user-configured rules.

Important:

If two or more independent SIP

DECT systems have overlapping coverage areas, configure
these systems so each has a unique subset or portion of carriers. When each system has
a unique subset of carriers, interference between the systems is reduced.

Reducing the number of available carriers reduces the maximum number of simultaneous
calls in the DECT system. To achieve your desired call capacity, you can be required to
install extra DAPs. For more information, see step 4 of

99.

page

Configuring DECT Settings on

The DAPs transmit with a minimum of two channels carrying primary voice and data, also
named bearers. If no voice calls occur over a DAP, the DAP transmits two dummy bearers. If

20 SIP DECT Fundamentals October 2012

Comments? [e-mail]

one or more voice calls occur on the DAP, one is one a dummy bearer, while the others are
voice calls.

Synchronization hierarchy

If two or more DAPs belong to the same system, the DAPs automatically synchronize using a
hierarchical structure. In most cases synchronization is automatic, but if your system has a
complex DAP

The DAP controller tracks the synchronization structure and assigns each DAP a unique Radio
Part Number (RPN) after the DAP starts the first time. One or more DAPs act as a
synchronization source to form the root of the hierarchical structure, as illustrated in

DAP synchronization hierarchy on page 21.

cell structure, you must manually configure synchronization.

Components of SIP DECT systems

Figure 3:

Figure 3: DAP synchronization hierarchy

If more than one synchronization source is present, each one forms a separate hierarchy of
DAPs called a synchronization island.

Automatic synchronization occurs within each synchronization island using the following
rules.

After a DAP starts, it searches for existing DAPs. If it finds one with a lower RPN, it

•
synchronizes with it. If no other DAP exists with a lower RPN, the new DAP becomes the
synchronization source.

Important:

Extra DAPs can be required to establish a synchronization path.

• If a DAP
path to the synchronization master. If two or more DAPs have the same path length

SIP DECT Fundamentals October 2012 21

detects more than one other DAP, it synchronizes with the DAP with the shortest

Site planning and hardware deployment

separating them from the master, the new DAP synchronizes to the DAP with the lowest
RPN.

Important:

After you install SIP DECT, wait at least 15 minutes until you see the results of the automatic
synchronization.

To make a DAP a synchronization master or to give a DAP a higher position in the
synchronization structure, you can manually assign a lower RPN number to a DAP. You can
manually assign RPNs using the DAP Manager Web interface. Automatically assigned RPNs
start at 010. If you manually assign a new RPN, ensure that it is in the range 000 to 00F.

Important:

You must determine the position of the Synchronization Master before you start site
planning. Place the synchronization master, which is the DAP with the lowest RPN, in the
middle of your site, building, or buildings.

Signal strength and frame errors

Signal strength is important for DAP-handset communication (voice quality) and
synchronization between DAPs.
synchronization.

• T o achieve a good voice quality , the minimum signal strength at the receiver in the handset
and DAP must be --72 Decibels (referenced to milliwatts) (dBm). This includes a margin
of --10 dBm for fast fading dips.

• Synchronization is possible if the strength of the received signal from another DAP is --80
dBm to --85 dBm. This is adjustable.

• In an open area, the distance is doubled if the received signal strength is 6 dB lower. This
means that at a minimum signal strength for good voice quality of --72 dBm and a distance
X, the signal strength at the double distance, 2X, is --78 dBm. For more information, see

Figure 4: Signal strength considerations on page 23.

The following items are relevant for the signal strength for

22 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Figure 4: Signal strength considerations

Components of SIP DECT systems

• An open area has more than suf
level at the double distance is --78 dBm. The required level is --80 dBm to --85 dBm. This
leaves a safely margin of 2 to 7 dB.

• Obstructions between the DAPs can introduce loss. Also, many objects cause reflections
that let the signal reach the DAPs through other path with sufficient signal strength.

• In rare cases, factors in the surrounding environment can cause the error rate in the
received frames to be temporarily much higher than is normal for speech. An occasionally
elevated error rate does not indicate a problem with your SIP DECT system. However, if
you consistently see a high error rate, then there is a problem with the deployment of your
SIP DECT system.

Frame errors:

Frame errors rarely can occur in DECT. The number of frame errors for each reading may not
be more than four. The most common cause of frame errors higher than four is a high number
of reflections. This causes an audible click during calls.

IP network configuration

The IP
planning an IP network that is suitable for supporting SIP DECT.

network must be able to support SIP DECT; this section provides information about

ficient signal strength for synchronization. The expected

SIP DECT typically uses existing IP network infrastructure and facilities for the network
connection. For IP connectivity, you must configure the network to ensure that all SIP DECT
components have the following characteristics:

• are equipped with unique IP addresses (some static, some dynamic)

• can reach all the required services

• can be reached by all clients and counterparts

SIP DECT Fundamentals October 2012 23

Site planning and hardware deployment

Ethernet requirements

The following items describe the Ethernet requirements.

• The IP
DECT Voice over IP.

• The IP network must support transparent IP multicast between all DAPs and the DAP
controller.

• Connect only one DAP to one IP Switch port.

• DAP supports full duplex and supports autonegotiation if DAP is connected to a port on
an Ethernet Switch.

• Ensure that enough unique IP addresses are available to support both data networking
traffic and SIP DECT components. Y ou can configure private IP addresses for local traffic,
and you can configure private IP addresses on the local network to connect to public IP
addresses if you use Network Address Translation (NAT). However, SIP DECT does not
support NAT.

• Ensure that IP addresses and routing are consistent with each other to deliver the required
transparency . Also ensure that IP addresses are consistent with routing for normal unicast
traffic as well as for the required multicast traffic.

network must offer a Quality of Service (QoS) that is sufficient to support the SIP

Important:

Configure the Ethernet switch ports to which the DAPs are connected to use
autonegotiation. If the switch does not support autonegotiation, you can use full-duplex;
however SIP DECT can operate incorrectly on some switches when you configure them
to use full-duplex.

• The maximum cable length between the DAP and IP network equipment, such as a
switch, is 100 meters for a Category 5, unshielded twisted-pair, half-duplex cable. If the
required cable length between the IP network equipment and the DAP exceeds 100
meters, use Long Range Ethernet equipment in the connection. Several manufacturers
offer such a solution, which allows cable lengths of more than one kilometer (km).

Fixed IP network addresses

ou must provision fixed IP addresses for the following servers:

Y

• The TFTP server stores the configuration file and the firmware that are available to the
DAPs. After a DAP starts up, the DHCP server sends the DAP the IP address of the TFTP

24 SIP DECT Fundamentals October 2012

Comments? [e-mail]

server. The DAP then downloads the configuration files from the TFTP server . The TFTP
server often runs on the DAP controller or manager PC.

• The DHCP server (optional) sends the address of the DNS server to the DAP. The DAP
does not support Domain Name Resolution.

• The DAP controller or manager requires a fixed IP address. The DAPs retrieve this fixed
IP address from the configuration file that the DAP loads from the TFTP server.

• The IP address of the PABX is reachable either through a router or directly . The PABX is
sometimes referred to as Gatekeeper or SIP proxy, depending on the type of PABX that
is used.

To facilitate network management, Avaya recommends that fixed IP addresses are also
assigned by the DHCP server . Ensure that the DHCP server has the hardware MAC addresses
of all servers to issue the proper (fixed) IP addresses to each individual server.

The DAP IP address can be stored in flash memory. If the IP address is stored, the DHCP
server is needed only for the first startup. Then an IP address is assigned to the DAP.

Dynamic IP network addresses

Components of SIP DECT systems

Network stations, which are not servers (PC workstations and DAPs), can use dynamic IP
addresses assigned by DHCP
addresses of all the network stations in the DHCP server.

Ensure that you configure the DHCP server to assign IP addresses from a specific range to
unknown MAC addresses. However, unknown LAN stations have valid IP addresses, which
can be a minor network security issue. To solve this, use the Vendor Class Identification (VCI)
in the DHCP server . The DHCP server issues IP addresses only to devices that have the DAP
VCI. Ensure that the DHCP server can make a distinction in VCIs. The DAP VCI is D(ECT)AP

49.
Each DAP in a SIP DECT system is assigned a dynamic IP addresses by the DHCP server.

You can configure the DAPs to store the IP address in flash memory, so the DHCP server is
required only during the initial configuration of the system.

Multicast addresses

DECT uses Multicast addresses for the following functions:

SIP

• Communication between the SIP DECT network components to locate or address a
handset. If a handset must be reached, the request must simultaneously go to all DAPs.
For example, if you use the page function during an incoming call, a single multicast
message is sent to all DAPs to find the DAP for your handset quickly and efficiently.

. For dynamic IP addresses, you need not specify the MAC

• Seamless handover from one DAP to the other If inter-cell handover is necessary, the
media path must be redirected from the existing DAP to another DAP. The handset always
initiates a handover. The handset sends request to another DAP (not the DAP with the

SIP DECT Fundamentals October 2012 25

Site planning and hardware deployment

current connection). This DAP issues a multicast on the network to determine on which
DAP the voice connection exists. The DAP, with the existing voice connection, responds
and then the connection can be redirected from the DAP with the existing voice connection
to the new DAP.

• Synchronization between DAPs Y ou must configure multicast before synchronization can
occur between DAPs in the SIP DECT system.

All network components must support forwarding of IP multicast packages. The IP DECT
Configurator proposes a default multicast IP address (239.192.49.49). This is a multicast
address in the private multicast IP address range for use in private IP networks. If you are not
sure you can access this address, contact the local IT manager.

Important:

You must disable IGMP Snooping and Spanning Tree Protocol on switch ports where SIP
DECT equipment is connected. For more information, see DAP multicast group

membership on page 259.

Location requirements

Comply with the following requirements for DAP

• Ensure that the location complies with local electrical codes.

• Install DAPs indoors where no condensation occurs and the temperature remains within
the range of 0°C to 40°C. (of -20C to +40C for external housing).

• Install the C4710 and C4710E DAPs in a vertical position. The radiation pattern differs
between the horizontal and vertical positions. The 4720 and 4720E can be installed
horizontally only if you change the antenna position. For more information, see

the antenna position on page 177

Do not mount a DAP to a metal surface.

•

• Do not roll up the extra cabling behind a DAP.

• Position DAPs upright on walls. DAPs must be at least 30 cm from the ceiling.

• Position DAPs at least 1 meter (m) from large concrete or stone columns and from major
building structural members such as support beams or columns.

• Position the DAPs high enough to clear obstructions between the DAPs and the cell edge
close to the ceiling.

• Mount the DAPs clear of obstacles such as pipes or ducts.

For more information about the 4720 DAP mounting procedure, see

on a wall on page

To install the DAPs outdoors, see

180

Install the external housing on page 217

location:

Adjusting

Mounting the 4720 DAP

.

26 SIP DECT Fundamentals October 2012

Comments? [e-mail]

DAP power configuration

The C4710 and C4710E DAPs are powered using one of the following methods:

Components of SIP DECT systems

• Locally
an AC adaptor that provides at least 10 W atts. For part numbers of available AC adaptors,
see

Table 1: Part numbers

• Through Power over Ethernet (PoE), as defined by IEEE802.3af specifications. The DAPs
support both phantom power and power over spare wires. The following specifications
apply to PoE power.

Both phantom power and power over spare wires are provisioned on the same DAP to provide
system redundancy . The power input providing the highest voltage is active. If one power input
fails, the other takes over without service interruption.

The 4720 and 4720E DAPs are powered only through Power over Ethernet (PoE) with the
following specifications:

, using an RJ-1 1 connector. The AC voltage must be 40V (+ or --10 percent). Use

Table 1: Part numbers on page 27

NTCW28AAE5 N0162030 DAP AC/AC adaptor Eur
NTCW28BAE5 N0162032 DAP AC/AC adaptor UK
NTCW28CAE5 N0162033 DAP AC/AC adaptor ANZ

- Minimum 36 Volts and maximum 60 Volts of voltage at the DAP

- Standard RJ-45 connector, using the spare wires pins (wires)

- Maximum cable length of 100 meters

.

• Voltage at C4720(E) via PoE : 36 . . . . 57 V. DC

• PoE Class ............................. : Class 2

• Power Consumption ............. : 6 Watt maximum

Wire color coding for Category 5 cables

This section shows you the normal color coding for Category 5 cables (4 pair) based on the
two standards supported by
the color code used with a single cable run.

Important:

Both cable ends must use the same standard!

Which standard to use is a matter of local decision. However
pin out at the connector,s you can mix 568A and 568B cables in any installation.

SIP DECT Fundamentals October 2012 27

TIA/EIA: the 568A and 568B standard. These standards apply to

, since they both use the same

Site planning and hardware deployment

Figure 5: Color Schemes for Wires in Category 5 Ethernet Cabling

Types of SIP DECT configuration

ou can implement SIP DECT in various system configurations to accommodate your needs.

Y
The most common SIP DECT configurations are as follows:

• Basic (or Simple) Configuration

• Routed Head Quarter Configuration

• Branch Office Configuration

• Routed Head Quarter Configuration with Branch Office

• Multi Site Mobility Network Configuration

Basic (or Simple) Configuration:

In Basic Configuration, all DAPs are in the same subnet that is based on one or more IP
switches. IP multicast must be able to occur between all DAPs. The configuration supports

28 SIP DECT Fundamentals October 2012

Comments? [e-mail]

Types of SIP DECT configuration

seamless handover between all DAPs. For an illustration of a simple SIP DECT configuration,
see Figure 6: Simple SIP DECT network configuration on page

Figure 6: Simple SIP DECT network configuration

29.

Routed Head Quarter configuration:

Routed Head Quarter Configuration is used for a Large Campus network that is split into
several subnets. In this configuration DAPs belong to various subnets and behave as one large

DECT system with the full support of seamless handover. IP multicast must be able to

SIP
occur between all DAPs in the Campus network, through IP switches and the IP routers that
connect the various subnets. For an illustration of a Routed Head Quarter configuration, see

Figure 7: SIP DECT configuration Routed Head Quarter on page 30

.

SIP DECT Fundamentals October 2012 29

Site planning and hardware deployment

Figure 7: SIP DECT configuration Routed Head Quarter

In Routed Head Quarter Configuration, the network settings must comply with the following
requirements:

•

The network must support Quality of Service (QoS) and IP connectivity throughout the
Campus.

• Routers must support IP multicast routing.

• The IP multicast address for SIP DECT must be the same in all subnets.

• Multicast Time to live (TTL) must be greater than 1.

• In the SIP DECT configuration, you must use an “aggregated” subnet mask that covers
all the subnets where DAPs are present. For instance, if each subnet is defined by mask

255.255.255.0, then “aggregated” mask 255.255.248.0 covers up to four such subnets.

Branch Office Configuration:

Branch Office Configuration is used for a Large Campus network that is split into various
(geographical) segments (branch offices). IP multicast must be able to occur between all DAPs
in every branch office and no IP multicast is allowed between any two branch offices. In this
configuration, each branch office behaves as an isolated site of a large SIP DECT system.
Branch Office configuration supports seamless handover within each isolated site (branch
office), but not between sites. Support is unavailable for roaming between branch offices. For

30 SIP DECT Fundamentals October 2012

Comments? [e-mail]