Avaya 3100 Mobile Communicator
Gateway and Avaya Communication
Server 2100 Solution Integration Guide
3.0
NN42200-506, 01.02
August 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
“Documentation” means information published by Avaya in varying
mediums which may include product information, operating instructions
and performance specifications that Avaya generally makes available
to users of its products. Documentation does not include marketing
materials. Avaya shall not be responsible for any modifications,
additions, or deletions to the original published version of
documentation unless such modifications, additions, or deletions were
performed by Avaya. End User agrees 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 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 its Hardware and Software
(“Product(s)”). 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://support.avaya.com. Please note that if
you acquired the Product(s) 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,
HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE
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; 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”).
Copyright
Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation, Software, or Hardware
provided by Avaya. All content on this site, the documentation and the
Product 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 unless expressly authorized by Avaya. 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:
http://support.avaya.com/Copyright.
Preventing Toll Fraud
“Toll fraud” is the unauthorized use of your telecommunications system
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 Toll 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 +1-800-643-2353 for the United States
and Canada. For additional support telephone numbers, see the Avaya
Support Web site:
http://support.avaya.com. Suspected security
vulnerabilities with Avaya products should be reported to Avaya by
sending mail to: [email protected].
Trademarks
The trademarks, logos and service marks (“Marks”) displayed in this
site, the Documentation 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 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 non-Avaya trademarks are the property of their respective owners,
and “Linux” is a registered trademark of Linus Torvalds.
Downloading Documentation
For the most current versions of Documentation, see the Avaya
Support Web site:
http://support.avaya.com.
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: http://support.avaya.com.
2 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010
Contents
Chapter 1: New in this release.................................................................................................5
Features............................................................................................................................................................5
Other changes...................................................................................................................................................5
Chapter 2: Introduction.............................................................................................................7
Chapter 3: Avaya 3100 MC and Avaya CS 2100 deployment overview................................9
Call flows...........................................................................................................................................................9
Licensing requirements...................................................................................................................................11
Dialing plans and telephone numbers.............................................................................................................12
Service DN......................................................................................................................................................12
Device Handoff key configuration in PBX telephones.....................................................................................12
Chapter 4: CallPilot MWI configuration.................................................................................13
Chapter 5: Avaya 3100 MC and Avaya CS 2100 integration................................................15
Avaya 3100 MC and Avaya CS 2100 integration workflow.............................................................................16
Establishing the system baseline....................................................................................................................17
Avaya 3100 Mobile Communicator Gateway installation and commissioning................................................19
Avaya Communication Server 2100 configuration..........................................................................................19
Service DN configuration................................................................................................................................19
Avaya 3100 Mobile Communicator Gateway configuration............................................................................21
Autoconfiguration settings...............................................................................................................................22
Validate deployment........................................................................................................................................22
Validating deployment task flow......................................................................................................................23
Validating Avaya 3100 Mobile Communicator Gateway registration...............................................................23
Job aid.............................................................................................................................................................24
Validating Avaya 3100 MC - Client for BlackBerry communication.................................................................25
Validating Avaya 3100 Mobile Communicator and Avaya CS 1000 ECS deployment....................................25
Index.........................................................................................................................................29
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 3
4 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010
Chapter 1: New in this release
The following sections detail what's new in Avaya Mobile Communication Gateway and Avaya
Communication Server 2100 Solution Integration Guide, NN42200-506 for Mobile Communication 3100
(MC 3100) Release 3.0.
• Features on page 5
• Other changes on page 5
Features
This is the first release of this document.
Other changes
There are no other changes to the document in this release.
Revision history
July 2009 Standard 01.01. This document is issued to support Avaya Mobile
Communication Gateway Release 3.0 and Avaya Communication Server
2100 Release SE 11.
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 5
New in this release
6 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010
Chapter 2: Introduction
This document describes the interworking of the Avaya 3100 Mobile Communicator (Avaya 3100 MC) and
Avaya Communication Server 2100 (Avaya CS 2100). The Avaya 3100 MC consists of the Avaya 3100
Mobile Communicator Gateway ) and three clients: Avaya 3100 Mobile Communicator - Client (Avaya
3100 MC-Client)) for BlackBerry, Avaya 3100 MC-Client for Nokia, and Avaya 3100 MC-Client for Windows
Mobile.
For information on the Avaya 3100 Mobile Communicator solution, see Avaya 3100 Mobile Communicator
Fundamentals, NN42040-109, Avaya 3100 Mobile Communicator Planning and Engineering,
NN42030-200, and the Avaya 3100 Mobile Communicator Technology Transfer (located in the Avaya 3100
Mobile Communicator product area of
http://www.avaya.com).
Important:
This document assumes a detailed knowledge of Communication Server 2100 configuration.
•
Avaya 3100 MC and Avaya CS 2100 deployment overview on page 9
• CallPilot MWI configuration on page 13
• Avaya 3100 MC and Avaya CS 2100 integration on page 15
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 7
Introduction
8 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010
Chapter 3: Avaya 3100 MC and Avaya CS
2100 deployment overview
This section describes the deployment of theAvaya 3100 Mobile Communicator Gateway (Avaya 3100
MC) with the Avaya Communication Server 2100 (Avaya CS 2100).
For information on the planning aspects related to the Avaya 3100 MC and Avaya CS 2100, see Avaya
3100 Mobile Communicator Gateway Planning and Engineering, NN42030-200, which covers the
following topics:
• Avaya 3100 Mobile Communicator - Client (Avaya 3100 MC-Client) deployment considerations
• Dialing plans and telephone numbers
• Avaya 3100 MC high availability support
• Avaya 3100 MC port tables
• Avaya CS 2100 deployment considerations
•
Call flows on page 9
• Licensing requirements on page 11
• Dialing plans and telephone numbers on page 12
• Service DN on page 12
•
Device Handoff key configuration in PBX telephones on page 12
Call flows
The communication between the Avaya 3100 Mobile Communicator Gateway and the call
server occurs through SIP lines for the client side communications, and through a SIP PBX
interface for network side communications.
The Avaya 3100 MC-Client registers back to the Avaya Communication Server 2100 through
the Wireless Data network back to the Avaya 3100 MC to the Application Server (SSL).
The following figure shows an outbound call flow, as follows:
1. The client initiates a call request, which signals SIP over HTTP across the wireless
data network to the Avaya 3100 MC.
2. The Avaya 3100 MC communicates to the Application Server in the Avaya CS 2100
through SIP to process the call.
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 9
3. Once processed, the call comes to the Avaya 3100 MC to generate the call to the
wireless voice client to establish the first leg.
4. Once completed, the Avaya 3100 MC sets up the second leg of the call to the
termination point.
Figure 1: Outbound call flow
The following figure shows an inbound call flow, as follows:
1. Call to Avaya 3100 MC-Client, call server terminates to the Avaya 3100 MC.
2. Avaya 3100 MC notifies Avaya 3100 MC-Client
3. Avaya 3100 MC-Client accepts the call.
4. Avaya 3100 MC establishes call between the gateway and the Avaya 3100 MC-
Client.
Avaya 3100 MC and Avaya CS 2100 deployment overview
10 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration
Guide August 2010
Figure 2: Inbound call flow
Licensing requirements
Avaya Communication Server licensing requirements:
• Requires Avaya Communication Server 2100 Release SE 11
• Uses SIP Access Port licenses for Avaya CS 2100 SIP infrastructure support
Avaya 3100 Mobile Communicator — Client licensing requirements:
• Each Avaya 3100 MC-Client requires a license.
• Each license key can only be used once per user.
• The Avaya 3100 MC-Client licenses are installed on the Avaya 3100 Mobile
Communicator Gateway (Avaya 3100 MC).
Licensing requirements
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 11
The Avaya 3100 MC allocates the license on a first come, first served basis as the Avaya 3100
MC-Client registers with the Avaya 3100 MC.
• There is no requirement to distribute licenses to each end user.
• The Avaya 3100 MC administrator can revoke licenses on a per user basis, if necessary,
to reclaim user licenses.
Dialing plans and telephone numbers
The dial plan available from Avaya 3100 Mobile Communicator Gateway 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 Mobile Communicator - Client device, the dial plan should be the same.
Service DN
The mobile clients use a Service DN to originate calls in direct outbound mode. The Service
DN information for the trunk between the Avaya 3100 Mobile Communicator Gateway and the
SIP PBX interface on the Avaya Communication Server 2100 must be set up.
For information about configuring the Service DN, see
Service DN configuration on page
19.
Device Handoff key configuration in PBX telephones
To allow an Avaya 3100 Mobile Communicator Gateway user to move calls between the Avaya
3100 Mobile Communicator - Client and the PBX telephone, the use of the Fast Transfer
feature on the desktop phone and the handoff key in the Avaya 3100 MC - Client allows the
user to quickly transition from one device to another.
To differentiate the Fast Transfer key for the Avaya 3100 MC-Client and other Fast Transfer
features, relabeling the key as “Handoff” is recommended.
Avaya 3100 MC and Avaya CS 2100 deployment overview
12 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration
Guide August 2010
Chapter 4: CallPilot MWI configuration
To enable message waiting indicator (MWI) notifications, you must configure the appropriate parameters in
the service order system (SERVORD), as follows:
• If you are using a SIP phone on the desk as well as the Avaya 3100 MC-Client, use the Message
Waiting Lamp (MWL) feature.
• If you are using a business set (TDM or Unistim) on the desk as well as the Avaya 3100 MC-
Client, use the appropriate Message Waiting feature for that terminal (MWT, MWL, etc.)
• If you are using a simring where a call is presented to a desktop phone and the Avaya CS 2100
simultaneously rings the Avaya 3100 MC-Client DN on the Avaya CS 2100, use the Multiple Set
Message Waiting Indication (MSMWI) feature.
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 13
CallPilot MWI configuration
14 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration
Guide August 2010
Chapter 5: Avaya 3100 MC and Avaya CS
2100 integration
This section describes the tasks required to get the Avaya 3100 Mobile Communicator Gateway (Avaya
3100 MC) working with Avaya Communication Server 2100 (Avaya CS 2100).
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 15
Avaya 3100 MC and Avaya CS 2100 integration workflow
Figure 3: Avaya 3100 MC and Avaya CS 2100 integration workflow
Avaya 3100 MC and Avaya CS 2100 integration
16 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration
Guide August 2010
Result
Work flow navigation
• Put in a new xref to Prerequisites after Prerequisites has been moved to the next topic.
• Avaya 3100 Mobile Communicator Gateway installation and commissioning on page
19
•
Avaya Communication Server 2100 configuration on page 19
• Avaya 3100 Mobile Communicator Gateway configuration on page 21
• Validate deployment on page 22
Move this to the next topic
Prerequisites
This section describes the prerequisites for Avaya 3100 Mobile Communicator Gateway
(Avaya 3100 MC) and Avaya Communication Server 2100 (Avaya CS 2100) integration.
Establishing the system baseline
To successfully integrate voice services, you must first establish the system baseline for the
Avaya CS 2100 and Avaya 3100 MC systems so that the systems are configured and working in
a stand-alone environment. Use the following table to complete system baselines before
integration.
Task Reference Comments
Avaya Communication
Server 2100
The dialing plan must be
implemented.
Avaya Communication
Server 2100 Configuration —
Commercial Systems
Translations, NN42100-500
Avaya CS 2100 software is
Release SE 11 or higher.
Basic installation, setup, and
configuration of the Call
Server components are
complete.
Avaya Installation Method
24-2786 (Avaya 3100 MC
installation and
commissioning performed by
Avaya services)
SSL
SSL must be Release
10.1.5.x.
Establishing the system baseline
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 17
Task Reference Comments
Line side datafill must be
complete.
Session Server Lines
Configuration, NN10437-511
OSSGate User Guide,
NE10004-512
VoIP VPN datafill must be
complete.
Session Initiation Protocol
(SIP)-enabled VoIP VPN
Configuration, NN10437-121
Avaya 3100 Mobile
Communicator Gateway
Avaya 3100 Mobile
Communicator Gateway
must be Release 3.0.x.x.x.
If using BlackBerry devices
and the BlackBerry
Enterprise Server (BES), the
devices and BES must have
the BlackBerry Mobile Data
Service (MDS) enabled and
the devices must be able to
access the Fully Qualified
Domain Name (FQDN) or IP
address of the Avaya 3100
Mobile Communicator
Gateway.
If using mobile devices from
the cellular data network (no
BES), the Avaya 3100 Mobile
Communicator Gateway
requires am internet-
accessible FQDN and IP
address.
The Avaya 3100 Mobile
Communicator Gateway
must have the latest patches
applied.
Avaya 3100 Mobile
Communicator Gateway
Release Notes,
NN42030-404 (Updates
through Product Bulletins).
n
Avaya 3100 Mobile
Communicator Gateway
license file installed to enable
MCC 3100 clients
Avaya 3100 Mobile
Communicator Gateway
Installation and
Commissioning,
NN42030-300
Avaya 3100 Mobile
Communicator Gateway
ports must be accessible
through the firewall.
Avaya 3100 Mobile
Communicator
GatewayPlanning and
Engineering, NN42030-200
Avaya 3100 MC and Avaya CS 2100 integration
18 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration
Guide August 2010
Avaya 3100 Mobile Communicator Gateway installation and
commissioning
Installation and commissioning of the Avaya 3100 Mobile Communicator Gateway is performed
by Avaya personnel. For information, see Installation Method, 24-2786.
Avaya Communication Server 2100 configuration
This section describes the configuration required on the Avaya Communication Server 2100
(avaya CS 2100).
Service DN configuration
The mobile clients use a Service DN to originate calls in direct outbound mode. The Service
DN information for the trunk between the Avaya 3100 Mobile Communicator Gateway and the
SIP PBX interface on the Avaya Communication Server 2100 must be set up.
The Service DN information on the Avaya CS 2100 is datafilled in tables DNROUTE and
IBNROUTE. The following example shows the datafill to use (references to the specific entry
in table IBNRTE and to the trunk CLLI are site-dependent):
>table dnroute TABLE: DNROUTE >pos 972 684 9120 972 684 9120 T IBNRTE
920 >dow 972 684 9121 T IBNRTE 921 >table ibnrte TABLE: IBNRTE >pos
920 920 ( N N N N N SIPPBX2MC31002 0)$ $ >pos 921 921 ( N N N N N
SIPPBX2MC3100 0)$ $
The Service DN information for the Avaya 3100 Mobile Communicator Gateway is set up using
the Dial-In Service DN on the Avaya 3100 Mobile Communicator Gateway. Additionally, the
User Name and Password must match the Dial-In Service DN, as shown in the following
examples.
Configure the Dial-In Service DN on the Avaya 3100 Mobile Communicator Gateway, as
shown in the following example.
Avaya 3100 Mobile Communicator Gateway installation and commissioning
Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration Guide
August 2010 19
Additionally, the User Name and Password must match the Dial-In Service DN, as shown in
the following example.
The Avaya 3100 Mobile Communicator Gatewaythen registers with the Avaya CS 2100 SIP
PBX, as shown in the following example:
Avaya 3100 MC and Avaya CS 2100 integration
20 Avaya 3100 Mobile Communicator Gateway and Avaya Communication Server 2100 Solution Integration
Guide August 2010
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/
