Deployment Guide Avaya 3100 Mobile Communicator 3.1 NN42030-301, 01.
© 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.
Contents Chapter 1: New in this release.................................................................................................7 Features............................................................................................................................................................7 Other changes...................................................................................................................................................7 Chapter 2: Introduction......................
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.............................................
Configuring network control parameters data block......................................................................................101 Configuring ESN access codes.....................................................................................................................101 Configuring the Route List Block...................................................................................................................102 Coordinated Dialing Plan.................................................
Chapter 15: Maintenance......................................................................................................151 Navigation.....................................................................................................................................................151 Removing a Service Upissue........................................................................................................................151 Job Aid...............................................................
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.
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.
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.
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).
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.
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-ti
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 Avaya CS 1000 package requirements on page 30. Avaya 3100 Mobile Communicator Release 3.
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.
Planning Avaya CS 1000 digit processing strips the CNTC and adds to produce 614161234567 Call to a number outside North America A user initiates a call to a contact with the phone number +41123456789. The URI incoming for the SIP INVITE for the call is sip: +41123456789@domain.com;user=phone Avaya CS 1000 digit processing adds to produce 601141123456789.
Security requirements Figure 3: Sample Avaya 3100 Mobile Communicator Gateway firewall configuration 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.
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.
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.
Planning Mobile Communicator Gateway stops responding, the clients switch to the other Avaya 3100 Mobile Communicator Gateway. Important: 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.
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.
Engineering Table 1: Avaya 3100 Mobile Communicator Gateway ports Port 24 Protocol Function 21 Transmissi on Control Protocol (TCP) File Transfer Protocol (FTP) Base Linux No No No 22 TCP Secure Shell Base Linux (SSH) No No No 53 User (Send Datagram only) Protocol (UDP) Domain Name Server (DNS) queries to external DNS server Base Linux No Yes, assuming DNS is within the Enterprise network No 123 TCP (Send only) Network Time Protocol (NTP) Base Linux No Yes, assuming DNS is within
Port tables Port Protocol Function Applica- tion Configurable? Configure Configure in Avaya in Avaya 3100 MCG- 3100 MCG toFirewall Enterprise policy? Firewall policy? server and the Avaya 3100 Mobile Communicat or Gateway Administrati on server 3306 TCP SQL Client Access 5060 Session Initiation Protocol (SIP) (UDP) 5072 No No No Avaya 3100 Avaya 3100 MCG listen MCG port for Voice over IP (VoIP) Signalling Yes Yes No SIP (UDP) Avaya 3100 MCG listen port for VoIP Signalling (Instant Call
Engineering Port Protocol Function Applica- tion Configurable? Configure Configure in Avaya in Avaya 3100 MCG- 3100 MCG toFirewall Enterprise policy? Firewall policy? managemen t only) 8443 HTTPS (TCP) Avaya 3100 MC - Client Secure Client Interface 8553 TCP 9800 9801 Avaya 3100 MCG Yes 8440 to No 8449 Yes Avaya 3100 Avaya 3100 MCG Secure MCG Admin Admin Interface (standalone managemen t only) No No No TCP Avaya 3100 MCG Server Java Virtual Machine (JVM) Avaya 3100 MCG JVM No No No
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-toEnterprise Firewall policy? Configure in the Internet-to-Avaya 3100 Mobile Communicator Gateway Firewall policy? RTP (UDP) VoIP send port for the Gateway server. Configured on the Avaya 3100 MCG.
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).
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:+16131234567@avaya.com;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.
Avaya CS 1000 engineering for Avaya 3100 Mobile Communicator - Each user requires one Universal Extension (UEXT). Each UEXT supports the SIP interface on the client. Configure the UEXT with the Fixed Mobile Convergence Line (FMCL) subtype. The FMCL subtype requires an Incremental Software Management (ISM) independent of the Mobile Extension (MOBX) subtype. - SIP Access Port license • SIP Gateway • SPS, using the Avaya CS 1000 NRS-SPS on the Linux-based NRS.
Interworking requirements with CS 1000 Figure 5: Client with Avaya CS 1000 and UDP on page 32 shows an example of clients using Avaya CS 1000 and UDP. Figure 5: Client with Avaya CS 1000 and UDP Figure 6: Client with Avaya CS 1000 and CDP on page 32 shows an example of clients using Avaya CS 1000 with CDP. Figure 6: Client with Avaya CS 1000 and CDP The UEXT configuration requirements are shown in the following table.
Avaya CS 1000 engineering for Avaya 3100 Mobile Communicator Table 3: UEXT configuration parameters Paramete r Description UDP example FMCL CDP example Subtype UEXT subtype; must be FMCL FMCL primary DN On key 0; this 5335 contributes to an determines the user's ESN of 3435335 and a published addresses for DID of +16139615335 both private electronic switched network (ESN) and public direct inward dial (DID).
Interworking requirements with CS 1000 Parameter Description Example dialplan. Can be the last digit of the mobility prefix with the User’s ESN DN. L1 DN prefix not required Authentication enabled Determines if Authentication is required. Authentication on Authentication password The password for authentication xxxxxxxx For information about SIP Gateway configuration, see IP Peer Networking Installation and Commissioning, NN43001-313.
Device Handoff configuration 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 (RDB) already has associated Virtual Trunks and is configured to SIGO STD, you must remove all Virtual Trunks before you can change the RDB to ESN5. Device Handoff configuration Device handoff permits the Avaya 3100 Mobile Communicator user to hand off an established call between the mobile phone and the desk telephone.
Interworking requirements with CS 1000 For more information, see Avaya 3100 Mobile Communicator and Avaya Communication Server 1000 Solution Integration Guide, NN49000-315 and Avaya Communication Server 1000 Features and Services Fundamentals, NN43001-106. Avaya CS 1000 system redundancy The clients support a high availability configuration for improved redundancy and failover. Configure the client with primary and secondary proxy addresses that refer to different NRSSPSs.
Avaya CS 1000 capacity requirements MWFB TRCL CRTOD CRDAY CRHOL LD 11 configures the number of ringing cycles for CFNA. Configure the CFN index that corresponds to the RCO entry configured in LD 15 (for example, RCO 1 uses CFN 1).
Interworking requirements with CS 1000 Trunk calculation: Method 1 Follow these steps: 1. Add the number of client users. 2. Locate the resulting number in the Number of Users column in Table 5: Poisson trunk table on page 38. 3. Select the appropriate PSTN and SIP Access Port parameters based on the required CCS per Users. Table 5: Poisson trunk table on page 38 uses a Poisson value of P.01, which represents 1 percent blocking.
Trunk calculation: Method 2 Number of users 300 400 500 600 700 800 900 1000 Parameter Up to 6 CCS per User Up to 12 CCS per User Up to 18 CCS per User Up to 24 CCS per User PSTN 68 125 180 238 SIP Access Port 136 250 360 476 PSTN 82 162 238 317 SIP Access Port 164 324 476 634 PSTN 106 198 297 396 SIP Access Port 212 396 594 792 PSTN 125 238 356 475 SIP Access Port 250 476 712 950 PSTN 144 277 416 554 SIP Access Port 288 554 832 1108 PSTN 162
Interworking requirements with CS 1000 3. Use Table 6: Trunk traffic Poisson 1 percent blocking on page 40 to find the CCS value and obtain the number of PSTN trunks (in the cell to the left of the CCS number). If the CCS value is between two values in the trunks column, choose the higher number of trunks. For trunk traffic greater than 6068 CCS, allow 30.34 CCS per trunk. 4. Multiply the number of PSTN trunks by two to obtain the number of SIP Access Ports required.
Trunk calculation: Method 2 Trunks CCS Trunks CCS Trunks CCS Trunks CCS 25 535 75 2028 125 3616 175 5245 26 562 76 2059 126 3648 176 5277 27 590 77 2091 127 3681 177 5310 28 618 78 2122 128 3713 178 5343 29 647 79 2153 129 3746 179 5376 30 675 80 2184 130 3778 180 5409 31 703 81 2215 131 3810 181 5442 32 732 82 2247 132 3843 182 5475 33 760 83 2278 133 3875 183 5508 34 789 84 2310 134 3907 184 5541 35 818 85 2341 13
Interworking requirements with CS 1000 The number of SIP Access Ports is the number of PSTN trunks multiplied by 2, which is 28 x 2 = 56. UEXT calculations You require one UEXT for each Avaya 3100 MC - Client user. Avaya CS 1000 and supported Avaya 3100 Mobile Communicator features The following table describes the Avaya 3100 Mobile Communicator call features.
Avaya CS 1000 and supported Avaya 3100 Mobile Communicator features Avaya Avaya Avaya CS 1000 3100 MC - 3100 MC Mobile Web UI Client Extension Support for any phone (mobile, home phone, other) √ √ Requires installed client Mid Call Features—Hold, Retrieve, Consultation Call, Transfer, Conference Using DTMF Using DTMF √ X √ √ Enterprise Voicemail MWI Using thirdparty application √ √ Advanced Call Control—Direct Outbound calls from mobile via the enterprise voice network Carrier support requi
Interworking requirements with CS 1000 Call Detail Recording The mobile clients support Call Detail Recording (CDR) for all calls initiated or accepted by the mobile clients. Interpret the CDR records according to the type of call made or received by the mobile clients. Direct outbound call When a user makes an outgoing call, the mobile client user's home Avaya CS 1000 generates two CDR records. • The first CDR record provides details of the call from the mobile phone to the service DN.
Incoming call mobile client that the user answers on the mobile phone generate four CDR records on the home Avaya CS 1000 . • The first CDR record provides details of the incoming call to the Multiple Appearance DN (MADN). In this record, the originator is the caller and destination is the multiple appearance DN where the UEXT is configured. • The second CDR record provides the details of the UEXT extended call to the Avaya 3100 Mobile Communicator Gateway (the target DN of the UEXT).
Interworking requirements with CS 1000 46 Deployment Guide October 2010
Chapter 7: Deployment planning This section describes the planning required to deploy the Avaya 3100 Mobile Communicator with the Enterprise Call Server (ECS).
Deployment planning Licensing requirements Avaya Communication Server 1000 licensing requirements: • Requires the Avaya Communication Server 1000 Release and corresponding Linux Baseed NRS • Uses SIP Access Port Licenses for Avaya CS 1000 SIP infrastructure support • Avaya CS 1000 requires 1 Universal Extension (UEXT) for each Avaya 3100 MC - Client user. The UEXT is configured with the Fixed Mobile Convergence Line (FMCL) subtype.
Avaya 3100 Mobile Communicator Gateway licenses The Avaya 3100 Mobile Communicator Gateway manages the client license keys using site licenses. For more information about Avaya 3100 Mobile Communicator Gateway licensing, see Avaya 3100 Mobile Communicator Gateway licenses on page 49. A device which connects using the Avaya 3100 MC - Client or the Avaya 3100 MC - Web UI only consumes one license. The user cannot be connected through the Avaya 3100 MC - Client and the Avaya 3100 MC - Web UI at the same time.
Deployment planning Figure 7: SIP GW CLID Parameters For all public calls (subscriber [for example, NXX in North America], national [for example, NPA in North America], or international) E.164 fully qualified numbers are used to represent the caller.
Avaya CS 1000 SIP Gateway CLID Parameters configuration • Subscriber/Number of Digits to strip • Subscriber/Prefix to insert • National/Number of Digits to strip • National/Prefix to insert The E.164 format of subscriber calls (for example, NXX in North America) is: +. The parameters Subscriber/Number of digits to strip and prefix to insert are used to modify the format of subscriber numbers presented from the PSTN due to region specific requirements. The E.
Deployment planning Parameter: National / Prefix to insert For incoming national (NPA) calls this parameter defines the prefix to insert after stripping any digits necessary from the incoming phone number prior to conversion to E.164 format. Mobility prefix Before configuring and deploying the Avaya 3100 Mobile Communicator solution, the administrator determines the mobility prefixfor the Avaya 3100 Mobile Communicator Gateway.
Data access planning Data access planning This section describes things to consider when planning data access. Avaya CS 1000 data access considerations on page 53 Avaya CS 1000 data access considerations The Avaya 3100 Mobile Communicator Gateway requires data access to the TLAN of the Avaya CS 1000. The Avaya 3100 Mobile Communicator Gateway uses the Avaya CS 1000 SPS as the SIP Signaling Proxy.
Deployment planning Example: sip:8885066404681@avaya.com Configure the mobility prefix on the Avaya 3100 Mobile Communicator Gateway configuration tab as the incoming prefix for call termination. Configure the Service DN field on the Avaya 3100 Mobile Communicator Gateway configuration with the service DN. Universal Extensions An Avaya CS 1000 Universal Extension (UEXT) represents each mobile client instance.
Caller ID table Redirection Prime (MARP) TN in the Multiple Access Directory Number (MADN) group of the Avaya 3100 MC - Client user.
Deployment planning 56 Deployment Guide October 2010
Chapter 8: Deployment work flow This section describes the order in which to install the Avaya 3100 Mobile Communicator system and then to interwork the Avaya 3100 Mobile Communicator with the Avaya Communication Server 1000 (Avaya CS 1000). Deploying the systems task flow Deploying the systems requires the following procedures.
Deployment work flow • Avaya 3100 Mobile Communicator Gateway installation on page 63 • Solution commissioning on page 92 • Validate deployment on page 129 58 Deployment Guide October 2010
Chapter 9: Deployment prerequisites This section describes the prerequisites for Avaya 3100 Mobile Communicator and Avaya Communication Server 1000 (Avaya CS 1000) integration.
Deployment prerequisites Task Reference Comments Configuration, 553-3031-210 Avaya Communication Server 1000E: Installation and Commissioning, NN43041-310 The CS 1000 must have the latest DEP List loaded.
Checking the Avaya CS 1000 release from Element Manager Task Reference Comments Avaya 3100 Mobile Communicator is Release 3.1. 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.
Deployment prerequisites Checking the Avaya CS 1000 release from the command line Use this procedure to check the version of the CS 1000 using the command line. 1. Log in to the Signaling server or the Enterprise Common Manager server using the nortel account. 2. Enter the following command swVersionShow The installed software applications and version numbers are displayed. For an example, see the following figure.
Chapter 10: Avaya 3100 Mobile Communicator Gateway installation This chapter contains the instructions for installing a new Mobile Communications Gateway 3100. For information about the Avaya 3100 Mobile Communicator - Client (Avaya 3100 MC - Client) installation, see Avaya 3100 Mobile Communicator Administration and Security, NN42030-600. Important: Use the server system console for installations and upgrades. Do not use a remote terminal.
Avaya 3100 Mobile Communicator Gateway installation Figure 10: Installation workflow Result Workflow navigation • Preparation on page 65 • Installation on page 72 • Commissioning on page 74 • Solution commissioning on page 92 Table 8: Complete installation times on page 64 shows the times for completing each of the above workflows.
Preparation Workflow Solution commissioning Time to complete task 4 hours, plus 20 minutes per user Preparation This section describes the tasks required to prepare for the installation of the Avaya 3100 Mobile Communicator Gateway. Important: Use the server system console for installations and upgrades. Do not use a remote terminal. Before you begin, review Appendix A: Installation worksheets and checklist on page 163 for useful worksheets and a checklist.
Avaya 3100 Mobile Communicator Gateway installation Figure 11: Preparation taskflow Preparation workflow navigation • Installing the Linux base on page 67 • Verifying the Enterprise network on page 71 Table 9: Preparation times on page 66 shows the estimated times for completing each of the above procedures.
Installing the Linux base Installing the Linux base For installation instructions for the Avaya CS 1000 Linux base, see Linux Platform Base and Applications Installation and Commissioning, NN43001-315. Important: Carefully observe the labels for the network interfaces of the specific platforms. During the Linux base installation for Avaya 3100 Mobile Communicator Gateway, you make two platform-specific configuration changes. • Physical connection—Use only the eth1 physical network interface.
Avaya 3100 Mobile Communicator Gateway installation 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 console on COM1, type com1 at the boot prompt and press Enter. • To install using an attached keyboard, video monitor, and mouse, type kvm at the boot prompt and press Enter. Note: It is not required to attach a keyboard, video monitor and mouse (KVM) to view output.
Installing the Linux base The Time zone selection for region screen appears. Figure 13: Time zone selection window 11. At the prompt, in the Timezone Selection for Region screen, type the appropriate time zone number and then press Enter to continue. 12.
Avaya 3100 Mobile Communicator Gateway installation 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 information is correct and press Enter, as shown in the Note: The CLI command hostconfig can be used to modify the static lookup table for host names. The Configuration Validation 2 screen appears with the correct information. Press Enter to continue. 19.
Verifying the Enterprise network Verifying the Enterprise network Install and configure on the enterprise network: • Domain Name Server (DNS) (required) • Lightweight Directory Access Protocol (LDAP) server (optional) Important: Avaya recommends that you program the DNS with the IP addresses of the License Server, the primary Enterprise Call Server (ECS), and the alternate ECS. You should ensure that the DNS and LDAP server can be accessed from the Avaya 3100 Mobile Communicator Gateway. 1.
Avaya 3100 Mobile Communicator Gateway installation Installation This section describes the software installation. Important: Use the server system console for installations and upgrades. Do not use a remote terminal. Installation task flow Figure 14: Installation taskflow on page 72 shows the required procedures.
Job aid: Admin shell access Job aid: Admin shell access Many of the maintenance procedures require that you access the admin shell and log on using the nortel user account. You have two options for admin shell access: • serial port connection • Secure Shell (SSH) For more information about accessing the admin shell, see Linux Platform Base and Applications Installation and Commissioning, NN43001-315.
Avaya 3100 Mobile Communicator Gateway installation 7. At the prompt for the mode, do one of the following: • If the Avaya 3100 Mobile Communicator Gateway configuration is not redundant, select Standalone mode. • If the Avaya 3100 Mobile Communicator Gateway configuration is redundant, select Active-Standby mode, and go to 8 on page 74. 8.
Configuring the Gateway settings Prerequisites • The Avaya 3100 Mobile Communicator Gateway software must be installed on the server. • You must be logged into the Avaya 3100 Mobile Communicator Web Administration Console as administrator. For more information, see Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as an administrator. • You are familiar with the configuration settings for the Avaya 3100 Mobile Communicator Gateway.
Avaya 3100 Mobile Communicator Gateway installation Prerequisites You must be logged into the Avaya 3100 Mobile Communicator Web Administration Console as administrator. For more information, see Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as an administrator. 1. Click the System Configuration tab. 2. Click Gateway Actions > Configure Gateway. 3. Click Edit. 4. Modify the Gateway settings.
Procedure job aid Field Description This parameter applies to both servers in the redundant configuration. Domain Enter the SIP registration domain defined on the Enterprise Call Server (ECS). This parameter applies to both servers in the redundant configuration. Gateway name Enter the gateway identity defined on the ECS for the Avaya 3100 Mobile Communicator Gateway. This parameter applies to both servers in the redundant configuration.
Avaya 3100 Mobile Communicator Gateway installation Field Description This parameter applies to both servers in the redundant configuration. Secondary ECS Address Enter the address and port of the secondary ECS. Format: : This parameter applies to both servers in the redundant configuration. Device Access HTTP Port Select the hypertext transport protocol (HTTP) port used by clients to access the system and to download software over the air.
Procedure job aid Field Description BlackBerry, Avaya 3100 MC - Client for Windows Mobile, and Avaya 3100 MC - Client for Nokia users to place calls directly from their wireless devices to other parties using the client's Direct Outbound call mode. The PSTN numbers that are dialed by the mobile on the PSTN are defined on the device configuration page.
Avaya 3100 Mobile Communicator Gateway installation Field Description 9, entered in any combination. The default value is *, which needs to be changed only if it conflicts with other network resources. For example, if clients use * to access conference features, then you must change the Mid-Call Cellular Prefix to a different value such as # or #99. This parameter applies to both servers in the redundant configuration.
Configuring the dial plan conversion parameters Field Description LDAP attribute tag that contains the user's last name Enter the tag for the User Last Name attribute on the LDAP server. The default is sn. This parameter applies to both servers in the redundant configuration. LDAP attribute tag that contains the user's display name Enter the tag for the User Display Name attribute on the LDAP server. The default is displayName. This parameter applies to both servers in the redundant configuration.
Avaya 3100 Mobile Communicator Gateway installation 1. Click the System Configuration tab. 2. Select Gateway Actions > Configure Gateway. 3. Click Edit. 4. Click the corresponding link for Dialplan Conversion List . Figure 15: Dialplan conversion list 5. In the Number box, type a number combination, and then click OK. 6. For each additional entry, click New Entry and in the Number box, type a new number combination. 7. To save the changes, click OK. 8. Click Save.
Configuring the device settings When you write a rule with the ^ sign, the Avaya 3100 Mobile Communicator Gateway replaces only the leading occurrence of the string of what is on the left side of the equal (=) sign with what is on the right. For example, you have a rule ^0=00. If the phone number dialed on the Avaya 3100 MC - Client is 0123456789, the number changes to 00123456789. However, if the phone number dialed is 01230123, the number changes to 001230123.
Avaya 3100 Mobile Communicator Gateway installation Figure 16: Device configuration tab 2. Click Edit. 3. Modify the Device settings. 4. Click Save. The new device settings apply for the next successful logon by each user. On a redundant system, the gateways automatically share the device settings. Procedure job aid Use the following table to help you understand the Devices settings.
Procedure job aid Field Description External: Use Secure Connection Select Yes to enable HTTPS connections on the primary Avaya 3100 Mobile Communicator Gateway public interface using security certificates on the clients on Avaya 3100 Mobile Communicator Gateway. Select No to enable HTTP. Use HTTPS when the clients use certificates to encrypt communication with the Avaya 3100 Mobile Communicator Gateway.
Avaya 3100 Mobile Communicator Gateway installation Field Description Configure this parameter if your Avaya 3100 Mobile Communicator system implementation uses BlackBerry devices that use the BES. Internal: Use Secure Connection Select Yes to enable HTTPS connections on the secondary Avaya 3100 Mobile Communicator Gateway private interface. Select No to enable HTTP.
Configuring the emergency telephone numbers Field Description Select Enable to require users to enter a prefix every time they make an outgoing call. This setting is useful if your dial plan does not support E.164 numbers. Default: Disable Default for Native Call Intercept Setting Defines the default setting to control the ability for users to make private calls that route through the Avaya 3100 Mobile Communicator Gateway. Private calls are calls placed through the native dialer.
Avaya 3100 Mobile Communicator Gateway installation 6. To save the changes, click OK. 7. Click Save. Adding the Avaya 3100 Mobile Communicator Gateway license This procedure installs the license file on the Avaya 3100 Mobile Communicator Gateway. This license file controls the number of users that can log in to the system. Prerequisites • You must be logged into the Avaya 3100 Mobile Communicator Web Administration Console as administrator.
Checking Gateway server status 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 the second server. Important: For information about troubleshooting license file problems, see Avaya 3100 Mobile Communicator Troubleshooting, NN42030-700. Checking Gateway server status Check the Gateway server status to view the information such as the number of connections and the system load.
Avaya 3100 Mobile Communicator Gateway installation Procedure job aid Use the following table to help you understand the Gateway Server System status fields. Field Description IP Address Contains the IP Address of the Gateway Server. Status information appears to the right of this field. Click the IP Address to view statistical data related to the associated server. If the IP Address displays in red, the server is not responding, which can indicate a server software problem or system outage.
Procedure job aid Field Description • You can access the alarm log file from the Tools page under Server Logs. • To clear an alarm, you must solve the original error condition. • Whenever the Avaya 3100 Mobile Communicator Gateway server stops, all alarms and informational messages clear. However, persistent error conditions (such as missing or incorrect configuration settings) immediately generate new alarms. To permanently delete an alarm, you must solve the original error condition.
Avaya 3100 Mobile Communicator Gateway installation Solution commissioning This section describes the final steps required to obtain a fully-working Avaya 3100 Mobile Communicator (Avaya 3100 Mobile Communicator) system. You perform these steps in order to have the system working with your Enterprise infrastructure. Before you perform these steps, the Avaya 3100 Mobile Communicator Gateway must be installed, commissioned, and configured.
Solution commissioning For more information, see Avaya 3100 Mobile Communicator Administration and Security, NN42030-600. 6. After the interworking with the network is functioning correctly, send e-mail messages to users that explain how to install and configure their clients. For more information, see Avaya 3100 Mobile Communicator Administration and Security, NN42030-600.
Avaya 3100 Mobile Communicator Gateway installation 94 Deployment Guide October 2010
Chapter 11: Avaya CS 1000 configuration for client support Before implementing IP Peer Networking with the Avaya 3100 Mobile Communicator Gateway, some prerequisite programming is required on the Call Server. This section assumes that the system is already installed and fully operational, that the Customer data Block (CDB) already exists, and the circuit-switched routes and trunks are already defined.
Avaya CS 1000 configuration for client support Task flow navigation Complete the tasks in the order that they appear in the following list: • Configuring zones on page 97 • Configuring a D-channel for virtual trunks on page 97 • Configuring virtual routes on page 98 • Configuring virtual trunks on page 100 • Configuring network control parameters data block on page 101 • Configuring ESN access codes on page 101 • Configuring the Route List Block on page 102 • Coordinated Dialing Plan on page 103 96 Deplo
Configuring zones • Forwarding Service DN to Avaya 3100 Mobile Communicator Gateway on page 103 • Configuring a Handoff key on page 105 • Configuring a HOT P key on page 106 • Configuring the SIP trunk gateway on page 107 • Configuring NRS on page 112 Configuring zones For information about configuring zones, see Converging the Data Network for VoIP Fundamentals, NN43001-260. Virtual Trunks must be configured with a different zone number than the endpoints.
Avaya CS 1000 configuration for client support 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, a message indicates that no D-channels are configured. Click OK. 3. Under the Configuration section, from the Choose a D-channel Number list, select a D-Channel number. 4. From the type list, select the type of D-Channel. 5. Click to-Add. 6. Choose the D channel Card Type (CYTP) of D-Channel is over IP (DCIP).
Configuring virtual routes 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 is the customer number). 3. Under Basic Configuration, fill in the required fields to create a new Virtual Trunk Route: • Select a Route Number (ROUT) from the drop-down list. • Select the Trunk Type (TKTP) = TIE trunk data block (TIE).
Avaya CS 1000 configuration for client support 11. Enter the appropriate information in the text boxes and in Basic Route Options, Network Options, General Options, and Advanced Configurations. 12. Click Submit. The Trunks and Routes Web page opens and the newly configured route is displayed for the customer. Configuring virtual trunks To configure Virtual Trunk, you can use Element Manager or LD 14 of the Command Line Interface. Use this procedure to configure a Virtual Trunk using Element Manager. 1.
Configuring network control parameters data block Configuring network control parameters data block To configure Network Control Parameters data block, you can use Element Manager or LD 87 of the command line interface (CLI). You must create a Network Control Parameters (NCTL) data block, if one does not exist. Use this procedure to create a Network Control Parameters (NCTL) data block using Element Manager. 1. Log on to Element Manager. 2.
Avaya CS 1000 configuration for client support • Enter a NARS/BARS Access Code (AC1) of up to four digits. Typically, the number is 9 for North America. Note: The code cannot conflict with any value in the numbering plan. • Enable Coordinated Dialing Plan feature for this customer (CDP). When enabled two additional fields appear. - Choose Maximum number of Steering Codes (MXSC) Note: Steering Codes are part of the customer numbering plan.
Coordinated Dialing Plan 8. Accept all other defaults. 9. Click Submit. Coordinated Dialing Plan A Coordinated Dialing Plan (CDP) permits a customer to define a simple dialing plan for an entire network. Each user within the network is assigned a unique 3-10 digit telephone number that does not conflict with any other in the network. All telephone numbers at a particular location must be the same length.
Avaya CS 1000 configuration for client support 4. In the navigation pane Dialing and Numbering Plans, Incoming Digit Translation 5. Click Customer Edit IDC. The Incoming Digit Conversion Property page opens. 6. Choose Digit Conversion Tree Number. Click New DCNO. 7. Enable Type: Send calling party DID. Figure 19: Digit Conversion Tree Configuration 8. Click Save. The Digit Conversion Tree Configuration page opens. Figure 20: Add Digit Conversion Tree 9. Click Add. The Add Incoming Digits page opens.
Configuring a Handoff key Figure 21: Edit Incoming Digits 10. Enter the DID DN Incoming Digits to be converted. 11. Enter the Converted Digits = Mobility Prefix + DID DN. 12. Click Save. The Digit Conversion Tree Configuration opens. Figure 22: Digit Conversion Tree Configuring a Handoff key Use this procedure to configure the Handoff Key on an existing telephone in Element Manager.
Avaya CS 1000 configuration for client support 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 Number of phones = 1 • Choose Customer = 0 • Choose Phone type = 2004P1 - IP Phone 2004P1 (example) 4. Click Preview. The Phone Details page opens.
Configuring the SIP trunk gateway • Choose Phone type = UEXT - Universal Extension 4. Click Preview. The Phone Details page opens. • Choose Customer Number = 0 • Enter Terminal Number = 252 00 01 02 (example) • Enter Designation = UEXT (example) • Enter Zone = 5 (example) Note: Do not use the VTRK Zone. Virtual Trunks must be configured with a different zone number than the endpoints. This Zone = MO. 5. Choose Key 00 = Prime DN, up to 7 digits. 6.
Avaya CS 1000 configuration for client support Figure 23: Signaling Server SIP 6. Select a SIP option from the Enable IP Peer Gateway (Virtual Trunk TPS) list. 7. Select Enable SIP Proxy/Redirect Server. 8. Verify the Local SIP Port. This is the port to which the gateway listens. The default is 5060. 9. Type the SIP Domain Name.
Configuring the SIP Gateway settings The Domain name is case sensitive and must match the Service Domain name configured in the NRS. 10. If authentication is enabled in the NRS, configure the SIP Gateway Endpoint Name and SIP Gateway Authentication Password to match the Gateway Endpoint name and Gateway Endpoint authentication password used by the SIP Redirect Server. 11. Click Save and Transfer. Configuring the SIP Gateway settings Perform the following procedure to configure the SIP Gateway settings.
Avaya CS 1000 configuration for client support Figure 24: SIP Gateway settings 5. Complete the following for the primary server. • Primary Proxy or Re-direct (TLAN) IP address: Enter the TLAN IP address of the server that hosts the NRS designated as the Primary Re-direct Server. • Supports Registration: Select to have the SIP Gateway register with the Primary NRS.
Configuring the SIP URI to NPI/TON mapping 1. Log on to Element Manager. 2. In the navigation pane click System > IP Network > Node: Servers, Media Cards. The Node Configuration page opens. 3. On the Node Configuration page, locate the node and click Edit. 4. Expand the SIP URI Map link. Figure 25: SIP URI map Important: The settings defined must be identical on each Call Server and the NRS. a. Enter Public E.164/National domain name = +1 b. Enter Public E.164/Subscriber domain name = +1613 c.
Avaya CS 1000 configuration for client support Restarting the Signaling Server There are two methods for restarting the Signaling Server: Warm restart 1. From the EM navigator select System > IP Network - Maintenance and Reports 2. Select the node that contains the Signaling Server to be restarted. Figure 26: Reset Signaling Server Cold restart Press the RST button on the faceplate of the Signaling Server. Configuring NRS The Network Routing Service (NRS) provides routing services to both SIP and H.
NRS Database interfaces with the database for viewing, adding, deleting, or modifying numbering plan configuration data and routing entries. All changes to the numbering plan database are carried out on the standby database. Changes that the administrator makes to the numbering plan database do not immediately affect call processing. The database must first be cut over to the active database by executing a database cut over command.
Avaya CS 1000 configuration for client support Figure 28: Database switched 3. Click the Commit. Figure 29: Database committed The databases are synchronized. Both databases are changed. Configuring Domain names on the NRS Perform the following procedure to configure the Domain name on the Network Routing Service (NRS). 1. Open NRS Manager by doing one of the following: In ECM, select Network > Elements and then select the NRS from the Elements page.
Configuring Domain names on the NRS Figure 30: NRS Server 2. Click Numbering Plans > Domains. Figure 31: Service Domains (1) 3. Ensure Standby database is selected. The Standby database is used for administrator changes. 4. Ensure the required domain is available or click Add to add it. Figure 32: Edit Service Domain 5. Ensure that the correct service domain, L1 domain, and L0 domain are available or Add them.
Avaya CS 1000 configuration for client support 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 not cut over and commit the database, until after you complete all of the configuration procedures. Configuring gateway endpoints on the NRS Perform the following procedure to configure the gateway endpoints on the Network Routing Service (NRS).
Configuring gateway endpoints on the NRS 1. Open NRS Manager by doing one of the following: In Element Manager, select Network, Elements and select the NRS from the Elements page. OR In Internet Explorer, enter the IP address of the NRS into the address bar. 2. Ensure Standby database is selected. The Standby database is used for administrator changes. 3. Click Numbering Plans, Endpoints. The search for Endpoints page appears. Figure 35: Gateway Endpoints 4.
Avaya CS 1000 configuration for client support Figure 36: Add Gateway Endpoint 5. For Endpoint name, type a relevant endpoint name. Example: 3100MCG Note: Endpoint names are case sensitive and must match. 6. Ensure that Tandem Gateway Endpoint name is blank.
Adding a User Endpoint 7. Ensure that Endpoint Authentication Enabled is configured to Authentication Off. 8. For SIP support, select Dynamic SIP endpoint. 9. For SIP transport, select the transport protocol type. The Avaya 3100 Mobile Communicator supports UDP. 10. Type a value for the SIP port, or leave the default value of 5060. 11. Click Save. 12. Cut over and commit database. See Committing NRS Database on page 113.
Avaya CS 1000 configuration for client support The User Endpoints pane contains User Endpoints for (Service Domain / L1 Domain / L0 Domain). 3. Click Numbering Plans, Endpoints. The search for Endpoints page appears. Figure 37: Search User Endpoints 4. Ensure that the correct domain, L1 domain, and L0 domain, and Gateway Endpoints are selected and click Add. The Add User Endpoint Web page opens. Figure 38: Add User Endpoint 5. Complete the mandatory fields using the Job Aid.
Adding a User Endpoint 6. Complete the optional fields as appropriate. 7. Click the Save button. The standby database is updated. The Endpoints Web page opens, showing the newly added User Endpoint in the User Endpoints pane. 8. If required, click Add to add additional User Endpoints. The User Endpoints Web page displays any new endpoints. Figure 39: User Endpoints Important: A maximum of 100 user endpoints can be displayed on the User Endpoints Web page.
Avaya CS 1000 configuration for client support Job Aid The following table to understand the Add User Endpoint Web page fields. Field Description User name Enter a User name for the endpoint. The endpoint’s user name must be alphanumeric (a…z, A…Z, 0…9) and can be up to 30 characters in length. The user name, together with the Service Domain names, becomes a string that is used to build the user’s SIP URI. Frequently, this field is configured with the user's extension number.
Adding an NRS Routing rule for the Avaya 3100 Mobile Communicator Gateway 1. Open NRS Manager by doing one of the following: In Element Manager, select Network, Elements and select the NRS from the Elements page. OR In Internet Explorer, enter the IP address of the NRS into the address bar. 2. Ensure Standby database is selected. The Standby database is used for administrator changes. 3. Select Routes. The Routing Entries for (Service Domain / L1 Domain / L0 Domain / Endpoint) pane appears. 4.
Avaya CS 1000 configuration for client support Figure 41: Adding routing entry MGC 3100 6. Click Save. The standby database is updated. The Routes web page opens, displaying the newly added routing entry in the Routing Entries pane. 7. Ensure your Routing Entries page displays the Mobility Prefix (888) for the DN Prefix and has the 3100 MCG Endpoint Name (3100mcg) in the Context field. Figure 42: Routing entry mobility prefix 8. Cut over and commit database, see Committing NRS Database on page 113.
Adding an NRS Routing rule for the Avaya CS 1000 Adding an NRS Routing rule for the Avaya CS 1000 Use this procedure to create an NRS Routing rule to route calls to the Avaya CS 1000. 1. Open NRS Manager by doing one of the following: In Element Manager, select Network, Elements and select the NRS from the Elements page. OR In Internet Explorer, enter the IP address of the NRS into the address bar. 2. Ensure Standby database is selected. The Standby database is used for administrator changes.
Avaya CS 1000 configuration for client support Communicator. In the example 46 is used to capture the DID DN numbers 4680-4689. Figure 44: Add routing entry Avaya CS 1000 6. Click Save. The standby database is updated. The Routes web page opens, displaying the newly added routing entry in the Routing Entries pane. 7. Ensure your Routing Entries page displays the DN Prefix with the leading digits for the DID DNs DN Prefix and has the CS 1000 Endpoint Name (cs1000ss) in the Context field.
Chapter 12: CallPilot MWI configuration This section describes the Call Pilot Message Waiting Indication (MWI) configuration for Avaya CS 1000 and Avaya CS 2100. MWI for Avaya CS 1000 For CallPilot to send message waiting indicator (MWI) notifications to the mobile clients, you must configure CallPilot with an alternate DN against the primary DN for the user. The alternate DN must be equal to the UEXT target DN used to extend SIP calls to the mobile clients.
CallPilot MWI configuration 128 Deployment Guide October 2010
Chapter 13: Validate deployment This section describes how to validate that the Avaya 3100 Mobile Communicator components and the Avaya Communication Server 2100 (Avaya CS 2100) Enterprise Call Server (ECS) integration is correct.
Validate deployment Validating Avaya 3100 Mobile Communicator Gateway registration Use this procedure to determine if the Avaya 3100 Mobile Communicator Gateway is registered to the Enterprise Communication Server (ECS).
Validating Avaya 3100 MC - Client for BlackBerry communication Figure 46: Successful registration The following figure shows an unsuccessful registration attempt with an alarm entry. Figure 47: Unsuccessful registration The following figure shows an unsuccessful registration attempt with the alarm entry details.
Validate deployment If you can view the Avaya 3100 Mobile Communicator Gateway User Portal, then you have proper communication between the client and the Avaya 3100 Mobile Communicator Gateway servers.
Validating Avaya 3100 Mobile Communicator and Avaya CS 1000 ECS deployment 6. Configure one of the clients to require encryption. Use this client in the remainder of this procedure. 7. Log in to the client using HTTPS. Validates that certificates are functioning correctly. 8. Dial the mobile device from another telephone. 9. Accept the call using the Avaya 3100 MC - Client. Tests that the setup (MADN, Simring, etc.) for incoming calls, the Call Server dial plan, and the routing are configured correctly.
Validate deployment 134 Deployment Guide October 2010
Chapter 14: Upgrade fundamentals This chapter describes the following upgrade paths: • Release 2.x to Release 3.0 upgrade • Release 3.0 to Release 3.1 upgrade • Service Upissue upgrade • Converting to a redundant configuration Important: Use the server system console for installations and upgrades. Do not use a remote terminal. Warning: During upgrades, users are logged out of the server being upgraded and redirected to the standby system (if available).
Upgrade fundamentals Upgrade work flow Figure 49: Upgrade workflow Workflow navigation • Upgrading from Release 2.x to Release 3.0 on page 136 • Upgrading from Release 3.0 to Release 3.1 on page 139 • Upgrading for a Service Upissue on page 147 Upgrading from Release 2.x to Release 3.0 This section describes the tasks to upgrade the Avaya 3100 Mobile Communicator Gateway from Release 2.x to Release 3.0. Important: Avaya 3100 Mobile Communicator Release 2.x cannot be directly upgraded to Release 3.1.
Upgrading from Release 2.x to Release 3.0 Important: You must upgrade both Avaya 3100 Mobile Communicator Gateway servers at the same time, and the IP addresses must not change. The client upgrades require unchanged gateway server addresses. Release upgrade taskflow Figure 50: Release upgrade task flow on page 137 shows the upgrade tasks. Figure 50: Release upgrade task flow Release upgrade task flow navigation • Capturing Release 2.
Upgrade fundamentals • Commissioning on page 74 • Solution commissioning on page 92 Important: When following the commissioning procedures for a Release 2.x to Release 3.0 upgrade, use the worksheet created in the upgrade task flow to guide the configuration steps. Table 13: Release 2.x to Release 3.0 upgrade times on page 138 shows the times for completing each of the above procedures. Table 13: Release 2.x to Release 3.0 upgrade times Workflow Time to complete task Capturing Release 2.
Upgrading from Release 3.0 to Release 3.1 Job Aid: Release 2.x parameter worksheet Fill in the following worksheet with the values from your Release 2.x system. Use the values when you commission your Release 3.0 system. Release 2.x parameter Corresponding Release 3.
Upgrade fundamentals Important: Upgrade one Avaya 3100 Mobile Communicator Gateway server and return it to service before upgrading the other server. As soon as you start the upgrade on the active system, the redundant server becomes the active server. Prerequisites Ensure that you have copies of the license file and any CA certificates backed up to a known location (for example, on the server disk in a folder in /tmp) before you start the upgrade procedure. Upgrading from Release 3.0 to Release 3.
Upgrading from Release 3.0 to Release 3.1 • Backing up the Avaya 3100 Mobile Communicator Gateway server databases on page 160 • Upgrading the Avaya 3100 Mobile Communicator Gateway software to a new software release on page 145 • (optional) Restoring the Avaya 3100 Mobile Communicator Gateway server databases on page 161 • (optional) If the database restore fails, follow Upgrade commissioning on page 147 Recording the Release 3.0 configuration parameters Use this procedure to record all the Release 3.
Upgrade fundamentals 11. Click the Tools tab. 12. In Table 16: Tools configuration on page 145, record the Tools configuration. Release 3.0 system configuration job aid Use the following tables to record your system configuration. Parameters that are not used in Release 3.1, or do not exist in Release 3.0, do not appear in these tables.
Upgrading from Release 3.0 to Release 3.1 Section DTR Release 3.0 field name Release 3.
Upgrade fundamentals Section Release 3.0 field name Release 3.1 field name LDAP tag for user's email LDAP attribute tag that contains the user's email address LDAP tag for user extension LDAP attribute tag that contains the user's home phone Server 1 configuration Server 2 configuration Table 15: Device settings configuration Section (3.0) Primary MG (3.1) Primary Avaya 3100 Mobile Communicator Gateway Release 3.0 field name External: Address (IP/host:Port) Release 3.
Upgrading the Avaya 3100 Mobile Communicator Gateway software to a new software release Section Release 3.0 field name Native Dialing Numbers Release 3.1 field name Configuration Native Dialing Numbers Auto-Download of Allow Client Override Allow Client Override Device Configuration Table 16: Tools configuration Section Admin Server Port Setting Release 3.0 field name Release 3.
Upgrade fundamentals • 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 agreement. 8. To agree to the license agreement, enter YES The software installation proceeds. Messages appear to show installation progress. After the installation completes, the configuration script starts automatically. 9. If you retained the data from the previous installation, cancel the configuration script and go to 13 on page 146.
Upgrading the Avaya 3100 Mobile Communicator Gateway software to a new software release Upgrade commissioning If the database restore fails, you need to recommission the system using the parameters saved in Recording the Release 3.0 configuration parameters on page 141. Prerequisites • You must be logged into the server as nortel. For more information, see Accessing the server command line as nortel on page 159. • You must know the root password to perform the following procedure.
Upgrade fundamentals Converting to a redundant configuration If the initial installation is a standalone configuration you can convert to a redundant configuration. Important: This procedure assumes that you are not performing an upgrade at the same time. Prerequisites • You have already configured the new server on the network. • You have already installed the Avaya 3100 Mobile Communicator Gateway software on the secondary server and cancelled the configuration.
Converting to a redundant configuration 8. Run the configuration script: /opt/MobilityGatewaybin/mgsetup.sh 9. At the prompt for the ethernet address, select the card that corresponds to the IP address of this Avaya 3100 Mobile Communicator Gateway server. 10. At the mode prompt, select 2 Active-Standby. 11. For Active-Standby mode, at the prompt, enter the following information: • Server name: the domain name (if defined) or the internal IP address of the primary Avaya 3100 Mobile Communicator Gateway.
Upgrade fundamentals 150 Deployment Guide October 2010
Chapter 15: Maintenance This chapter contains procedures used to maintain the software. Navigation • Removing a Service Upissue on page 151 • Uninstalling the Avaya 3100 Mobile Communicator system software on page 152 Removing a Service Upissue This procedure removes a Service Upissue (SU) from the system. Important: To completely remove the Avaya 3100 Mobile Communicator software from the system, see Uninstalling the Avaya 3100 Mobile Communicator system software on page 152.
Maintenance 4. Enter y. The RPM patch removal completes. 5. Enter su 6. At the prompt, enter 7. To complete the removal, enter /opt/mobilitybase-3.0-101a/ postunpatch.sh The server continues the removal, which ends with the message Pre uninstall phase done. Post uninstall phase done. Updating iptables rules: [ OK ] . 8. Enter the following command pout 9. To check the SU installation, enter pstat The server responds with information about the SU status. 10.
Uninstalling the Avaya 3100 Mobile Communicator system software Prerequisites You must be logged into the server as nortel. For more information, see Accessing the server command line as nortel on page 159. To delete the software, enter the following command: sudo rpm -e mobilitygw mobileclients eas_gcs_telephony eas_gcs_locale-en_US The rpm command removes the software from the system.
Maintenance 154 Deployment Guide October 2010
Chapter 16: Common procedures This chapter contains the following procedures: • Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as an administrator • Managing the server processes from the Web Administration Console on page 157 • Managing the server processes from the command line on page 158 • Accessing the server command line as nortel on page 159 • Accessing the server command line as superuser on page 159 • Backing up the Avaya 3100 Mobile Communicator Gateway server database
Common procedures OR https://:8553/adminserver 2. In the Username field, type the user name. 3. In the Password field, type the admin password. Important: Avaya recommends that you change the default administrator password. For more information, see Changing the Avaya 3100 Mobile Communicator Web Administration Console password on page 156. 4. Click Sign In. 5. Click a tab at the top of the Avaya 3100 Mobile Communicator Web Administration Console to view the corresponding page.
Managing the server processes from the Web Administration Console Prerequisites You must be logged into the Avaya 3100 Mobile Communicator Web Administration Console as administrator. For more information, see Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as an administrator on page 155. 1. On the Avaya 3100 Mobile Communicator Web Administration Console main page, click the Tools tab. 2.
Common procedures Prerequisites You must be logged into the Avaya 3100 Mobile Communicator Web Administration Console as administrator. For more information, see Logging on to the Avaya 3100 Mobile Communicator Web Administration Console as an administrator. 1. Click the System Configuration tab. The Status field indicates which server is currently active. In a single-server system, this is always the local server. • Running—The server is running.
Accessing the server command line as nortel appstart start 3. To stop the server, enter appstart stop 4. To restart the server, enter appstart restart Important: Some implementations of the Avaya 3100 Mobile Communicator Gateway do not include the restart command. Accessing the server command line as nortel Use this procedure to access the server command line as nortel. Prerequisites You require the password to the nortel userid on the server. 1. Use SSH to connect to the server. 2.
Common procedures 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. Use SSH to connect to the server. 2. At the userid prompt, enter nortel 3. At the password prompt, enter 4. To become the root user, enter su root 5. At the prompt, enter Variable definitions Variable Value The password associated with the nortel userid.
Restoring the Avaya 3100 Mobile Communicator Gateway server databases Prerequisites You must be logged into the server as nortel. For more information, see Accessing the server command line as nortel on page 159. 1. To verify that the backup directory exists, enter: ls /admin/nortel/backup You should see mobilitybase in the directory list. 2. To backup the current system configuration, enter: sudo /opt/mobilitybase/backup.
Common procedures Important: This procedure does not restore the shared files for the Instant Conferences. 1. To stop the server processes, enter the following command: appstart stop 2. To restore the backup, enter the following command: /opt/mobilitybase/restore.sh 3.
Chapter 18: Appendix A: Installation worksheets and checklist This section contains worksheets to capture the system information and a checklist to assist you during the installation of the Avaya 3100 Mobile Communicator system. • Linux base worksheet on page 163 • Avaya 3100 Mobile Communicator Gateway worksheet on page 164 • Avaya 3100 Mobile Communicator solution checklist on page 166 Linux base worksheet Use the following worksheet to capture required information during the Linux base installation.
Appendix A: Installation worksheets and checklist Configuration parameter Value Notes Primary DNS Server Required Secondary DNS Server Optional Tertiary DNS Server Optional Network Time Protocol (NTP) Clock Source Optional—Can be internal clock on COTS or IP. Avaya 3100 Mobile Communicator Gateway worksheet Use the following worksheet to capture required information for the Avaya 3100 Mobile Communicator Gateway installation.
Avaya 3100 Mobile Communicator Gateway worksheet Configuration parameter Value Notes Communicator Gateway strips this prefix for incoming calls to produce the user name of the Avaya 3100 MC - Client users. For example, if you configure 88888 as the Mobility HLOC, 888881234 is configured on the hotp key of a UEXT for DN 1234.
Appendix A: Installation worksheets and checklist Configuration parameter Value Notes LDAP attribute tag that contains the user's business phone # LDAP attribute tag that contains the user's mobile phone # LDAP attribute tag that contains the user's e-mail address LDAP attribute tag that contains the user's extension LDAP attribute tag that contains the user's home phone Avaya 3100 Mobile Communicator solution checklist Use the following checklist to ensure that you have everything you need for the ins
Avaya 3100 Mobile Communicator solution checklist Item Done? Have the firewall rules (if needed) been configured to allow Avaya 3100 Mobile Communicator clients access to port 8080 (HTTP) or 8443 (HTTPS) on the Avaya 3100 Mobile Communicator Gateway? Deployment Guide October 2010 167
Appendix A: Installation worksheets and checklist 168 Deployment Guide October 2010
Chapter 18: Appendix B: Call flows from CS 1000 The following figure shows the call flow for receiving an incoming call. Figure 52: Receiving incoming call flow The following figure shows the call flow for an outgoing call.
Appendix B: Call flows from CS 1000 Figure 53: Outgoing call flow 170 Deployment Guide October 2010
Index A Avaya 3100 MC - Client for BlackBerry ....13, 15, 16, 18, 48 BlackBerry Enterprise Server (BES) .........13, 15, 18 Dialing plan ..........................................................16 Enterprise Call Server (ECS) ...............................48 Avaya 3100 MC - Client for Nokia ...................13, 16, 48 Dialing plan ..........................................................16 Enterprise Call Server (ECS) ...............................48 Virtual Private Network (VPN) ....................
Deployment Guide October 2010
