Avaya 3100 Deployment Guide

Deployment Guide
Avaya 3100 Mobile Communicator

NN42030-301, 01.04

3.1

October 2010

©

2010 Avaya Inc.

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 Avaya reseller outside of the United States
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 TO ANYONE WHO DOWNLOADS, USES AND/OR
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 AVAYA, AN AVAYA AFFILIATE 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 INSTALLING, DOWNLOADING OR USING THE SOFTWARE, 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 INTERCHANGEABLY 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”).

Avaya grants End User a license within the scope of the license types
described below. The applicable number of licenses and units of
capacity for which the license is granted will be one (1), unless a
different number of licenses or units of capacity is specified in the
Documentation or other materials available to End User. “Designated
Processor” means a single stand-alone computing device. “Server”
means a Designated Processor that hosts a software application to be

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

accessed
in object code, originally licensed by Avaya and ultimately utilized by
End User, whether as stand-alone products or pre-installed on
Hardware. “Hardware” means the standard hardware originally sold by
Avaya and ultimately utilized by End User.

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
protected by copyright and other intellectual property laws including the
sui generis rights relating to the protection of databases. You may not
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:

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 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:

support

by multiple users. “Software” means the computer programs

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

http://www.avaya.com/support

http://www.avaya.com/

2 Deployment Guide October 2010

Contents

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

Features............................................................................................................................................................7

Other changes...................................................................................................................................................7

Chapter 2: Introduction.............................................................................................................9

References........................................................................................................................................................9

Chapter 3: Planning and engineering....................................................................................11

Chapter 4: Planning.................................................................................................................13

Avaya 3100 MC - Client and Avaya 3100 MC - Web UI network deployment................................................13

Avaya 3100 Mobile Communicator Gateway network deployment.................................................................15

Communication server requirements..............................................................................................................16

Dialing plans and telephone numbers.............................................................................................................16

Security requirements.....................................................................................................................................18

High availability...............................................................................................................................................20

Capacity..........................................................................................................................................................22

Chapter 5: Engineering...........................................................................................................23

Client device specifications.............................................................................................................................23

Gateway specifications...................................................................................................................................23

Port tables.......................................................................................................................................................23

Chapter 6: Interworking requirements with CS 1000...........................................................29

Avaya CS 1000 deployment considerations....................................................................................................29

Avaya CS 1000 Source Based Routing..........................................................................................................29

Avaya CS 1000 package requirements...........................................................................................................30

Avaya CS 1000 engineering for Avaya 3100 Mobile Communicator..............................................................30

SIP Trunk configuration...................................................................................................................................34

Device Handoff configuration..........................................................................................................................35

Avaya CS 1000 system redundancy...............................................................................................................36

Call Forward No Answer feature interactions..................................................................................................36

Avaya CS 1000 capacity requirements...........................................................................................................37

Trunk calculation: Method 1............................................................................................................................38

Trunk calculation: Method 2............................................................................................................................39

UEXT calculations...........................................................................................................................................42

Avaya CS 1000 and supported Avaya 3100 Mobile Communicator features.................................................42

Call Detail Recording......................................................................................................................................44

Direct outbound call........................................................................................................................................44

Call-Me-First outbound call.............................................................................................................................44

Incoming call...................................................................................................................................................44

Chapter 7: Deployment planning...........................................................................................47

Navigation.......................................................................................................................................................47

Licensing requirements...................................................................................................................................48

Avaya 3100 MC - Client and Avaya 3100 MC - Web UI licenses....................................................................48

Avaya 3100 Mobile Communicator Gateway licenses....................................................................................49

Avaya CS 1000 SIP Gateway CLID Parameters configuration.......................................................................49

Parameter: Country Code.......................................................................................................................51

Deployment Guide October 2010 3

Parameter: Area Code............................................................................................................................51

Parameter: Subscriber/Number of Digits to strip....................................................................................51

Parameter: Subscriber/Prefix to insert....................................................................................................51

Parameter: National/Number of Digits to strip........................................................................................51

Parameter: National / Prefix to insert......................................................................................................52

Mobility prefix..................................................................................................................................................52

Data access planning......................................................................................................................................53

Avaya CS 1000 data access considerations...................................................................................................53

Service DN......................................................................................................................................................53

Universal Extensions.......................................................................................................................................54

Caller ID table.................................................................................................................................................54

Chapter 8: Deployment work flow..........................................................................................57

Deploying the systems task flow.....................................................................................................................57

Chapter 9: Deployment prerequisites....................................................................................59

Establishing the Avaya CS 1000 and Avaya 3100 Mobile Communicator system baseline...........................59

Checking the Avaya CS 1000 release from Element Manager.......................................................................61

Checking the Avaya CS 1000 release from the command line.......................................................................62

Chapter 10: Avaya 3100 Mobile Communicator Gateway installation................................63

Avaya 3100 Mobile Communicator Gateway installation workflow.................................................................63

Preparation......................................................................................................................................................65

Avaya 3100 Mobile Communicator Gateway preparation workflow................................................................65

