Avaya 3100 Mobile Communicator Deployment User's Guide

Deployment GuideAvaya 3100 Mobile Communicator3.1NN42030-301, 01.04October 2010

• Avaya 3100 Mobile Communicator - Client for iPhone User Guide, NN42030-111• Avaya 3100 Mobile Communicator - Web UI User Guide, NN42030-110Introduct

11. Enter the appropriate information in the text boxes and in Basic Route Options,Network Options, General Options, and Advanced Configurations.12. C

Configuring network control parameters data blockTo configure Network Control Parameters data block, you can use Element Manager or LD 87of the comman

• Enter a NARS/BARS Access Code (AC1) of up to four digits. Typically, thenumber is 9 for North America.Note: The code cannot conflict with any value

8. Accept all other defaults.9. Click Submit.Coordinated Dialing PlanA Coordinated Dialing Plan (CDP) permits a customer to define a simple dialing pl

4. In the navigation pane Dialing and Numbering Plans, Incoming Digit Translation5. Click Customer Edit IDC.The Incoming Digit Conversion Property pag

Figure 21: Edit Incoming Digits10. Enter the DID DN Incoming Digits to be converted.11. Enter the Converted Digits = Mobility Prefix + DID DN.12. Clic

1. Log on to Element Manager.2. In the navigation pane select Phones.The Search for Phones pane opens.3. Click Add.The New Phones page opens.• Enter N

• Choose Phone type = UEXT - Universal Extension4. Click Preview.The Phone Details page opens.• Choose Customer Number = 0• Enter Terminal Number = 25

Figure 23: Signaling Server SIP6. Select a SIP option from the Enable IP Peer Gateway (Virtual Trunk TPS) list.7. Select Enable SIP Proxy/Redirect Ser

The Domain name is case sensitive and must match the Service Domain nameconfigured in the NRS.10. If authentication is enabled in the NRS, configure t

Chapter 3: Planning and engineeringThis chapter contains information that supports the activities that you must perform before installing anAvaya 310

Figure 24: SIP Gateway settings5. Complete the following for the primary server.• Primary Proxy or Re-direct (TLAN) IP address: Enter the TLAN IP addr

1. Log on to Element Manager.2. In the navigation pane click System > IP Network > Node: Servers, Media Cards.The Node Configuration page opens.

Restarting the Signaling ServerThere are two methods for restarting the Signaling Server:Warm restart1. From the EM navigator select System > IP Ne

interfaces with the database for viewing, adding, deleting, or modifying numbering planconfiguration data and routing entries. All changes to the numb

Figure 28: Database switched3. Click the Commit.Figure 29: Database committedThe databases are synchronized. Both databases are changed.Configuring Do

Figure 30: NRS Server2. Click Numbering Plans > Domains.Figure 31: Service Domains (1)3. Ensure Standby database is selected.The Standby database i

Figure 33: L1 Domains (UDP) (1)Figure 34: L0 Domains (CDP) (1)6. Cut over and commit database, see Committing NRS Database on page 113. Note:You need

1. Open NRS Manager by doing one of the following: In Element Manager, selectNetwork, Elements and select the NRS from the Elements page. OR In Inter

Figure 36: Add Gateway Endpoint5. For Endpoint name, type a relevant endpoint name.Example: 3100MCGNote: Endpoint names are case sensitive and must ma

7. Ensure that Endpoint Authentication Enabled is configured to AuthenticationOff.8. For SIP support, select Dynamic SIP endpoint.9. For SIP transport

Planning and engineering12 Deployment Guide October 2010

The User Endpoints pane contains User Endpoints for (Service Domain / L1Domain / L0 Domain).3. Click Numbering Plans, Endpoints. The search for Endpoi

6. Complete the optional fields as appropriate.7. Click the Save button.The standby database is updated. The Endpoints Web page opens, showing thenewl

Job AidThe following table to understand the Add User Endpoint Web page fields.Field DescriptionUser name Enter a User name for the endpoint. The endp