Installing the Linux base..................................................................................................................................67

Verifying the Enterprise network.....................................................................................................................71

Job aid: Supported LDAP servers...................................................................................................................71

Installation.......................................................................................................................................................72

Installation task flow........................................................................................................................................72

Job aid: Admin shell access............................................................................................................................73

Installing the Avaya 3100 Mobile Communicator Gateway software..............................................................73

Commissioning................................................................................................................................................74

Adding an Avaya 3100 Mobile Communicator Gateway server......................................................................74

Configuring the Gateway settings...................................................................................................................75

Procedure job aid............................................................................................................................................76

Configuring the dial plan conversion parameters............................................................................................81

Variable definitions..........................................................................................................................................82

Rules that use the carat sign...........................................................................................................................82

Configuring the device settings.......................................................................................................................83

Procedure job aid............................................................................................................................................84

Configuring the emergency telephone numbers.............................................................................................87

Adding the Avaya 3100 Mobile Communicator Gateway license....................................................................88

Checking Gateway server status....................................................................................................................89

Procedure job aid............................................................................................................................................90

Solution commissioning..................................................................................................................................92

Chapter 11: Avaya CS 1000 configuration for client support..............................................95

Avaya CS 1000 configuration for client support task flow...............................................................................95

Configuring zones...........................................................................................................................................97

Configuring a D-channel for virtual trunks.......................................................................................................97

Configuring virtual routes................................................................................................................................98

Configuring virtual trunks..............................................................................................................................100

4 Deployment Guide October 2010

Configuring network control parameters data block......................................................................................101

Configuring ESN access codes.....................................................................................................................101

Configuring the Route List Block...................................................................................................................102

Coordinated Dialing Plan..............................................................................................................................103

Forwarding Service DN to Avaya 3100 Mobile Communicator Gateway......................................................103

Configuring a Handoff key.............................................................................................................................105

Configuring a HOT P key..............................................................................................................................106

Configuring the SIP trunk gateway................................................................................................................107

Configuring the SIP Gateway settings..........................................................................................................109

Configuring the SIP URI to NPI/TON mapping..............................................................................................110

Restarting the Signaling Server.....................................................................................................................112

Warm restart..................................................................................................................................................112

Cold restart....................................................................................................................................................112

Configuring NRS............................................................................................................................................112

NRS Database...............................................................................................................................................113

Committing NRS Database...........................................................................................................................113

Configuring Domain names on the NRS.......................................................................................................114

Configuring gateway endpoints on the NRS.................................................................................................116

Adding a User Endpoint.................................................................................................................................119

Job Aid..........................................................................................................................................................122

Adding an NRS Routing rule for the Avaya 3100 Mobile Communicator Gateway.......................................122

Adding an NRS Routing rule for the Avaya CS 1000....................................................................................125

Chapter 12: CallPilot MWI configuration.............................................................................127

MWI for Avaya CS 1000................................................................................................................................127

Chapter 13: Validate deployment.........................................................................................129

Validating deployment task flow....................................................................................................................129

Validating Avaya 3100 Mobile Communicator Gateway registration.............................................................130

Job aid...........................................................................................................................................................130

Validating Avaya 3100 MC - Client for BlackBerry communication...............................................................131

Validating Avaya 3100 Mobile Communicator and Avaya CS 1000 ECS deployment..................................132

Chapter 14: Upgrade fundamentals.....................................................................................135

Navigation.....................................................................................................................................................135

Upgrade work flow........................................................................................................................................136

Upgrading from Release 2.x to Release 3.0.................................................................................................136

Release upgrade taskflow....................................................................................................................137

Capturing Release 2.x parameters.......................................................................................................138

Job Aid: Release 2.x parameter worksheet..........................................................................................139

Upgrading from Release 3.0 to Release 3.1.................................................................................................139

Prerequisites.........................................................................................................................................140

Upgrading from Release 3.0 to Release 3.1 taskflow..........................................................................140

Recording the Release 3.0 configuration parameters..........................................................................141

Release 3.0 system configuration job aid.............................................................................................142

Upgrading the Avaya 3100 Mobile Communicator Gateway software to a new software release................145

Upgrade commissioning.......................................................................................................................147

Upgrading for a Service Upissue..........................................................................................................147

Upgrading the Avaya 3100 Mobile Communicator system software from CD......................................147

Converting to a redundant configuration.......................................................................................................148

Deployment Guide October 2010 5

Chapter 15: Maintenance......................................................................................................151

Navigation.....................................................................................................................................................151

Removing a Service Upissue........................................................................................................................151

Job Aid..........................................................................................................................................................152

Uninstalling the Avaya 3100 Mobile Communicator system software...........................................................152

Chapter 16: Common procedures........................................................................................155

Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as an administrator

......................................................................................................................................................................155

Changing the Avaya 3100 Mobile Communicator Web Administration Console password..........................156

Managing the server processes from the Web Administration Console.......................................................157

Managing the server processes from the command line..............................................................................158