1. Open NRS Manager by doing one of the following: In Element Manager, selectNetwork, Elements and select the NRS from the Elements page. OR In Inter

Figure 41: Adding routing entry MGC 31006. Click Save.The standby database is updated. The Routes web page opens, displaying thenewly added routing en

Adding an NRS Routing rule for the Avaya CS 1000Use this procedure to create an NRS Routing rule to route calls to the Avaya CS 1000.1. Open NRS Manag

Communicator. In the example 46 is used to capture the DID DN numbers4680-4689.Figure 44: Add routing entry Avaya CS 10006. Click Save.The standby dat

Chapter 12: CallPilot MWI configurationThis section describes the Call Pilot Message Waiting Indication (MWI) configuration for Avaya CS 1000and Avaya

CallPilot MWI configuration128 Deployment Guide October 2010

Chapter 13: Validate deploymentThis section describes how to validate that the Avaya 3100 Mobile Communicator components and theAvaya Communication Se

Chapter 4: PlanningThis chapter details the planning aspects of the Avaya 3100 Mobile Communicator (Avaya 3100 MobileCommunicator).Navigation• Avaya

Validating Avaya 3100 Mobile Communicator GatewayregistrationUse this procedure to determine if the Avaya 3100 Mobile Communicator Gateway is register

Figure 46: Successful registrationThe following figure shows an unsuccessful registration attempt with an alarm entry.Figure 47: Unsuccessful registra

If you can view the Avaya 3100 Mobile Communicator Gateway User Portal, thenyou have proper communication between the client and the Avaya 3100 Mobile

6. Configure one of the clients to require encryption. Use this client in the remainderof this procedure.7. Log in to the client using HTTPS.Validates

Validate deployment134 Deployment Guide October 2010

Chapter 14: Upgrade fundamentalsThis chapter describes the following upgrade paths:• Release 2.x to Release 3.0 upgrade• Release 3.0 to Release 3.1 up

Upgrade work flowFigure 49: Upgrade workflowWorkflow navigation• Upgrading from Release 2.x to Release 3.0 on page 136• Upgrading from Release 3.0 to

Important:You must upgrade both Avaya 3100 Mobile Communicator Gateway servers at the sametime, and the IP addresses must not change. The client upgr

• Commissioning on page 74• Solution commissioning on page 92 Important:When following the commissioning procedures for a Release 2.x to Release 3.0up

Job Aid: Release 2.x parameter worksheetFill in the following worksheet with the values from your Release 2.x system. Use the valueswhen you commissio

Figure 1: Typical Avaya 3100 Mobile Communicator network architectureThe Avaya 3100 MC - Client for Nokia and Avaya 3100 MC - Client for Windows Mobil

Important:Upgrade one Avaya 3100 Mobile Communicator Gateway server and return it to servicebefore upgrading the other server. As soon as you start t

• Backing up the Avaya 3100 Mobile Communicator Gateway server databases onpage 160• Upgrading the Avaya 3100 Mobile Communicator Gateway software to

11. Click the Tools tab.12. In Table 16: Tools configuration on page 145, record the Tools configuration.Release 3.0 system configuration job aidUse t

Section Release 3.0 fieldnameRelease 3.1field nameServer 1configurationServer 2configurationDial-In ServiceDNDial-In ServiceDNDialplanConversion ListD

Section Release 3.0 fieldnameRelease 3.1field nameServer 1configurationServer 2configurationLDAP tag foruser's emailLDAP attributetag that contai

Section Release 3.0 fieldnameRelease 3.1 fieldnameConfigurationNative DialingNumbersNative DialingNumbersAuto-Download ofDevice ConfigurationAllow Cli

• 1 to install the upgrade and delete the existing data.• 2 to install the upgrade and retain the existing.7. Read the Avaya software license agreemen

Upgrade commissioningIf the database restore fails, you need to recommission the system using the parameters savedin Recording the Release 3.0 configu

Converting to a redundant configurationIf the initial installation is a standalone configuration you can convert to a redundantconfiguration. Importan