Accessing the server command line as nortel...............................................................................................159

Accessing the server command line as superuser........................................................................................159

Backing up the Avaya 3100 Mobile Communicator Gateway server databases...........................................160

Restoring the Avaya 3100 Mobile Communicator Gateway server databases.............................................161

Chapter 18: Appendix A: Installation worksheets and checklist......................................163

Linux base worksheet...................................................................................................................................163

Avaya 3100 Mobile Communicator Gateway worksheet...............................................................................164

Avaya 3100 Mobile Communicator solution checklist...................................................................................166

Chapter 18: Appendix B: Call flows from CS 1000.............................................................169

Index.......................................................................................................................................171

6 Deployment Guide October 2010

Chapter 1: New in this release

This section details what’s new in Avaya 3100 Mobile Communicator Deployment Guide, NN42030-301
for Avaya 3100 Mobile Communicator Release 3.1.

Features

This document is new for Avaya 3100 Mobile Communicator Release 3.1.

For more information about Avaya 3100 Mobile Communicator, see Avaya 3100 Mobile
Communicator Fundamentals, NN42030-109.

Other changes

This document is new for Avaya 3100 Mobile Communicator Release 3.1. It consolidates the
following documents:

• Avaya 3100 Mobile Communicator Planning and Engineering, NN42030-200

• Avaya 3100 Mobile Communicator Installation and Commissioning, NN42030-300

• Avaya 3100 Mobile Communicator and Avaya Communication Server 1000 Solution

Integration Guide, NN49000-315

Revision History

October 2010 Standard 01.04. This document is issued to support Avaya 3100 Mobile

Communicator Release 3.1. Removed obsolete external references.

July 2010 Standard 01.03. This document is issued to support Avaya 3100 Mobile

Communicator Release 3.1. Updated Avaya 3100 Mobile Communicator

Gateway installation on page 63 and Upgrading the Avaya 3100 Mobile
Communicator Gateway software to a new software release on

page 145. Added Converting to a redundant configuration on page

148.

April 2010 Standard 01.02. This document is up-issued to provide correction to

procedures.

January 2010 Standard 01.01. This document is issued to support Avaya 3100 Mobile

Communicator Release 3.1.

Deployment Guide October 2010 7

New in this release

8 Deployment Guide October 2010

Chapter 2: Introduction

This document guides you through the deployment steps for Avaya 3100 Mobile Communicator (Avaya
3100 Mobile Communicator). These steps include planning, engineering, installation of the Avaya 3100
Mobile Communicator, and interworking the Avaya 3100 Mobile Communicator with the Avaya
Communication Server 1000 (Avaya CS 1000).

• Planning and engineering on page 11 takes you through the planning and engineering required.
At the end of this step, you will have completed a worksheet with parameters you need for
deployment.

•

Deployment work flow on page 57 takes you through the installation of Avaya 3100 Mobile

Communicator and interworking it with your ECS.

This document also includes the following related sections:

•

Upgrade fundamentals on page 135

• Maintenance on page 151

• Converting to a redundant configuration on page 148

• Appendix B: Call flows from CS 1000 on page 169

Important:

For Avaya CS 1000 platforms, Avaya personnel perform all installation and interworking activities.

References

For more information about Avaya 3100 Mobile Communicator, see Avaya 3100 Mobile
Communicator Fundamentals, NN42030-109.

For more information about administration tasks and tasks involving the Avaya 3100 Mobile
Communicator clients, see Avaya 3100 Mobile Communicator Administration and Security,
NN42030-600.

For information about the Avaya 3100 Mobile Communicatorclients, see

• Avaya 3100 Mobile Communicator - Client for BlackBerry User Guide, NN42030-101

• Avaya 3100 Mobile Communicator - Client for Nokia User Guide, NN42030-102

• Avaya 3100 Mobile Communicator - Client for Windows Mobile User Guide,

NN42030-107

Deployment Guide October 2010 9

Introduction

• Avaya 3100 Mobile Communicator - Client for iPhone User Guide, NN42030-111

• Avaya 3100 Mobile Communicator - Web UI User Guide, NN42030-110

10 Deployment Guide October 2010

Chapter 3: Planning and engineering

This chapter contains information that supports the activities that you must perform before installing an
Avaya 3100 Mobile Communicator (Avaya 3100 Mobile Communicator) solution, including requirements,
network management, performance, and capacity requirements.

During the planning and engineering phase, use the worksheets in Appendix A: Installation worksheets

and checklist on page 163 to gather the information you need in order to install, configure, and interwork

your Avaya 3100 Mobile Communicator with your Avaya Communication Server 1000 (Avaya CS 1000).

•

Planning on page 13

• Engineering on page 23

• Interworking requirements with CS 1000 on page 29

• Deployment planning on page 47

Deployment Guide October 2010 11

Planning and engineering

12 Deployment Guide October 2010

Chapter 4: Planning

This chapter details the planning aspects of the Avaya 3100 Mobile Communicator (Avaya 3100 Mobile
Communicator).

Navigation

• Avaya 3100 MC - Client and Avaya 3100 MC - Web UI network deployment on page 13

• Avaya 3100 Mobile Communicator Gateway network deployment on page 15

• Communication server requirements on page 16

•

Dialing plans and telephone numbers on page 16

• Security requirements on page 18

• High availability on page 20

• Capacity on page 22

Avaya 3100 MC - Client and Avaya 3100 MC - Web UI network deployment

The Avaya 3100 Mobile Communicator - Client (Avaya 3100 MC - Client) for BlackBerry, the
Avaya 3100 MC - Client for Nokia, the Avaya 3100 MC - Client for Windows Mobile, the Avaya
3100 MC - Client for iPhone, and the Avaya 3100 Mobile Communicator - Web UI (Avaya 3100
MC - Web UI) require access to the Avaya 3100 Mobile Communicator Gateway. In this
document, the terms Avaya 3100 MC - Client and clients refer to the supported clients and
Avaya 3100 MC - Web UI.

The Avaya 3100 MC - Client for BlackBerry supports two network deployment options:

• with the BlackBerry Enterprise Server (BES)

• without the BES

The Avaya 3100 MC - Client for BlackBerry with the BES uses the BES to route data and
provide security.

Avaya 3100 MC - Client for BlackBerry (without the BES), Avaya 3100 MC - Client for Nokia,
and Avaya 3100 MC - Client for Windows Mobile require a Wireless Access Point or an internet
connection through the Enterprise firewall. These clients can also use the cellular data network.

Figure 1: Typical Avaya 3100 Mobile Communicator network architecture on page 14 shows

a typical network architecture.

Deployment Guide October 2010 13

Planning

Figure 1: Typical Avaya 3100 Mobile Communicator network architecture

The Avaya 3100 MC - Client for Nokia and Avaya 3100 MC - Client for Windows Mobile do not
contain integrated virtual private network (VPN) software. Any industry-standard VPN software
for the Nokia or Windows Mobile device can be used.

The Avaya 3100 MC - Client for Nokia and Avaya 3100 MC - Client for Windows Mobile
communicate directly to the Avaya 3100 Mobile Communicator Gateway. When deployed with
the BES, the Avaya 3100 MC - Client for BlackBerry communicates with the BES, which
communicates with the Avaya 3100 Mobile Communicator Gateway. When deployed without
the BES, the Avaya 3100 MC - Client for BlackBerry communicates directly with the Avaya
3100 Mobile Communicator Gateway.

The Avaya 3100 MC - Web UI does not require software installation on the device. When the
Avaya 3100 MC - Web UI runs on a BlackBerry that uses a BES, the BlackBerry Web browser
uses the Mobile Data Service (MDS) on the BES to access the Avaya 3100 Mobile
Communicator Gateway. For the non-BES BlackBerry, and for Windows Mobile and Nokia
devices, the Avaya 3100 MC - Web UI (in the Web browser) uses HTTPS to connect to the
Avaya 3100 Mobile Communicator Gateway.

For examples of Avaya 3100 MC - Client and Avaya 3100 Mobile Communicator Gateway call
flows, see Avaya 3100 Mobile Communicator Fundamentals, NN42030-109.

14 Deployment Guide October 2010

Avaya 3100 Mobile Communicator Gateway network deployment

Avaya 3100 Mobile Communicator Gateway network
deployment

The Avaya 3100 Mobile Communicator Gateway requires the following network infrastructure:

• access to an Enterprise Call Server (ECS) including a call server, Session Initiation
Protocol (SIP) gateway, and SIP Proxy Server (SPS)

• access to the ECS Telephony Local Area Network (TLAN), including all SIP infrastructure,
media gateways, and any IP endpoint that can originate or terminate real-time transport

• access to a BlackBerry Enterprise Server (BES) if the Avaya 3100 Mobile Communicator
Gateway supports the Avaya 3100 MC - Client for BlackBerry with the BES

Figure 2: Data access from devices on page 15 shows data access from the devices.

Figure 2: Data access from devices

The Avaya 3100 Mobile Communicator Gateway requires the following network infrastructure
with the Avaya CS 1000:

For examples of Avaya 3100 MC - Client and Avaya 3100 Mobile Communicator Gateway call
flows, see Avaya 3100 Mobile Communicator Fundamentals, NN42030-109.

Deployment Guide October 2010 15

Planning

Communication server requirements

Avaya 3100 Mobile Communicator Release 3.1 supports the following versions of Avaya
Communication Server 1000 (Avaya CS 1000):

• Avaya CS 1000 Release 5.5

- CS and SS: Deplist of February 3, 2009 or later

- SPS: SU 5.50.12.006 or later

• Avaya CS 1000 Release 6.0

latest deplist must be loaded

Avaya CS 1000 package requirements are discussed in

requirements on page 30.

Avaya 3100 Mobile Communicator Release 3.1 supports the following versions of Avaya
Communication Server 2100 (Avaya CS 1000):

Avaya CS 1000 SE 11