8. Run the configuration script:/opt/MobilityGatewaybin/mgsetup.sh9. At the prompt for the ethernet address, select the card that corresponds to the I

Avaya 3100 Mobile Communicator Gateway networkdeploymentThe Avaya 3100 Mobile Communicator Gateway requires the following network infrastructure:• acc

Upgrade fundamentals150 Deployment Guide October 2010

Chapter 15: MaintenanceThis chapter contains procedures used to maintain the software.Navigation• Removing a Service Upissue on page 151• Uninstalling

4. Enter y.The RPM patch removal completes.5. Enter su6. At the prompt, enter <root_password>7. To complete the removal, enter /opt/mobilitybase

PrerequisitesYou must be logged into the server as nortel. For more information, see Accessing the servercommand line as nortel on page 159.To delete

Maintenance154 Deployment Guide October 2010

Chapter 16: Common proceduresThis chapter contains the following procedures:• Logging on to the Avaya 3100 Mobile Communicator Web Administration Cons

ORhttps://<IP address | hostname>:8553/adminserver2. In the Username field, type the user name.3. In the Password field, type the admin password

PrerequisitesYou must be logged into the Avaya 3100 Mobile Communicator Web Administration Consoleas administrator. For more information, see Logging

PrerequisitesYou must be logged into the Avaya 3100 Mobile Communicator Web Administration Consoleas administrator. For more information, see Logging

appstart start3. To stop the server, enterappstart stop4. To restart the server, enterappstart restart Important:Some implementations of the Avaya 310