Dialing plans and telephone numbers

Avaya 3100 Mobile Communicator supports telephone numbers in the following formats

• Dial strings, where the user enters all the digits to be dialed. Examples of dial strings
include 2356, 63432356, 93432356 and 3432356.

• E.164 Fully Qualified International Numbers, where telephone numbers start with the plus
(+) symbol. E.164 Fully Qualified International Numbers are also known as "plus
numbers". Examples of Fully Qualified International Numbers include [phone] and
[phone].

On all mobile phones, mobile carriers support the plus (+) sign in telephone numbers. The +
identifies that this is an E.164 fully qualified international number (for example, see http://
unifiedcommunicationsblog.globalknowledge.com/2009/07/02/e164-the-modern-dial-plan/).

Avaya CS 1000 package

If you use the +, you do not need to use an international dial prefix (for example,. 011). Avaya
3100 Mobile Communicator supports the same dial plan as the mobile carrier by supporting
the +. On devices with a keyboard, the + has its own key (for instance, the ‘O’ on a BlackBerry).
On devices without a QWERTY keyboard, inserting the + is specific to the device.

The dial plan available from Avaya 3100 Mobile Communicator should be the same as the dial
plan for a desk telephone. That is, if the user has a desk telephone and an Avaya 3100 MC ­Client device, the dial plan should be the same.

16 Deployment Guide October 2010

Dialing plans and telephone numbers

Avaya 3100 Mobile Communicator users should use the E.164 Fully Qualified International
Numbers for all stored Public Switched Telephone Network (PSTN) numbers in address books
and mobile device applications. By using this format, the numbers can be dialed from any
region or country, within the wireless network or from the communication server.

The E.164 Fully Qualified International Numbers ensure that users do not need to be
concerned about dial prefixes or long distance codes. The network determines how to place
the call, based on the user's location and network connection.

When the user dials an E.164 Fully Qualified International Number, the communication server
puts the number in the request Uniform Resource Indicator (URI) of the SIP INVITE message in
the following format sip: +CCCXXXXXXXX@domain; user=phone.

When using the ECS, configure the CNTC, NATC, and INTC parameters in LD 15 to support
E.164 Fully Qualified International Numbers. These parameters ensure that fully qualified
numbers within the same country are dialed as national numbers, and international numbers
are prefixed correctly.

Example 1 (Switzerland)

ECS is Avaya Communication Server 1000 (Avaya CS 1000) AC1=0, CNTC=41, NATC=0,
INTC=00

Call to a number within Switzerland

A user initiates a call to a contact with the phone number [phone].

The URI incoming for the SIP INVITE for the call is sip:
[e-mail];user=phone

Avaya CS 1000 digit processing strips the CNTC and adds <AC1 + NATC> to produce
00123456789

Call to a number outside Switzerland

A user initiates a call to a contact with the phone number [phone].

The URI incoming for the SIP INVITE for the call is sip:
[e-mail];user=phone

Avaya CS 1000 digit processing adds <AC1 + INTC> to produce 00014161234567

Example 2 (North America)

ECS is Avaya CS 1000 AC1=6, CNTC=1, NATC=1, INTC=011

Call to a number within North America

A user initiates a call to a contact with the phone number [phone].

The URI incoming for the SIP INVITE for the call is sip:
[e-mail];user=phone

Deployment Guide October 2010 17

Planning

Avaya CS 1000 digit processing strips the CNTC and adds <AC1 + NATC> to produce
614161234567

Call to a number outside North America

A user initiates a call to a contact with the phone number [phone].

The URI incoming for the SIP INVITE for the call is sip:
[e-mail];user=phone

Avaya CS 1000 digit processing adds <AC1 + INTC> to produce 601141123456789.

Security requirements

The Avaya 3100 Mobile Communicator Gateway requires data access to the ECS TLAN and
uses the ECS SIP Proxy Server (SPS) as the SIP Signaling Proxy. The Avaya 3100 Mobile
Communicator Gateway can accept or transmit real time protocol (RTP) messages to any IP
endpoint in the Enterprise (for example, Media Cards, other SIP clients, or IP telephones).

Figure 3: Sample Avaya 3100 Mobile Communicator Gateway firewall configuration on

page 19 shows a firewall that separates the Avaya 3100 Mobile Communicator Gateway
from the remainder of the Enterprise voice infrastructure. The Avaya 3100 MC - Client for
BlackBerry (without the BES), Avaya 3100 MC - Client for Nokia, and Avaya 3100 MC - Client
for Windows Mobile require access on the internet to a public FQDN and a public IP address.
The figure also shows a sample firewall configuration and policy. For the purposes of this
example assume

• that the Avaya 3100 MC - Client (in the absence of a BES) requires a public FQDN and
IP for the Avaya 3100 Mobile Communicator Gateway to be accessible from the internet.
This in turn forces the Avaya 3100 Mobile Communicator Gateway to be placed in a
demilitarized zone (DMZ).

• Firewalls are used to filter traffic from the internet and from the DMZ to separate the Avaya
3100 Mobile Communicator Gateway and internet from the trusted Enterprise voice
infrastructure where other components on the ECS TLAN reside.

18 Deployment Guide October 2010

Figure 3: Sample Avaya 3100 Mobile Communicator Gateway firewall configuration

Security requirements

If a user calls a client, the SIP signaling comes through the SPS. Real Time Protocol (RTP) for
announcements or Avaya 3100 Mobile Communicator Instant Conference calls takes place
between the Avaya 3100 Mobile Communicator Gateway and the IP telephone without using
the SPS.

To allow public internet traffic to reach the Avaya 3100 Mobile Communicator Gateway from
clients, while simultaneously providing Avaya 3100 Mobile Communicator Gateway access to
the ECS TLAN for SIP and RTP, you must carefully consider the data network and security
requirements of the Enterprise.

Proprietary communication between the Avaya 3100 Mobile Communicator Gateway and the
Avaya 3100 MC - Client for BlackBerry (without the BES, using HTTP), the Avaya 3100 MC ­Client for Nokia (using HTTPS), and the Avaya 3100 MC - Client for Windows Mobile (using
HTTPS) enables clients to initiate and modify calls for the user on the ECS. In the BES
configuration, the Avaya 3100 MC - Client for BlackBerry communicates with the BES, which
communicates with the Avaya 3100 Mobile Communicator Gateway. The Avaya 3100 MC ­Client for Nokia and Avaya 3100 MC - Client for Windows Mobile communicates directly with
the Avaya 3100 Mobile Communicator Gateway, as well as the Avaya 3100 MC - Client for
BlackBerry when configured without the BES.

Access to user records in an active directory server configured against the Avaya 3100 Mobile
Communicator Gateway uses a tunnel over HTTP or HTTPS. Configure the Avaya 3100 Mobile
Communicator Gateway to specify the query search base, which limits the search to a subtree
of the base.

Deployment Guide October 2010 19

Planning

The Avaya 3100 Mobile Communicator Gateway queries a corporate Lightweight Directory
Access Protocol (LDAP) server when the users use the Directory lookup feature on their clients.
The Avaya 3100 Mobile Communicator Gateway supports the following LDAP servers:

• Active Directory/Exchange Server 2000 or 2003

• Avaya Common Network Directory (CND)

High availability

You can deploy the Avaya 3100 Mobile Communicator Gateway as a nonredundant server
or in a redundant pair. Figure 4: Avaya 3100 Mobile Communicator Gateway high availability

configuration on page 21 shows the redundant pair configuration that enables the high

availability solution.

20 Deployment Guide October 2010

High availability

Figure 4: Avaya 3100 Mobile Communicator Gateway high availability configuration

A redundant system includes an active server and a standby server. Mobile clients access the
active server, while the standby server functions as a backup. The two roles switch freely,
based on the following rules:

• If the Avaya 3100 Mobile Communicator Gateway does not have a configured backup IP
address, it starts in active mode.

• If the Avaya 3100 Mobile Communicator Gateway has a configured backup IP address,
it starts in inactive mode and attempts to locate the standby system.

- If the standby server is in standby mode, the system with the lower IP address
becomes active.

- If the standby server is in active mode, the standby server remains active.

- If the standby server is not located, the local system is declared active.

• If the active system stops, the standby system becomes active.

The pair of Avaya 3100 Mobile Communicator Gateway servers must contain identical software
for redundancy to work. Each server acts as the backup for the other server.

The clients support Avaya 3100 Mobile Communicator Gateway redundancy. The Primary
Avaya 3100 Mobile Communicator Gateway address and Secondary Avaya 3100 Mobile
Communicator Gateway address fields in the clients contain the active and standby Avaya
3100 Mobile Communicator Gateway IP addresses respectively. When the active Avaya 3100

Deployment Guide October 2010 21

Planning

Mobile Communicator Gateway stops responding, the clients switch to the other Avaya 3100
Mobile Communicator Gateway.

The communication link between two Avaya 3100 Mobile Communicator Gateway servers
in the redundant pair must be highly reliable and available. When the gateways cannot
communicate with each other, they both become active, start processing traffic, and try to
register with the NRS. The NRS has only one gateway endpoint associated with the Avaya
3100 Mobile Communicator Gateway, so the second gateway to register with the NRS
receives all the incoming SIP traffic.

Capacity

The Avaya 3100 Mobile Communicator Gateway supports 1500 users per gateway. Avaya
testing used a capacity of 8000 calls per hour. The 1500 users per gateway capacity
recommendation assumes each user makes on average four calls per hour (or approximately
6000 calls per hour). This results in a margin of safety for the capacity of the Avaya 3100 Mobile
Communicator Gateway when servicing 1500 users per gateway.

Important:

22 Deployment Guide October 2010

Chapter 5: Engineering

This chapter details the engineering aspects of the Avaya 3100 Mobile Communicator (Avaya 3100 Mobile
Communicator).

Navigation

• Client device specifications on page 23