Communication server requirementsAvaya 3100 Mobile Communicator Release 3.1 supports the following versions of AvayaCommunication Server 1000 (Avaya C

Prerequisites• You require the password to the nortel userid on the server.• You require the password to the superuser (root) userid on the server.1.

PrerequisitesYou must be logged into the server as nortel. For more information, see Accessing the servercommand line as nortel on page 159.1. To veri

Important:This procedure does not restore the shared files for the Instant Conferences.1. To stop the server processes, enter the following command:a

Chapter 18: Appendix A: Installationworksheets and checklistThis section contains worksheets to capture the system information and a checklist to assi

ConfigurationparameterValue NotesPrimary DNS Server RequiredSecondary DNS Server OptionalTertiary DNS Server OptionalNetwork Time Protocol(NTP) Clock

Configuration parameter Value NotesCommunicator Gateway stripsthis prefix for incoming calls toproduce the user name of theAvaya 3100 MC - Client user

Configuration parameter Value NotesLDAP attribute tag that contains theuser's business phone #LDAP attribute tag that contains theuser's mob

Item Done?Have the firewall rules (if needed) been configured to allow Avaya 3100 MobileCommunicator clients access to port 8080 (HTTP) or 8443 (HTTPS

Appendix A: Installation worksheets and checklist168 Deployment Guide October 2010

Chapter 18: Appendix B: Call flows fromCS 1000The following figure shows the call flow for receiving an incoming call.Figure 52: Receiving incoming ca

Avaya 3100 Mobile Communicator users should use the E.164 Fully Qualified InternationalNumbers for all stored Public Switched Telephone Network (PSTN)

Figure 53: Outgoing call flowAppendix B: Call flows from CS 1000170 Deployment Guide October 2010

IndexAAvaya 3100 MC - Client for BlackBerry ...13, 15, 16, 18,48BlackBerry Enterprise Server (BES) ...13, 15, 18Dialing plan ...

172 Deployment Guide October 2010

Avaya CS 1000 digit processing strips the CNTC and adds <AC1 + NATC> to produce614161234567Call to a number outside North AmericaA user initiate

Figure 3: Sample Avaya 3100 Mobile Communicator Gateway firewall configurationIf a user calls a client, the SIP signaling comes through the SPS. Real

© 2010 Avaya Inc.All Rights Reserved.NoticeWhile reasonable efforts have been made to ensure that theinformation in this document is complete and accu

The Avaya 3100 Mobile Communicator Gateway queries a corporate Lightweight DirectoryAccess Protocol (LDAP) server when the users use the Directory loo

Figure 4: Avaya 3100 Mobile Communicator Gateway high availability configurationA redundant system includes an active server and a standby server. Mob

Mobile Communicator Gateway stops responding, the clients switch to the other Avaya 3100Mobile Communicator Gateway. Important:The communication link

Chapter 5: EngineeringThis chapter details the engineering aspects of the Avaya 3100 Mobile Communicator (Avaya 3100 MobileCommunicator).Navigation•

Table 1: Avaya 3100 Mobile Communicator Gateway portsPort Protocol Function Applica- tion Configur-able?Configurein Avaya3100 MCG-to-EnterpriseFirewal

Port Protocol Function Applica- tion Configur-able?Configurein Avaya3100 MCG-to-EnterpriseFirewallpolicy?Configurein Avaya3100 MCGFirewallpolicy?serve

Port Protocol Function Applica- tion Configur-able?Configurein Avaya3100 MCG-to-EnterpriseFirewallpolicy?Configurein Avaya3100 MCGFirewallpolicy?manag

The following table lists the ports that are defined by the Enterprise Call Server (ECS). Youconfigure these ports on the ECS.Table 2: ECS portsProtoc

Engineering28 Deployment Guide October 2010

Chapter 6: Interworking requirements withCS 1000This chapter details the interworking requirements for the Avaya 3100 Mobile Communicator (Avaya 3100

ContentsChapter 1: New in this release...7Features...

Gateway contains the tag x-nt-net-feature=x-nt-home. For example, the following request URItriggers SBR:INVITE sip:[email protected];x-nt-sip-lin

- Each user requires one Universal Extension (UEXT). Each UEXT supports the SIPinterface on the client. Configure the UEXT with the Fixed Mobile Conve

Figure 5: Client with Avaya CS 1000 and UDP on page 32 shows an example of clients usingAvaya CS 1000 and UDP.Figure 5: Client with Avaya CS 1000 and

Table 3: UEXT configuration parametersParameterDescription UDP example CDP exampleSubtype UEXT subtype; must beFMCLFMCL FMCLprimaryDNOn key 0; thisdet

Parameter Description Exampledialplan. Can be the last digit of the mobilityprefix with the User’s ESN DN.L1 DN prefix not requiredAuthenticationenabl

TYPE RDB CUST 00 DMOD ROUT 10 DES IPROUTE TKTP TIE ... VTRK YES ZONE 100 PCID SIP ... ANTK SIGO ESN5 STYP SDAT Important:If the Route Data Block (RD

For more information, see Avaya 3100 Mobile Communicator and Avaya CommunicationServer 1000 Solution Integration Guide, NN49000-315 and Avaya Communic

MWFB TRCL CRTOD CRDAY CRHOLLD 11 configures the number of ringing cycles for CFNA. Configure the CFN index thatcorresponds to the RCO entry configured

Trunk calculation: Method 1Follow these steps:1. Add the number of client users.2. Locate the resulting number in the Number of Users column in Table

Number ofusersParameter Up to 6CCS perUserUp to 12CCS perUserUp to 18CCS perUserUp to 24CCS perUser300PSTN 68 125 180 238SIP Access Port 136 250 360 4

Parameter: Area Code...51Para

3. Use Table 6: Trunk traffic Poisson 1 percent blocking on page 40 to find the CCSvalue and obtain the number of PSTN trunks (in the cell to the left

Trunks CCS Trunks CCS Trunks CCS Trunks CCS25 535 75 2028 125 3616 175 524526 562 76 2059 126 3648 176 527727 590 77 2091 127 3681 177 531028 618 78 2

The number of SIP Access Ports is the number of PSTN trunks multiplied by 2, which is28 x 2 = 56.UEXT calculationsYou require one UEXT for each Avaya

AvayaCS 1000MobileExtensionAvaya3100 MC -Web UIAvaya3100 MC -ClientSupport for any phone (mobile, home phone, other) √ √RequiresinstalledclientMid Cal

Call Detail RecordingThe mobile clients support Call Detail Recording (CDR) for all calls initiated or accepted by themobile clients.Interpret the CDR

mobile client that the user answers on the mobile phone generate four CDR records on thehome Avaya CS 1000 .• The first CDR record provides details of

Interworking requirements with CS 100046 Deployment Guide October 2010

Chapter 7: Deployment planningThis section describes the planning required to deploy the Avaya 3100 Mobile Communicator with theEnterprise Call Serve

Licensing requirementsAvaya Communication Server 1000 licensing requirements:• Requires the Avaya Communication Server 1000 Release and corresponding

The Avaya 3100 Mobile Communicator Gateway manages the client license keys using sitelicenses. For more information about Avaya 3100 Mobile Communicat

Configuring network control parameters data block...101Configuring

Figure 7: SIP GW CLID ParametersFor all public calls (subscriber [for example, NXX in North America], national [for example, NPAin North America], or

• Subscriber/Number of Digits to strip• Subscriber/Prefix to insert• National/Number of Digits to strip• National/Prefix to insertThe E.164 format of

Parameter: National / Prefix to insertFor incoming national (NPA) calls this parameter defines the prefix to insert after stripping anydigits necessar

Data access planningThis section describes things to consider when planning data access.Avaya CS 1000 data access considerations on page 53Avaya CS 10

Example: sip:[email protected] the mobility prefix on the Avaya 3100 Mobile Communicator Gateway configurationtab as the incoming prefi

Redirection Prime (MARP) TN in the Multiple Access Directory Number (MADN) group of theAvaya 3100 MC - Client user.Caller ID tableDeployment Guide Oct

Deployment planning56 Deployment Guide October 2010

Chapter 8: Deployment work flowThis section describes the order in which to install the Avaya 3100 Mobile Communicator system and thento interwork th

• Avaya 3100 Mobile Communicator Gateway installation on page 63• Solution commissioning on page 92• Validate deployment on page 129Deployment work fl

Chapter 9: Deployment prerequisitesThis section describes the prerequisites for Avaya 3100 Mobile Communicator and Avaya CommunicationServer 1000 (Av

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

Task Reference CommentsConfiguration, 553-3031-210Avaya CommunicationServer 1000E: Installationand Commissioning,NN43041-310The CS 1000 must have thel

Task Reference CommentsAvaya 3100 MobileCommunicator is Release3.1.If using BlackBerry devicesand the BlackBerryEnterprise Server (BES), thedevices an

Checking the Avaya CS 1000 release from the command lineUse this procedure to check the version of the CS 1000 using the command line.1. Log in to the

Chapter 10: Avaya 3100 MobileCommunicator GatewayinstallationThis chapter contains the instructions for installing a new Mobile Communications Gateway

Figure 10: Installation workflowResultWorkflow navigation• Preparation on page 65•Installation on page 72• Commissioning on page 74• Solution commissi

Workflow Time to complete taskSolution commissioning 4 hours, plus 20 minutes per userPreparationThis section describes the tasks required to prepare

Figure 11: Preparation taskflowPreparation workflow navigation• Installing the Linux base on page 67• Verifying the Enterprise network on page 71Table

Installing the Linux baseFor installation instructions for the Avaya CS 1000 Linux base, see Linux Platform Base andApplications Installation and Comm

1. Insert the Linux base bootable CD-ROM in the CD-ROM tray.2. Reboot the server.3. Choose the method of installation:• To install using a serial cons

The Time zone selection for region screen appears.Figure 13: Time zone selection window11. At the prompt, in the Timezone Selection for Region screen,

Chapter 1: New in this releaseThis section details what’s new in Avaya 3100 Mobile Communicator Deployment Guide, NN42030-301for Avaya 3100 Mobile Co

Note 2: You can use Base Manager to modify the static lookup table for host names.18. In the Configuration Validation 2 screen, type Y if the informat

Verifying the Enterprise networkInstall and configure on the enterprise network:• Domain Name Server (DNS) (required)• Lightweight Directory Access Pr

InstallationThis section describes the software installation. Important:Use the server system console for installations and upgrades. Do not use a rem

Job aid: Admin shell accessMany of the maintenance procedures require that you access the admin shell and log on usingthe nortel user account. You hav

7. At the prompt for the mode, do one of the following:• If the Avaya 3100 Mobile Communicator Gateway configuration is notredundant, select Standalon

Prerequisites• The Avaya 3100 Mobile Communicator Gateway software must be installed on the server.• You must be logged into the Avaya 3100 Mobile Com

PrerequisitesYou must be logged into the Avaya 3100 Mobile Communicator Web Administration Consoleas administrator. For more information, see Logging

Field DescriptionThis parameter applies to both servers in the redundantconfiguration.Domain Enter the SIP registration domain defined on theEnterpris

Field DescriptionThis parameter applies to both servers in the redundantconfiguration.Secondary ECS Address Enter the address and port of the secondar

Field DescriptionBlackBerry, Avaya 3100 MC - Client for WindowsMobile, and Avaya 3100 MC - Client for Nokia users toplace calls directly from their wi

New in this release8 Deployment Guide October 2010

Field Description9, entered in any combination. The default value is *,which needs to be changed only if it conflicts with othernetwork resources.For

Field DescriptionLDAP attribute tag that containsthe user's last nameEnter the tag for the User Last Name attribute on theLDAP server. The defaul

1. Click the System Configuration tab.2. Select Gateway Actions > Configure Gateway.3. Click Edit.4. Click the corresponding link for Dialplan Conv

When you write a rule with the ^ sign, the Avaya 3100 Mobile Communicator Gateway replacesonly the leading occurrence of the string of what is on the

Figure 16: Device configuration tab2. Click Edit.3. Modify the Device settings.4. Click Save.The new device settings apply for the next successful log

Field DescriptionExternal: Use Secure Connection Select Yes to enable HTTPS connections on theprimary Avaya 3100 Mobile Communicator Gatewaypublic int

Field DescriptionConfigure this parameter if your Avaya 3100 MobileCommunicator system implementation usesBlackBerry devices that use the BES.Internal

Field DescriptionSelect Enable to require users to enter a prefix everytime they make an outgoing call. This setting is usefulif your dial plan does n

6. To save the changes, click OK.7. Click Save.Adding the Avaya 3100 Mobile Communicator GatewaylicenseThis procedure installs the license file on the

6. Click Open.7. Click Install.8. Click Close.9. On a redundant system, repeat step 3 on page 88 to step 8 on page 89 on thesecond server. Important

Chapter 2: IntroductionThis document guides you through the deployment steps for Avaya 3100 Mobile Communicator (Avaya3100 Mobile Communicator). Thes

Procedure job aidUse the following table to help you understand the Gateway Server System status fields.Field DescriptionIP Address Contains the IP Ad

Field Description• You can access the alarm log file from the Toolspage under Server Logs.• To clear an alarm, you must solve the original errorcondit

Solution commissioningThis section describes the final steps required to obtain a fully-working Avaya 3100 MobileCommunicator (Avaya 3100 Mobile Commu

For more information, see Avaya 3100 Mobile Communicator Administration andSecurity, NN42030-600.6. After the interworking with the network is functio

Avaya 3100 Mobile Communicator Gateway installation94 Deployment Guide October 2010

Chapter 11: Avaya CS 1000 configuration forclient supportBefore implementing IP Peer Networking with the Avaya 3100 Mobile Communicator Gateway, somep

Task flow navigationComplete the tasks in the order that they appear in the following list:• Configuring zones on page 97• Configuring a D-channel for

• Forwarding Service DN to Avaya 3100 Mobile Communicator Gateway onpage 103• Configuring a Handoff key on page 105•Configuring a HOT P key on page 10

1. Log on to Element Manager.2. In the navigation pane, select Routes and Trunks, D-Channels.If this is the first time that this Web page is accessed,

The Routes and Trunks Web page opens.2. Click Add route associated with the customer.The Customer xx, New Route Configuration Web page opens (where xx