• Gateway specifications on page 23

• Port tables on page 23

Client device specifications

The Avaya 3100 Mobile Communicator - Client (Avaya 3100 MC - Client) application runs on
a number of devices. These devices have no special hardware or software requirements.

To view the list of supported devices, see the Avaya 3100 Mobile Communicator Product
Bulletin at http://www.avaya.com.

Gateway specifications

The Avaya 3100 Mobile Communicator Gateway uses one of the following servers:

• HP DL320G4

• IBM x306m

The Avaya 3100 Mobile Communicator Gateway runs on the Avaya CS 1000 Linux Base
operating system. For more information, see Linux Platform Base and Applications Installation
and Commissioning, NN43001-315.

Port tables

The following table details the ports used in the Avaya 3100 Mobile Communicator Gateway.
When using this section to configure firewalls, refer to Figure 3: Sample Avaya 3100 Mobile

Communicator Gateway firewall configuration on page 19.

Deployment Guide October 2010 23

Engineering

Table 1: Avaya 3100 Mobile Communicator Gateway ports

Port Protocol Function Applica- tion Configur-

able?

21 Transmissi

on Control
Protocol
(TCP)

22 TCP Secure Shell

53
(Send
only)

123
(Send
only)

User
Datagram
Protocol
(UDP)

TCP Network

File Transfer
Protocol
(FTP)

(SSH)

Domain
Name
Server
(DNS)
queries to
external
DNS server

Time
Protocol
(NTP)

Base Linux No No No

Base Linux No No No

Base Linux No Yes,

Base Linux No Yes,

Configure

in Avaya

3100 MCG-

to-

Enterprise

Firewall

policy?

assuming
DNS is
within the
Enterprise
network

assuming
DNS is
within the
Enterprise
network

Configure

in Avaya

3100 MCG

Firewall

policy?

No

No

389
(Send
only)

1098 TCP Communicat

1099 TCP Communicat

LDAP
(TCP)

Directory
access

ion between
the Avaya
3100 MCG
Administrati
on server
and the
Avaya 3100
Mobile
Communicat
or Gateway
server

ion between
the Avaya
3100 MCG

Directory
access

Avaya 3100
MCG

Avaya 3100
MCG

Yes Yes No

No No No

No No No

24 Deployment Guide October 2010

Port tables

Port Protocol Function Applica- tion Configur-

able?

server and
the Avaya
3100 Mobile
Communicat
or Gateway
Administrati
on server

3306 TCP SQL Client

Access

5060 Session

Initiation
Protocol
(SIP)
(UDP)

Avaya 3100
MCG listen
port for Voice
over IP
(VoIP)
Signalling

MySQL No No No

Avaya 3100
MCG

Yes Yes No

Configure

in Avaya

3100 MCG-

to-

Enterprise

Firewall

policy?

Configure

in Avaya

3100 MCG

Firewall

policy?

5072 SIP (UDP) Avaya 3100

MCG listen
port for VoIP
Signalling
(Instant Call
Server)

7800 TCP Avaya 3100

MCG Data
Replication

8008 HTTP

(TCP)

8080 TCP Avaya 3100

8282 HTTP

(TCP)

Licensing
validation
with
www199.nor
tel.com

MC - Client
open client
interface

Avaya 3100
MCG Open
Web Admin
Interface
(standalone

Avaya 3100
MCG

Avaya 3100
MCG

Avaya 3100
MCG

Avaya 3100
MC - Client

Avaya 3100
MCG Web
Administratio
n Console

Yes Yes No

No No No

No No No

Yes 8080 to
8089

No No No

No Yes

Deployment Guide October 2010 25

Engineering

Port Protocol Function Applica- tion Configur-

able?

managemen
t only)

8443 HTTPS

(TCP)

8553 TCP Avaya 3100

9800 TCP Avaya 3100

Avaya 3100
MC - Client
Secure
Client
Interface

MCG Secure
Admin
Interface
(standalone
managemen
t only)

MCG Server
Java Virtual
Machine
(JVM)

Avaya 3100
MCG

Avaya 3100
MCG Admin

Avaya 3100
MCG JVM

Yes 8440 to
8449

No No No

No No No

Configure

in Avaya

3100 MCG-

to-

Enterprise

Firewall

policy?

No Yes

Configure

in Avaya

3100 MCG

Firewall

policy?

9801 TCP Avaya 3100

MCGAdmini
stration JVM

26000
to
26099
(listen
only)

27000
to
27099
(listen
only)

UDP Media for all

Avaya 3100
MC - Client
calls
anchored on
the Avaya
3100 MCG

RTP (UDP) Media for all

Avaya 3100
MC - Client
calls
anchored on
the Avaya
3100 MCG

Avaya 3100
MCG Admin
JVM

Voice over IP
(VoIP)
Conference
Media

VoIP Media Yes Yes No

No No No

Yes Yes No

In the preceding table, the ranges 26000 to 26999 and 27000 to 27999 depend on the
configuration of the Maximum number of DTR ports parameter.

26 Deployment Guide October 2010

Port tables

The following table lists the ports that are defined by the Enterprise Call Server (ECS). You
configure these ports on the ECS.

Table 2: ECS ports

Protocol Function Application Configure in the

Avaya 3100

Mobile

Communicator

Gateway-to-

Enterprise

Firewall policy?

RTP
(UDP)

RTP
(UDP)

RTP
(UDP)

VoIP send port for the
Gateway server.
Configured on the
Avaya 3100 MCG.

VoIP send port for the
Instant Conference
Server. Configured on
the Avaya 3100 MCG.

VoIP send port for the
VoIP Conference
Media. RTP can be sent
to media gateways, IP
endpoints, or other SIP
User Agents. The range
of end point ports
defines the ports to
which the Avaya 3100
MCG sends media.

Avaya 3100
MCG

Avaya 3100
MCG

Avaya 3100
MCG

Yes No

Yes No

Yes No

Configure in the

Internet-to-Avaya

3100 Mobile

Communicator

Gateway Firewall

policy?

RTP
(UDP)

Deployment Guide October 2010 27

VoIP send port for
Media. RTP can be sent
to media gateways, IP
endpoints, or other SIP
User Agents. The range
of end point ports
defines the ports to
which the Avaya 3100
MCGsends media.

Avaya 3100
MCG

Yes No

Engineering

28 Deployment Guide October 2010

Chapter 6: Interworking requirements with

CS 1000

This chapter details the interworking requirements for the Avaya 3100 Mobile Communicator (Avaya 3100
Mobile Communicator) and Avaya Communication Server 1000 (Avaya CS 1000), which is a supported
Enterprise Call Server (ECS).

Navigation

•

Avaya CS 1000 deployment considerations on page 29

•

Avaya CS 1000 Source Based Routing on page 29

• Avaya CS 1000 package requirements on page 30

• Avaya CS 1000 engineering for Avaya 3100 Mobile Communicator on page 30

• Avaya CS 1000 capacity requirements on page 37

• Avaya CS 1000 and supported Avaya 3100 Mobile Communicator features on page 42

•

Call Detail Recording on page 44

Avaya CS 1000 deployment considerations

The Avaya 3100 Mobile Communicator Gateway requires data access to the Avaya CS 1000
Telephony Local Area Network (TLAN). The Avaya 3100 Mobile Communicator Gateway uses
the Avaya CS 1000 Session Initiation Protocol (SIP) Proxy Server (SPS) as the SIP Signaling
Proxy. The Avaya 3100 Mobile Communicator Gateway accepts or transmits real time protocol
(RTP) messages to any IP endpoint within the Enterprise (for example, Media cards, other SIP
clients, or IP telephones).

To allow public internet traffic to reach the Avaya 3100 Mobile Communicator Gateway from
clients, while simultaneously providing Avaya 3100 Mobile Communicator Gateway access to
the Avaya CS 1000 TLAN for SIP and RTP, you must carefully consider the data network and
security requirements of the Enterprise.

Avaya CS 1000 Source Based Routing

Avaya CS 1000 Source Based Routing (SBR) occurs when the request Uniform Resource
Indicator (URI) of the INVITE message sent from the Avaya 3100 Mobile Communicator

Deployment Guide October 2010 29

Interworking requirements with CS 1000

Gateway contains the tag x-nt-net-feature=x-nt-home. For example, the following request URI
triggers SBR:

INVITE sip:[e-mail];x-nt-sip-line-service;x-nt-net-feature=x-nt-home SIP/

2.0

SBR causes the Avaya CS 1000 Network Routing Service-SIP Proxy Service (NRS-SPS) to
route the call attempt (INVITE) to the P-Asserted-Id in the SIP INVITE instead of using the
Request URI.

Using SBR means that all calls from a SIP user route to the home call server for origination,
allowing the call server to apply features such as Calling Line ID (CLID) and Network Class of
Service (NCOS) to SIP calls.

In the Avaya 3100 Mobile Communicator Gateway, use the User Prefix/Phone-context for Call
origination field to configure SBR. For information, see Avaya 3100 Mobile Communicator
Administration and Security, NN42030-600.

Avaya CS 1000 package requirements

Avaya CS 1000 requires the following packages to support Avaya 3100 Mobile Communicator:

• FMCL package (414)

• Mobile Extension (412)

• PCA (398)

• ISDN (145)

If the Avaya 3100 Mobile Communicator supports the CallPilot Message Waiting Indicator, the
following package must be licensed:

Premium Service and NMC (175, 219)

Avaya CS 1000 engineering for Avaya 3100 Mobile Communicator

The Avaya 3100 Mobile Communicator - Web UI, Avaya 3100 MC - Client for BlackBerry, Avaya
3100 MC - Client for Nokia, Avaya 3100 MC - Client for Windows Mobile, and Avaya 3100
Mobile Communicator Gateway depend on the following Avaya CS 1000 components:

• Avaya CS 1000

30 Deployment Guide October 2010