Avaya One X Mobile 1.1

Avaya one-X Mobile Integration, Administration, and Maintenance Guide
18-602153 Issue 2 December 2008
2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document may be incorporated in future releases. For full support information, please see the complete document, Avaya Support Notices for Software Documentation, document number 03-600758. To locate this document on our Web site, simply go to http:// www.avaya.com/support and search for the document number in the search box. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all of the time and we have no control over the availability of the linked pages. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avayas standard warranty language, as well as information regarding support for this product, while under warranty, is available through the following Web site: http://www.avaya.com/support. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. 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://www.avaya.com/support.
Contents
Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What You Need to Know. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Avaya one-X Mobile Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Avaya one-X Mobile Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Whats New in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Tasks for New Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3: Integration with Avaya Equipment . . . . . . . . . . . . . . . . . . . . . . . . . Integration Task Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Integration with Avaya Communication Manager . . . . . . . . . . Validate Licensed Features . . . . . . . . . . . . . . . . . . . . . . . . . . Configure CTI Links in Avaya Communication Manager . . . . . . . . . . Configure IP Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure EC500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Feature Access Codes. . . . . . . . . . . . . . . . . . . . . Create a Configuration Set . . . . . . . . . . . . . . . . . . . . . . . . Configure EC500 for Avaya one-X Mobile Users . . . . . . . . . . . . Configure the Dial Prefix in the Route Pattern . . . . . . . . . . . . . . Configure the Confirmed Answer Feature (for CM 5.0 and above) . . . . . Configure SAT Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure DTMF Functionality (for CM 3.X and 4.X only) . . . . . . . . . . Determine Triplet Quantity . . . . . . . . . . . . . . . . . . . . . . . . Configure VDN Triplets . . . . . . . . . . . . . . . . . . . . . . . . . . Create Directory Ranges for VDNs . . . . . . . . . . . . . . . . . . . . Create VDN Triplets Manually . . . . . . . . . . . . . . . . . . . . . . . Create Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Virtual Extensions . . . . . . . . . . . . . . . . . . . . . . . . . Configure Mobile Feature Extensions (MFEs) for Virtual Extension Users Set Communication Server to Create and Send UCIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 9 10 10 11 12 13 13 13 14 15 15 19 19 20 20 21 22 23 24 25 25 26 27 29 29 30 30 31 32 35 35 37 37 40 40
Configure Integration with Avaya Application Enablement Services . . . . . . . . . . Validate Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
December 2008
Contents
Create a JTAPI User . . . . . . . . . . . . . Create a DMCC User . . . . . . . . . . . . . Network Configuration of AES . . . . . . . Configure Switch Connections in AES . . . Enable Unrestricted Access . . . . . . . . TSAPI Configuration (for AES 4.0 and 4.1) . TSAPI Configuration (for AES 4.2) . . . . . Create TSAPI Links . . . . . . . . . . . . . Reset AES Server . . . . . . . . . . . . . . Validate TSAPI Links . . . . . . . . . . . . Validate the ASAI Link . . . . . . . . . . TSAPI Test . . . . . . . . . . . . . . . . TR87 Configuration . . . . . . . . . . . . . Configure the DMCC Port . . . . . . . . Create Dial Plan Rules for the Switch . SMS Configuration. . . . . . . . . . . . . . Install the occsim Binary Patch. . . . . . . AES 3.x . . . . . . . . . . . . . . . . . . AES 4.0 and AES 4.0.x . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
40 41 41 42 43 44 45 45 46 46 46 47 47 47 49 49 50 50 51 51 52 53 54 54 54 55 57 57 57 58 58 58 58 59 59 60 61 62 62
Configure Integration with Avaya Modular Messaging . . . . Configure Modular Messaging 3.1 with MSS . . . . . . . Configure Modular Messaging 3.0 with MSS . . . . . . . Configure Modular Messaging with Exchange . . . . . . Configure the Exchange Administrative User . . . . . Create a Domain User . . . . . . . . . . . . . . . . . . Validate Exchange Administrative User Permissions .
Chapter 4: Integration with Cisco Equipment . . . . . . . . . . . . . . . . . . . . . . . . . Integration Task Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About CTI Devices used by Avaya one-X Mobile Server to Intercept Calls . . . . . . . CTI Route Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CTI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About Partitions and Calling Search Spaces . . . . . . Partition . . . . . . . . . . . . . . . . . . . . . . . . Calling Search Space . . . . . . . . . . . . . . . . . Example 1: Calling Search Space . . . . . . . . . . Example 2: Exact Match Takes Precedence . . . . . Example 3: Pattern Match . . . . . . . . . . . . . . . Example 4: Two Managed Phones in Same Partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prepare Partitions and Calling Search Spaces for the Avaya one-X Mobile Server . . .
December 2008
Contents
Add a Partition for Avaya one-X Mobile Server Managed Phones . . . . . . . Create a Partition for Interceptor CTI Route Points . . . . . . . . . . . . . . . Create a Calling Search Space for Interceptor CTI Route Points. . . . . . . . Include the Route Point Partition in other Calling Search Spaces . . . . . . . Calling Search Space Example with Route Point Partition . . . . . . . . . Modify Other Calling Search Spaces to Include the Route Point Partition Modify the MWI and Voicemail Ports Calling Search Space . . . . . . . . . . Create CTI Route Points for Intercepting Calls . . . . . . . . . . Understanding Patterns in Directory Numbers . . . . . . . . Create an Interceptor Route Point . . . . . . . . . . . . . . . Associate the JTAPI User with the Interceptor Route Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
62 63 64 66 66 67 68 68 69 69 70 72 73 74 75 75 75 75 75 76 76 78 80 81 82 82 84 84 85 86 86 87 88 89 90 93 93 95 95
Create the JTAPI user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transfer Route Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How the Avaya one-X Mobile Server uses Transfer Route Points . . . . . . . . Choose Directory Numbers for the Transfer Route Point. . . . . . . . . . . . . Allowed Characters Transfer Route Point Directory Numbers . . . . . . . . Interdigit Timeout Issues with Pattern Matching . . . . . . . . . . . . . . . Example: Matching Route Pattern . . . . . . . . . . . . . . . . . . . . . . . Example: Matching Directory Number . . . . . . . . . . . . . . . . . . . . . Route Plan Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use Multiple Transfer Route Points to Preserve Users Calling Search Spaces . Create a Transfer Route Point . . . . . . . . . . . . . . . . . . . . . . . . . . . Associate Transfer Route Points with the JTAPI User . . . . . . . . . . . . . .
Create a Pool of CTI Route Ports for Outbound calls . . . . . . . . . . . . . . . . . . . Modify AXL Throttle Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Phones for the Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Cisco CallManager to Correctly Pass Caller ID . . . . . . . . Method One: Preserve Caller ID via Route Pattern . . . . . . . . . . Modify the Route Pattern . . . . . . . . . . . . . . . . . . . . . . Modify the Route List Detail Configuration . . . . . . . . . . . . Method Two: Preserve Caller ID via External Phone Number Mask. . Set the External Phone Number Mask . . . . . . . . . . . . . . . Modify the Route Pattern for External Calls . . . . . . . . . . . . Modify the H.323 Gateway Settings in Cisco CallManager . . . . Modify the Route List Detail Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5: Avaya one-X Mobile Administrative Interface . . . . . . . . . . . . . . . . . . . Obtain the Avaya one-X Mobile License . . . . . . . . . . . . . . . . . . . . . . . . . . Avaya one-X Mobile Administration Status Screen . . . . . . . . . . . . . . . . . . . . Configure the Avaya one-X Mobile Server . . . . . . . . . . . . . . . . . . . . . . . . .
December 2008
Contents
Configure the Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Split Server Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 6: Avaya Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a CTI Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a New CTI Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy a CTI Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Voicemail Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Modular Messaging with Exchange Integration . . . . . . . . . . . . . . Configure Modular Messaging with MSS . . . . . . . . . . . . . . . . . . . . . . . Create a Corporate Directory Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure CTI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create VDNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administer Users . . . . . . . . . . . Import Users . . . . . . . . . . . . Manage Unlicensed Users . . . . License Selected Users . . . . Manage Licensed Users . . . . . . Change Class of Service . . . Reprovision Selected Users. . Unlicense Selected Users . . . Delete Selected Users . . . . . View User Details . . . . . . . . . Lost or Stolen Mobile Phone . No Longer an Employee . . . . Unlock one-X Mobile Account Configure a User as Virtual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
96 97 99 99 103 103 107 107 109 111 112 115 120 122 124 124 125 125 126 127 127 128 128 129 129 130 130 130 130 132 135 135 136 136 137 139 139
Configure Dial Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add a New Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 7: Serviceability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Control Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Route Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Trace Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View Component Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 8: Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . View License Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
December 2008
Contents
Chapter 9: Carrier Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Carrier Offset Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 10: Direct Call PBX Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 11: Cisco Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Cisco CallManager Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy a Provisioning Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Voicemail Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy a Voicemail Profile . . . . . . . . . . . . . . . . . . . . . . . . . . Edit a Voicemail Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . Ensure the Exchange Administrative User has Sufficient Permissions . . . . . . . . . . . . . . . . . . . . . . . . .
141 141 143 145 145 149 151 151 155 155 155 157 159 160 160 165 167 168 169 169 170 170 170 171 172 172 173 173 174 174 174 175 175 177 179 179
Create a Corporate Directory Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy a Corporate Directory Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . Edit a Corporate Directory Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create CTI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import Route Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manage Route Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Administer Users . . . . . . . . . . . Import Users . . . . . . . . . . . . Manage Unlicensed Users . . . . Change Class of Service . . . License Selected Users . . . . Manage Licensed Users . . . . . . Change Class of Service . . . Reprovision Selected Users. . Unlicense Selected Users . . . Delete Users . . . . . . . . . . View User Details . . . . . . . . . Lost or Stolen Mobile Phone . No Longer an Employee . . . . Unlock one-X Mobile Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configure Dial Plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Add a New Dial Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A: Log Cleaning Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule the Tomcat Log Cleaning Utility . . . . . . . . . . . . . . . . . . . . . . . . .
December 2008
Contents
December 2008
Chapter 1: Introduction
The Avaya one-X Mobile Integration, Administration, and Maintenance Guide provides the procedures required to integrate the Avaya one-X Mobile Server with existing equipment in a corporate IP voice network as well as provision the Avaya one-X Mobile Server itself.
Audience
This guide is written for network and IT administrators who are responsible for administering, configuring, and maintaining the Avaya one-X Mobile Server. Administrator or root permissions are required to accomplish the tasks in this guide. Also required is knowledge of Avaya Communication Manager, Avaya Modular Messaging, Application Enablement Services, Cisco CallManager, and Messaging applications.
What You Need to Know

To successfully integrate the Avaya one-X Mobile Server into your network, you need to know:

the details of your IP network how to configure your call management switch (either Avaya Communication Manager or Cisco CallManager) how to configure Avaya Application Enablement Services (AES) how to configure your messaging platform
December 2008
Conventions
The following conventions appear in this guide: Convention Bold font Italic font Courier Font Menu Font Description Keywords and names of text fields are in boldface font. Values that the administrator must enter into text fields are in italic font. Text which must be entered into a terminal session is in courier font. Menu Items are in Bold Font
Acronyms
The following acronyms may appear in this guide: Acronym AES AXL CCM CM CMC COS CSS EC500 FAC (Avaya) FAC (Cisco) IMAP JTAPI Meaning Application Enablement Services AVVID XML Layer Cisco CallManager Communication Manager Client Matter Code Class of Service Calling Search Space Extension to Cellular Feature Access Code Forced Authorization Code Internet Message Access Protocol Java Telephony Application Programming Interface 1 of 2
10
December 2008
Avaya one-X Mobile Documentation
Acronym LDAP MAPI MSS SAC SAFE SMTP SSL
Meaning Lightweight Directory Access Protocol Messaging Application Programming Interface Message Storage Server Send All Calls EC500 Self Administration Feature Simple Mail Transfer Protocol Secure Sockets Layer 2 of 2
Avaya one-X Mobile Documentation

Avaya documents are available on the Avaya support web site at http://support.avaya.com.The documents listed below are part of the Avaya one-X Mobile documentation set. Title Avaya one-X Mobile Site Survey/Pre-Installation Checklist (for Avaya Communication Manager Environment) Avaya one-X Mobile Site Survey for the Cisco CallManager Environment Avaya one-X Mobile Installation Guide Avaya one-X Mobile Installation and Upgrade Checklists Avaya one-X Mobile Integration, Administration, and Maintenance Guide Avaya one-X Mobile User Guide for J2ME Avaya one-X Mobile User Guide for RIM Blackberry Avaya one-X Mobile User Guide for Palm Treo Avaya one-X Mobile User Guide for iPhone Document Number 18-602133 18-602908 18-602135 18-603138 18-602153 18-602147 18-602148 18-602149 18-602788 1 of 2
December 2008
11
Title Avaya one-X Mobile User Guide for Windows Mobile Avaya one-X Mobile Web User Guide
Document Number 18-602903 18-602150 2 of 2
Other Product Documentation

The documents listed below may help in completing the tasks in this book Title Avaya Communication Manager documentation Avaya Application Enablement Services documentation Avaya MultiVantage Application Enablement Services TR/87 Implementation Guide (in particular "Chapter 2, Dial Plan") 02-601893 Document Number
You should also refer to the manuals for other vendors equipment that may be installed in your network.
12
December 2008
Chapter 2: Overview
This chapter provides a brief description of Avaya one-X Mobile, highlights new features, lists supported Avaya and Cisco equipment, and describes tasks that should be completed before you begin using this guide. Also provided is a list of all integration and configuration tasks that must be completed for a new installation of Avaya one-X Mobile.
Avaya one-X Mobile Overview

Avaya one-X Mobile is software and hardware that offers enterprise voice, messaging, voicemail, and corporate directory integration on mobile devices (cell phones and PDAs). Avaya one-X Mobile allows the corporate voice network to be invisibly and seamlessly extended to employees mobile phones. Features include:
Managing call routing of corporate PBX extensions directly to other locations, such as a mobile phone. Routing calls based on an individual caller using special routing rules (for example, allow a spouse to reach an employees mobile phone, while all other calls redirect to voicemail). Access and receive corporate voice mail. View and manage personal phone book and corporate directory. Administration portal for administering and provisioning users. Web interface for user configuration and changing settings.
Whats New in this Release

Avaya one-X Mobile Release 1.1 introduces the following new features:
Support for the following systems: - Avaya Communication Manager 5.0 - Application Enablement Services 4.2 - Avaya Modular Messaging 4.0 Support for iPhone, Pocket PC, and Smartphone mobile clients. Support for 15 languages on the mobile clients.
December 2008
13
Chapter 2: Overview
Support for virtual extensions which allows Avaya one-X Mobile users who do not have a physical desk phone or Softphone to make and receive calls using the Avaya one-X Mobile application. Support for Vierling Mobile Gateways which allows Avaya one-X Mobile customers to reduce cell phone minute charges when using Avaya one-X Mobile with a Mobile Gateway. Support for Dell PE 1950 server platform. Support for No Voicemail clients which allows an Avaya one-X Mobile server and client configuration that does not require integration with a voicemail platform. In this configuration, all Avaya one-X Mobile features except voicemail are available on the mobile device. Users whose mobile device is configured without voicemail are able to call their corporate voicemail system directly to listen to their corporate voicemail messages. Improved connection status feedback on the mobile clients which provides users with a better understanding of the current status of the I/O path between the Avaya one-X Mobile client and Avaya one-X Mobile server. Green, yellow, and red icons are provided on the top of the Home, Call Log, New Voicemail, and Saved Voicemail screens.
Supported Equipment
The table below lists the supported equipment that may be in your network. It is unlikely that you would have equipment from different vendors performing the same function in your network. Function Call Management Voicemail IP Phones Corporate Directory Avaya Equipment Communication Manager Modular Messaging Supported Avaya IP Phones Cisco Equipment CallManager Unity (via MS Exchange) Cisco IP Phones CallManager Microsoft Active Directory (2000 and 2003) SunOne Netscape_iPlanet MS Exchange Server Other Vendors Equipment
MS Exchange Other Application Enablement Services (AES)
14
December 2008
Before You Begin
Before You Begin

Before you begin performing the integration and administration tasks provided in this guide: 1. The following equipment and software must be installed on your network: - Avaya Application Enablement Services (AES) server

SE Linux must be disabled AES license must be installed
- Avaya Communication Manager (version 3.1 or later) - Avaya Modular Messaging (optional) You should also have all the relevant documentation for this equipment on hand for reference. 2. Review the worksheets in the Avaya one-X Mobile Site Survey/Pre-Installation Checklist, document number 18-602133, and complete as much information as possible: Note: You will complete some information on the worksheets as you perform the tasks in this guide. 3. The installation of the Avaya one-X Mobile Server software must be completed. See the Avaya one-X Mobile Installation Guide, document number 18-602135.
Note:
Required Tasks for New Installations

The following integration and configuration tasks must be performed for new installations of Avaya one-X Mobile. For tasks listed that do not have a corresponding procedure in this guide, refer to the administration and maintenance documents for Avaya Communication Manager, Avaya Application Enablement Services, and Avaya Modular Messaging. Task Procedure
Avaya Communication Manager

For CM 3.1.2 verify that service pack 12866 has been applied and SA8481 is turned on. For CM 3.1.4 and higher verify that SA8481 is turned on. See Validate Licensed Features on page 20.
1 of 4
December 2008
15
Chapter 2: Overview
Task Load license for Avaya one-X Mobile call center functions Administer AES in NodeNames. Set up Configuration Set for each carrier. Verify EC500 is set up for users. Administer CTI link. Administer IP services. Once AES is administered and up and running, use the following SAT commands to determine status and troubleshoot connectivity: stat aes link, stat aes cti, stat aes inter Add COS and COR for VDNs and CTIs Add CTI stations. Add announcement. Add VDN triplets. Add virtual extensions (for Avaya Communication Manager 5.0 and above only). Configure MFEs for virtual extensions (for Avaya Communication Manager 5.0 and above only). Add superuser login (in Web browser). Confirm SSH 5022 and Telnet port 5023 is enabled on both sides.
Procedure
See Create a Configuration Set on page 25. See Configure EC500 on page 23. See Configure CTI Links in Avaya Communication Manager on page 21. See Configure IP Services on page 22.
See Create Announcements on page 35. See Configure VDN Triplets on page 30. See Configure Virtual Extensions on page 35. See Configure Mobile Feature Extensions (MFEs) for Virtual Extension Users on page 37.
Avaya Application Enablement Services

Verify in Linux that name entered by technician is in all caps and IP information is correct. Load license in WebLM Add DMCC and JTAPI logins and passwords (under User Management). See Validate Licensing on page 40. See Create a JTAPI User on page 40. See Create a DMCC User on page 41. 2 of 4
16
December 2008
Required Tasks for New Installations
Task Set local IP for single or dual NIC (in CTI OAM administration, under Administration > Network Configuration > NIC Configuration). Set duplex speed on eth0 to 100/full and make sure far-end matches. Enable ports 4721 and 4722 (but not TR87). Add switch connection. Add CLAN(s) Add TSAPI link (in CTI OAM administration, under Administration > CTI Link Admin > TSAPI Links). Verify SDB is enabled (in CTI OAM administration, under Administration > TSAPI Configuration). Verify button shows enable (in CTI OAM administration, under Administration > Security Database > CTI Users > List All Users). Add area code/prefix in TR87 dial plan to match Avaya one-X Mobile users DID extensions. Verify AES is talking to Avaya Communication Manager (under Administration > Status and Control > Switch Conn Summary). Once AES is administered and up and running, use the following Communication Manager SAT commands to confirm AES is talking to CM: stat aes link, stat aes cti, stat aes inter Configure SMS
Procedure
See Configure the DMCC Port on page 47. See Configure Switch Connections in AES on page 42. See Configure Switch Connections in AES on page 42. See Create TSAPI Links on page 45.
See TSAPI Configuration (for AES 4.0 and 4.1) on page 44. See Enable Unrestricted Access on page 43.
See TR87 Configuration on page 47.
See SMS Configuration on page 49.
Avaya Modular Messaging

Set in VMSC partial = Full (in MAS). Add login for administrator with SA permissions (in MSS). 3 of 4
December 2008
17
Chapter 2: Overview
Task Add trusted server for Avaya one-X Mobile (in MSS). Verify that updates on network machine are set for in/out = yes (in MSS). Verify that LDAP/SMTP/IMAPI ports are enabled (in MSS). Set Restrict Client to NO in Class of Service for Avaya one-X Mobile users (in MSS).
Procedure See Configure Integration with Avaya Modular Messaging on page 51.
Avaya one-X Mobile

Remote desktop from MAS to Avaya one-X Mobile. Create login and password. Verify license is correct. Create Provisioning Profile. Create CTI Profile. Create Voicemail Profile. Create Corporate Directory Profile. Create Class of Service Profile. Configure CTI Ports. Create VDNs. Import users. License users. See Obtain the Avaya one-X Mobile License on page 93. See Create a Provisioning Profile on page 99. See Create a CTI Profile on page 103. See Create a Voicemail Profile on page 107. See Create a Corporate Directory Profile on page 112. See Create a Class of Service on page 115. See Configure CTI Ports on page 120. See Create VDNs on page 122. See Import Users on page 124. See License Selected Users on page 125. 4 of 4
18
December 2008
Chapter 3: Integration with Avaya Equipment

This chapter provides procedures to integrate Avaya Communication Manager, Avaya Application Enablement Services, and Avaya Modular Messaging with the Avaya one-X Mobile Server.
Integration Task Flow

To integrate Avaya one-X Mobile in a network containing Avaya equipment, perform these tasks in the following order: 1. Configure Integration with Avaya Communication Manager on page 20. a. Validate the Licensed Features b. Configure CTI Links on Avaya Communication Manager c. Configure IP Services d. Configure EC500 e. Configure Confirmed Answer feature (CM 5.0 and above only) f. Configure SAT Access g. Configure VDNs h. Configure DTMF Functionality i. Configure Virtual Extensions j. Configure Mobile Feature Extensions for Virtual Extension Users k. Set Communication Server to Create and Send UCIDs 2. Configure Integration with Avaya Application Enablement Services on page 40. a. Validate Licensing b. Create a JTAPI user c. Create a DMCC User d. Network Configuration of AES e. Configure Switch Connections in AES f. Enable Unrestricted Access
December 2008
19
g. Configure TSAPI h. Create TSAPI Links i. Reset AES Server j. Validate TSAPI Links k. TR87 Configuration l. SMS Configuration 3. Configure Integration with Avaya Modular Messaging on page 51. a. Configure Modular Messaging 3.1 with MSS b. Configure Modular Messaging 3.0 with MSS c. Configure Modular Messaging with Exchange
Configure Integration with Avaya Communication Manager

Avaya one-X Mobile uses Avaya Communication Manager to:
Route inbound calls to match the call handling settings selected by the user in Avaya one-X Mobile. Place calls on behalf of the user while they are away from the office. Monitor inbound and outbound call activity by the user so it can be displayed in a call log for access by Avaya one-X Mobile.
You must configure Avaya Communication Manager in order to properly integrate the Avaya one-X Mobile server. The configuration tasks provided in this chapter include tasks to configure CTI links, IP services, EC500, SAT access for the Avaya one-X Mobile server, DTMF functionality, and Virtual Extensions. You use System Administration Terminal (SAT) commands to configure Avaya Communication Manager. There are several different Avaya applications, such as Avaya Site Administration, that you can use in order to enter the SAT commands.
Validate Licensed Features

It is important to validate the licensed features on Avaya Communication Manager before attempting to configure. Validate the following licenses exist:

FEAT_ADJLK FEAT_BSCVEC FEAT_PRTVEC
20
December 2008
FEA_RCNAA_CFF REGISTRATION IP_API_A* FEAT_EC500 FEAT_XCOV_ADMIN VALUE_OPT_EC500
To validate licensed features: 1. Enter the system-parameters special-applications command. 2. Verify the following:
For CM 3.1.2 verify that service pack 12866 has been applied and SA8481 is turned on. For CM 3.1.4 and higher verify that SA8481 is turned on.
Contact your Avaya Business Partner if you do not have the proper features licensed.
Configure CTI Links in Avaya Communication Manager

Before performing this procedure, you must identify an unused extension from the dial plan. To configure a CTI Link in Avaya Communication Manager: 1. Use the add cti-link <n> command, where n is the CTI Link number, to access the CTI Link screen. Note: If you need to identify a free CTI link, use the list cti-link command to identify a free number. 2. On page 1, change Extension to an unused extension in the dial plan. 3. Change Type to ADJ-IP. 4. In the Name field, enter a name for the link. 5. Change the Class of Restriction to one that allows the type of dialing you allow your users from their desks. This can be changed depending on company requirements. 6. On page 2, ensure that all fields are set to n. 7. Press Enter or F3 to save. 8. Use the list cti-link command to validate that the CTI Link you created is in the list.
Note:
December 2008
21
Configure IP Services
IP Services must be configured to link the switch to an AES switch connection. To configure IP services: 1. Enter the command change ip-services.
2. On page 1, in the Service Type field, select AESVCS from the drop-down box. 3. Set Enabled to y. 4. In the Local Node field, enter the name of the local node. 5. Set the Local Port to 8765.
22
December 2008
6. On page 3, in the AES Services Server field, enter a Server ID for the AES server being used.
Note:
Note: The Server ID must match the hostname found in the /etc/hosts file on the AES server. 7. In the Password field, enter a password. Note: The password is required when configuring the AES later. 8. Set Enabled to y. 9. Press Enter or F3 to save.
Note:
Configure EC500
The Extension to Cellular feature is used as part of Avaya one-X Mobile. It is necessary to configure EC500 for all Avaya one-X Mobile users before provisioning them for the product. This guide provides a very cursory introduction to configuring EC500. Complete documentation on EC500 is found in Feature Description and Implementation for Avaya Communication Manager, document number 555-245-205.
December 2008
23
Configure Feature Access Codes

Feature Access Codes (FACs) are used to effect features of the EC500 product during Avaya one-X Mobile call flows. It may be helpful to note them down as they will be required for administration of the Avaya one-X Mobile Server. See the Avaya one-X Mobile Site Survey/ Pre-Installation Checklist, document number 18-602133, and note the FACs on the appropriate worksheet. To set up the required FACs: 1. Enter the command change feature-access-codes.
2. On page 2, enter FACs (if they do not already exist) for the following: a. EC500 Self-Administration Access Code b. Enhanced EC500 Activation c. Enhanced EC500 Deactivation 3. On page 3, enter FACs (if they do not already exist) for the following: a. Send All Calls Activation b. Send All Calls Deactivation 4. Press Enter or F3 to save.
24
December 2008
Create a Configuration Set

A configuration set is required in order for EC500 to detect cellular voicemail correctly. To create a configuration set: 1. Use the change xmobile configuration-set <n> command, where n is a new configuration set if one is not predefined, to access the Configuration Set screen. 2. Give the configuration set a name to identify which mobile carrier it is associated with. 3. Change the Cellular Voicemail Detection as required. This information is typically published by cellular carriers. Typically a number of no less than 2 seconds is adequate. A large number here will make it difficult for users to accept calls in good networks. 4. Press Enter or F3 to save. Note: Make a list of all configuration sets that apply to the Avaya one-X Mobile users. You will need this list when you perform the procedure in Configure the Confirmed Answer Feature (for CM 5.0 and above) on page 27.
Note:
Configure EC500 for Avaya one-X Mobile Users

EC500 must be configured for all Avaya one-X Mobile users. To configure EC500 for each Avaya one-X Mobile user: 1. Enter the command change off-pbx-telephone station-mapping <n>, where n represents the station extension.
December 2008
25
2. In the Station Extension field, enter the station extension of the user. 3. In the Application field, enter EC500. 4. Leave the Dial Prefix field empty. 5. Leave the Phone Number field empty if the mobile number is not known. The Avaya one-X Mobile Server will provision this automatically when the user logs in to setup their account for the first time. 6. Set Trunk Selection as ars. 7. In the Config Set field, enter the configuration set configured in Create a Configuration Set on page 25. 8. Press Enter or F3 to save. Note: Since Avaya one-X Mobile uses EC500 in its call flows, it is recommended that EC500 buttons be removed from stations used by Avaya one-X Mobile to prevent users from manually enabling or disabling this feature.
Note:
Configure the Dial Prefix in the Route Pattern

When you run the command change off-pbx-telephone station-mapping and update the Phone Number field as described in the previous section Configure EC500 for Avaya one-X Mobile Users, the dial prefix field remains empty. In order for managed mobile calls to work properly, you must configure the dial prefix in the Route Pattern so that Avaya Communication Manager prepends the correct digits for Avaya one-X Mobile calls.
26
December 2008
To configure the dial prefix for a Route Pattern: 1. Enter the command change route-pattern <n> command, where n represents the route pattern number or name.
2. In the Inserted Digits field, enter <PSTN_prefix+County Code>. For example, you might enter 91, where 9 is the PSTN prefix and 1 is the country code. 3. Press Enter or F3 to save. 4. Use the change ars analysis <n> command, where n represents the location number or name, to view the ARS Digit Analysis Table. Verify the Route Pattern that you configured is associated with the appropriate Dialed Strings. Note: In the change ars analysis <n> command, if you enter location for <n>, the ARS Digit Analysis Table will list all locations.
Note:
Configure the Confirmed Answer Feature (for CM 5.0 and above)

For Avaya Communication Manager 5.0 and above, configure the Confirmed Answer feature to ensure the voicemail system does not answer a callback and then connect the callback destination party to the voicemail platform. Configuring the Confirmed Answer feature ensures that when a call is placed to an EC500 device using Avaya Communication Manager 5.0 and above, the call is not delivered until a DTMF digit is received by Avaya Communication Manager. This procedure is performed for all configuration sets that apply to the Avaya one-X Mobile users.
December 2008
27
Note:
Note: For systems using the Confirmed Answer feature, callback is not supported on stations without a coverage path. If is not required that the Confirmed Answer feature be used with Avaya one-X Mobile. If the Confirmed Answer feature is turned on, a number key (DTMF) must always be pressed for all incoming calls accepted at the EC500 destination before the call will be accepted. This includes the first leg of any callback call. If the Confirmed Answer feature is turned off, a number key does not have to be pressed for incoming calls accepted at the EC500 destination before the call will be accepted. Rather, incoming calls are accepted at the EC500 destination immediately after the user answers the call.
To configure the Confirmed Answer feature for a configuration set: 1. Enter the command change off-pbx-telephone configuration-set <n> where n represents the configuration set number.
2. Change Confirmed Answer to Yes. 3. Change the Timeout (seconds) to 10. 4. Press Enter or F3 to save. 5. Repeat this procedure for each configuration set that applies to the Avaya one-X Mobile users.
28
December 2008
Configure SAT Access

The Avaya one-X Mobile Server requires SAT access in order to provision CTI resources such as CTI Ports and VDNs. For Avaya Communication Manager, SSH port 5022 and Telnet port 5023 need to be enabled. To configure Avaya one-X Mobile Server SAT access: 1. Log on to the Avaya Communication Manager web page. 2. Go to Maintenance. 3. Go to Security/Server Access. 4. Make sure SAT (SSH 5022) is enabled for both Service State and Corporate LAN Firewall. 5. Make sure SAT (Telnet 5023) is enabled for both Service State and Corporate LAN Firewall.
Configure DTMF Functionality (for CM 3.X and 4.X only)

Avaya one-X Mobile uses Virtual Directory Numbers (VDNs) to collect DTMF digits to confirm answer by a user rather than a cellular voicemail provider. The application manages a pool of VDN triplets. Each triplet consists of two VDNs and one CTI port. Note: For Avaya Communication 5.0 and above, the Confirmed Answer feature is used to confirm answer by a user rather than a cellular voicemail provider. See Configure the Confirmed Answer Feature (for CM 5.0 and above) on page 27 for more information. If you are using the Confirmed Answer feature, do not configure VDNs. 1. Waits for one second 2. Collects a digit after playing an announcement 3. Routes to the Second VDN
Note:
The first VDN has a vector program attached to it that does the following:
December 2008
29
The second VDN is monitored by the application and is used to retrieve the actual digit entered. The second VDN is attached to a vector that waits for 0 seconds and then routes to the CTI port. The CTI port is used to keep the call up. To configure DTMF functionality for Avaya one-X Mobile, perform the steps listed below. Note: If meet me vectors have already been configured in Avaya Communication Manager, you cannot create the VDN triplets using the following process. You must create the VDN triplets manually in Avaya Communication Manager. See Create VDN Triplets Manually on page 32 for more information. 1. Create VDN triplets VDN triplets are created using the Avaya one-X Mobile administrative interface under Avaya Setup > CTI Resources > VDNs. See Create VDNs on page 122 for more information. 2. Configure the VDN triplets After the VDN triplets are created, they must be provisioned on the switch. See Configure VDN Triplets on page 30 for more information. 3. Create directory ranges for the VDNs see Create Directory Ranges for VDNs on page 31 for more information. 4. Create announcements see Create Announcements on page 35 for more information. Note: Using the VDN triplets to collect DTMF tone is not supported for users who utilize Virtual Extensions or for users whose line appearance may appear as a bridged appearance on another users phone. For these users, in the Avaya one-X Mobile administrative interface, you must create a separate Class of Service which does not utilize the DTMF requirement. See Create a Class of Service on page 115 for more information.
Note:
Note:
Determine Triplet Quantity

One triplet is needed to service a callback. They are managed in a pool. The number of VDN triplets is determined by the quantity of callbacks expected during your busy hour. If you run out of VDN triplets, the call is placed, but no DTMF information is collected. The second leg of the call is placed immediately.
Configure VDN Triplets

After the VDNs are created, provision the switch. For each triplet: 1. Create a vector number for the first VDN. 2. Assign that vector number to the first VDN
30
December 2008
3. Enter the command change vector <x> where x represents the vector number.
4. Change the steps of the vector to be: a. Wait-time 1 second b. Collect 1 digit after announcement 1234 (where 1234 is an announcement created by the administrator which says something like please press any key to connect your call) c. Route-to VDN2 5. Create a vector number for the second VDN. 6. Assign that vector number to the first VDN. 7. Use the change vector <y> command, where y represents the vector number, to access the Change Vector <y> screen. 8. Change the steps of the second vector to be: a. Wait-time 0 seconds b. Route-to CTI Port (the one that is part of the triplet).
Create Directory Ranges for VDNs

VDN triplets must be populated in the local Avaya one-X Mobile database. You can use the Avaya one-X Mobile administrative interface to create the VDN triplets if you want to:

use existing VDNs and CTI ports that are in triplet form and already exist on the switch create new VDNs triplets
December 2008
31
See Create VDNs on page 122 for the procedure to create directory ranges for VDNs using the Avaya one-X Mobile administrative interface.
Create VDN Triplets Manually

If Meet Me vectors have already been configured in Avaya Communication Manager, you must manually create the VDN triplets in Avaya Communication Manager. 1. Determine the Directory Number to be used for each of the VDN triplets. Note that for each triplet, you need three Directory Numbers one for each of the two VDNs and one for the CTI Port. For example, for the first VDN triplet, you determine that: a. VDN 1 = 2550 b. VDN 2 = 2551 c. CTI Port = 2552 Note: The CTI Ports used in VDN triplets should be out of range of the ones that are used as CTI resources for Avaya one-X Mobile call handling functionality. To view CTI Port information, in the Avaya one-X Mobile administrative interface select Avaya Setup > CTI Resources > CTI Ports. See Configure CTI Ports on page 120 for more information. 2. Create the first vector as described in step 3 in Configure VDN Triplets on page 30. Note that you will need to know the Directory Number that will be used for the second VDN in the triplet. Using the example VDN triplet described in step 1, the following would appear:
Note:
3. Create the first VDN in Avaya Communication Manager, as follows:
32
December 2008
a. Enter the command add vdn <x> where x represents the Directory Number chosen for VDN 1 in step 1. b. For the vector number, use the vector created in step 2. Using the example VDN triplet described in step 1, the following would appear:
4. Create the second vector as described in step 5 in Configure VDN Triplets on page 30. Note that you will need to know the Directory Number that will be used for the CTI Port that will be part of this triplet. Using the example VDN triplet described in step 1, the following would appear:
5. Create the second VDN in Avaya Communication Manager, as follows: a. Enter the command add vdn <x> where x represents the Directory Number chosen for VDN 2 in step 1.
December 2008
33
b. For the vector number, use the vector created in step 4. Using the example VDN triplet described in step 1, the following would appear:
6. Create the CTI Port in Avaya Communication Manager to complete the VDN triplet. To create the CTI Port, enter the command add station <x> where x represents the Directory Number chosen for the CTI Port in step 1. Using the example VDN triplet described in step 1, the following would appear:
34
December 2008
Create Announcements
Create an announcement that is similar to this one: Please press 5 to connect your call <pause 5 seconds> Please press 5 to connect your call <pause 5 seconds> Please press 5 to connect your call Note: Use a phone with Class of Service permissions to perform this task. Record the announcement three times, as shown above, to provide sufficient time for input.
Note:
For instructions about how to create and record announcements using Avaya Communication Manager, refer to the Avaya Communication Manager Online Help or the Administrators Guide for Avaya Communication Manager Software for more information. Ensure that Avaya Communication Manager is configured so that the:

Announcement Queue field is set to Y System-Parameters Customer Options - Call Center Features - Vectoring (ANI/II-Digits Routing) is set to Y DTMF licenses are installed
Configure Virtual Extensions

With Service Pack 1.1.1, Avaya one-X Mobile supports virtual extensions where a user is not required to have a desk phone or softphone to use Avaya one-X Mobile to make and receive calls on their mobile device. The virtual extension feature is available only if the corporate communication system is Avaya Communication Manager 4.1 and above and utilizes Avaya AES 4.2.1 and above. Perform the tasks described below for each virtual user. In this procedure, you are square-bridging a CTI port with the users managed extension. To configure a virtual user on Avaya Communication Manager 4.1 and above: 1. Make sure the users managed station has been set up to have 3 line appearances. 2. Use the add station <n> command, where n is the new station extension you want to add. This station does not have to be a dialable number from the PSTN. 3. In the Type field, select CTI. 4. Make sure the Port field displays X. This is pre-populated when you select CTI. 5. In the Name field, enter the name.
December 2008
35
6. In the COR field, enter the appropriate Class of Restriction. 7. In the COS field, enter the appropriate Class of Service. 8. On page 4, under Button Assignments area, remove all call-appr assignments and add brdg-appr assignments to the first three buttons of the users managed extension as shown below.
9. Click Enter or F3 to save.
36
December 2008
Configure Mobile Feature Extensions (MFEs) for Virtual Extension Users

To configure MFE, follow these steps: (You do not have to do this for every user.) 1. Enter the command change off-pbx-telephone mobile-feature-extensions.
2. Enter a station number which is not used and is not configured in Avaya Communication Manager. 3. Press Enter or F3 to save. Note: Dialing an MFE port from a managed extension should ring its EC500 destination. If you are unable to ring the EC500 destination, you might have a configuration issue. Contact your system administrator for Avaya Communication Manager for further assistance.
Note:
Set Communication Server to Create and Send UCIDs

Universal Call ID (UCID) is a unique tag assigned to a call. In simple call scenarios, the tag stays with that call within a network that is based on a communication server connected by ISDN lines. In complex call scenarios, the tag often merges with other tags. For more detailed information about UCID, refer to http://support.avaya.com/elmodocs2/callctr/r3_1/ 07_300478.pdf.
December 2008
37
To enable UCID generation: Use the change system-parameters feature command to display the Feature-Related System Parameters form. Verify that your administration settings comply with the following requirements: 1. Go to page 5 of the form. 2. In the Create Universal Call ID (UCID)? field, enter y. 3. In the UCID Network Node ID field, enter the node ID number. Valid numbers are from 1 to 32,767.
!
CAUTION:
CAUTION: The UCID Network Node ID must be unique for every communication server and IVR in the system. If it is not unique, the integrity of the UCID is compromised.
Figure 1: Page 5 of the Feature-Related System Parameters Form
4. Go to page 13 of the form. 5. Send UCID? y
38
December 2008
Figure 2: Page 13 of the Feature-Related System Parameters Form
6. Press Enter or F3 to save.
December 2008
39
Configure Integration with Avaya Application Enablement Services

The Avaya one-X Mobile Server uses Application Enablement Services (AES) to communicate with Avaya Communication Manager via JTAPI. Note: This section provides a cursory set of steps for configuring AES. Refer to the complete AES documentation for installation instructions.
Note:
Validate Licensing
Validate that the proper licensing is available on the AES: 1. Go to the AES URL http://<AESHOST>/WebLM 2. Enter the credentials. 3. Validate that the following licenses exist:

VALUE_CVLAN_VERSION VALUE_AEC_CONNECTIONS VALUE_TSAPI_VERSION VALUE_AEC_VERSION VALUE_NOTES VALUE_TSAPI_USERS
Create a JTAPI User

In the User Administration portion of the AES, it is necessary to create a user that the Avaya one-X Mobile Server can use to communicate with the AES. Perform the following steps: 1. Login to AES User Management. Note: This is a separate login from CTI OAM. 2. Navigate to User Management > Add User. 3. Create a new User ID. 4. Fill in the required fields. 5. Set the CT User field to yes.
Note:
40
December 2008
6. Click Apply. 7. Note the User and Password in the Avaya one-X Mobile Site Survey/Pre-Installation Checklist, document number 18-602133, (sections 2.1 and 2.2) for future reference.
Create a DMCC User

In the User Administration portion of the AES, it is necessary to create a user that the Avaya one-X Mobile Server can use to communicate with DMCC. Note: This procedure should be performed only if you want to use AES to perform the extension conversion. If you want to use the algorithm provided by the Avaya one-X Mobile administrative interface to perform the extension conversion, you do not need to perform this procedure. See step 33 in the procedure Create a Class of Service on page 115 for more information. 1. Login to AES User Management Note: This is a separate login from CTI OAM. 2. Navigate to User Management > Add User. 3. Create a new User ID. 4. Fill in the required fields. 5. Set the CT User field to yes. 6. Click Apply. 7. Note the User and Password in the Avaya one-X Mobile Site Survey/Pre-Installation Checklist, document number 18-602133, (section 2.10) for future reference.
Note:
Perform the following steps:
Note:
Network Configuration of AES

Inside the CTI OAM Administration, perform the following steps: 1. Login to AES CTI OAM. Note: This is a non-root Linux user login.
Note:
December 2008
41
2. Go to the Administration > Network Configuration > Local IP page.
3. Ensure all the interfaces are set to the correct network interfaces. Otherwise, the Avaya one-X Mobile Server will not be able to contact the AES.
Configure Switch Connections in AES

Perform these steps to configure switch connections in AES: 1. Navigate to Administration > Switch Connections. 2. Click Add Connection. 3. Enter the name of the AES host name.
4. Set the Switch Password to what you configured in the switch in Configure IP Services on page 22.
42
December 2008
5. Confirm the password. 6. Click the checkbox for SSL. 7. Click Apply. The newly created connection should show in the list of connections. 8. Click on Edit CLAN IPs. 9. Enter the IP Address of the Avaya Communication Manager you configured and click on Add Name or IP. 10. Save the changes.
Enable Unrestricted Access

This configuration must be done in the CTI OAM. 1. Navigate to Administration > Security Database > CTI Users > List All Users.
2. Select the user you created in Create a JTAPI User on page 40, and then click the Edit button.
December 2008
43
3. Make sure that Unrestricted Access is set to Disable. (The default is Disable.) Note: The Unrestricted Access button shows the action to be taken, not the current state.
Note:
When the Unrestricted Access button shows Enable, unrestricted access is currently disabled. When the Unrestricted Access button shows Disable, unrestricted access is currently enabled.
TSAPI Configuration (for AES 4.0 and 4.1)

This configuration must be done in the CTI OAM. 1. Navigate to Administration > TSAPI Configuration.
2. Click the checkbox for Auto Admin of LAN Addresses. 3. Click the Apply Changes button.
44
December 2008
TSAPI Configuration (for AES 4.2)

This configuration must be done in the CTI OAM. 1. Navigate to Administration > Security Database > SDB Control.
2. Ensure the checkbox for Enable SDB TSAPI Service, JTAPI and Telephony Service is checked. 3. Click the Apply Changes button.
Create TSAPI Links

This configuration must be done in the CTI OAM. 1. Navigate to Administration > CTI Link Admin > TSAPI Links.
2. Click the Add Link button. 3. In the Link drop-down box, select a link number for AES. 4. In the Switch Connection drop-down box, select the name of the switch that you configured in Configure Switch Connections in AES on page 42.
December 2008
45
5. In the Switch CTI Link Number drop-down box, set the CTI Link Number to the CTI link you configured in Configure CTI Links in Avaya Communication Manager on page 21. 6. In the ASAI Link Version drop-down box, select 4. 7. In the Security drop-down box, select Unencrypted. 8. Click the Apply Changes button.
Reset AES Server

You must reset the AES server before you validate the TSAPI links. To reset the AES server: 1. Navigate to Administration > Maintenance > Service Controller. 2. Click on Reset AES Server.
Validate TSAPI Links

Before you validate the TSAPI links, you must reset the AES server. See Reset AES Server on page 46. This configuration must be done in the CTI OAM. 1. Navigate to Administration > Security Database. 2. Click on Tlinks. 3. You should see the following Tlink: AVAYA#<switch connection Name>#CSTA#<Hostname>
Validate the ASAI Link

Perform these steps to validate the ASAI Link: 1. Navigate to Utilities > ASAI Test. 2. Select the TSAPI link you configured in Validate TSAPI Links on page 46. 3. Click Test. 4. If the test is successful, text should display Heartbeat with switch for TSAPI link 01 was successful.
46
December 2008
TSAPI Test
Perform these steps to test the TSAPI Link: 1. Navigate to Utilities > TSAPI Test. 2. Select the Tlink created in Create TSAPI Links on page 45. 3. Enter the JTAPI User created in Create a JTAPI User on page 40. 4. Enter the JTAPI User password. 5. Enter an extension in the from field. 6. Enter an extension in the to field. 7. Click the Dial button. 8. If the test is successful, the phone should dial from one extension to the other.
TR87 Configuration
The TR87 configuration on AES must be performed to administer dial plan information so that that Avaya one-X Mobile Server can access it. This document provides a cursory description of TR87 configuration. For full details, refer to http://support.avaya.com/elmodocs2/AES/4.0/02_601893_1_1.pdf
Configure the DMCC Port

Note:
Note: This procedure should be performed only if you want to use AES to perform the extension conversion. If you want to use the algorithm provided by the Avaya one-X Mobile administrative interface to perform the extension conversion, you do not need to perform this procedure. See step 33 in the procedure Create a Class of Service on page 115 for more information.
December 2008
47
Perform these steps to configure the DMCC port: 1. Navigate to Administration > Network Configuration > Ports.
2. In the DMCC Server Ports section, make sure that Unencrypted Port 4721 is Enabled. and Encrypted Port 4722 is Enabled. Note: Do not enable the TR/87 port.
Note:
48
December 2008
Create Dial Plan Rules for the Switch

Dial plan rules must be configured in AES so that Avaya one-X Mobile can determine if numbers are on-switch or off-switch. Note: This procedure should be performed only if you want to use AES to perform the extension conversion. If you want to use the algorithm provided by the Avaya one-X Mobile administrative interface to perform the extension conversion, you do not need to perform this procedure. See step 33 in the procedure Create a Class of Service on page 115 for more information. 1. Navigate to Administration > Dial Plan > Switch Administration.
Note:
To configure dial plan rules in AES:
2. Select the switch you are administering, then click the Detail button. 3. In the From TelURI section, enter conversion rules for the switch that map from E.164 numbers to extensions that are on-switch. Refer to the full AES documentation for notes on how to administer the dial plan and order the conversion rules.
SMS Configuration
The Avaya one-X Mobile Server needs to access the SMS interface in order to administer the product. Perform the following steps on the AES: 1. Log in to AES as root. 2. Edit syslog.conf using the following command: vi /etc/syslog.conf
December 2008
49
3. Add the following line to the end of the file: local1.* 4. Save and exit. 5. Search for any syslogd processes that may be running: ps -ef | grep syslogd 6. Terminate any syslogd processes found in the previous step: kill-9 7. Edit saw.ini: vi /opt/mvap/web/sms/saw.ini 8. Add the switches -T -V to Proxy options. The resulting line appears: ProxyOptions=-n -T -V 9. Set CMPort to 5023: CMPort=5023 10. Save and exit. 11. Search for any ossi processes that may be running: ps -ef | grep ossi 12. Terminate any ossi processes found in the previous step: kill <ossicm-PID> A reboot is not necessary for this step. /var/log/ossicm.log
Install the occsim Binary Patch

Install this patch only if the Avaya Communication Manager version is lower than 4.x.
AES 3.x
For AES 3.x, verify the telnet option is turned on. 1. Open /opt/mvap/web/sms/saw.ini. 2. Under ACP, check to see if ProxyOption=-T and CMPort= 5023. 3. If the settings are not as described in step 2, edit the file.
50
December 2008
Configure Integration with Avaya Modular Messaging
AES 4.0 and AES 4.0.x

For AES 4.0 and AES 4.0.x, follow these steps: 1. Download the AES 4.1 rpm file from http://www.avaya.com/support. 2. Save to any directory. 3. Run swversion to see what the Offer Type is: a. If the offer type is SWONLY, run su root. b. If the offer type TURNKEY, run su sroot. 4. Run ps -ef | grep ossi. 5. Run kill <pid>. 6. Back up /opt/mvap/web/sms/saw.ini. 7. Run rpm -U --force mvap-sms-4.0.651-1.noarch.rpm. If the commands do not run properly and you need to restore the saw.ini file, follow these steps: 1. Run swversion to see what the Offer Type is: a. If the offer type is SWONLY, run su root. b. If the offer type TURNKEY, run su sroot. 2. Run rpm -e mvap-sms. 3. For SWONLY, run rpm -ivh /var/disk/rpms/mvap-sms-4.<release>.rpm. 4. For TURNKEY, run rpm -ivh /var/disk/software/MVAP/rpms/ mvap-sms-4.<release>.rpm 5. Run ps -ef | grep ossi. 6. Run kill <pid>. 7. Restore the old saw.ini file to /opt/mvap/web/sms/saw.ini.

Avaya Modular Messaging is the voicemail platform used by Avaya Communication Manager and Avaya one-X Mobile to manage users voicemail.
December 2008
51
Configure Modular Messaging 3.1 with MSS

To configure Modular Messaging 3.1 with Message Storage Server (MSS), you must configure the trusted server in the Modular Messaging Administration. Perform the following steps to configure the trusted server: 1. Log onto the MSS webpage. 2. Click Trusted Server.
3. Click the Add a New Trusted Server button.
52
December 2008
4. In the Trusted Server Name field, enter a user name. 5. In the Password and Confirm Password fields, enter a password for the user. Note: This user name and password is needed in the Avaya one-X Mobile Server configuration. Add them to the Avaya one-X Mobile Site Survey/Pre-Installation Checklist, document number 18-602133, (section 2.2) for future reference. 6. In the Machine Name/IP Address field, enter the IP address of the Avaya one-X Mobile server. 7. In the Service Name field, enter edge. 8. Set the LDAP Access Allowed field to yes. 9. Set the IMAP4 Super User Access Allowed field to yes. 10. Set the LDAP Connection Security field to No encryption required. 11. Click Save.
Note:
Configure Modular Messaging 3.0 with MSS

To configure Modular Messaging 3.0 with Message Storage Server (MSS), you must configure the trusted server in the Modular Messaging Administration. Perform the following steps to configure the trusted server: 1. Log onto the MSS web page. 2. Click Global Administrator (for MM 3.0 only). 3. Click TrustedServer Management. 4. Click the Add a New Trusted Server button. 5. In the Trusted Server Name field, enter a user name. 6. In the Password and Confirm Password fields, enter a password for the user. Note: This name and password is needed in the Avaya one-X Mobile Server configuration. Add them to the appropriate worksheet in the Avaya one-X Mobile Site Survey/Pre-Installation Checklist, document number 18-602133, (section 2.2) for future reference. 7. In the Machine Name/IP Address field, enter the IP address of the Avaya one-X Mobile server. 8. Set the LDAP Access Allowed field to yes. 9. Set the IMAP4 Super User Access Allowed field to yes. 10. Set the LDAP Connection Security field to No encryption required.
Note:
December 2008
53
11. Click Save. Note: For Modular Messaging 3.0, the superuser mode needs to be manually turned on in the MSS. Contact Avaya Support to have this feature enabled.
Note:
Configure Modular Messaging with Exchange

This section explains the credential set that is necessary to integrate Avaya one-X Mobile with Modular Messaging Exchange message store. Access to Exchange is required by the Avaya one-X Mobile Server to provide Visual Voicemail functionality. Perform the steps in this section on a Domain Controller.
Configure the Exchange Administrative User

When you create a Voicemail Profile in the Avaya one-X Mobile administrative interface, you must complete the Exchange Administrative User section. The Exchange Administrative User section enables the configuration of the location and authentication credentials of the Exchange Server. Access to Exchange is required by the Avaya one-X Mobile Server to provide Visual Voicemail functionality. Authentication credentials of the Exchange Administrative User must be entered so that the Avaya one-X Mobile Server can access voicemail for any user. See "Create a Domain User" below to create a user with the permissions required to be the Exchange Administrative User. Ideally, this user should be a member of the Domain Administrators group. Additionally, the user must have permissions to Log on as a Service locally on the Avaya one-X Mobile Server.
Create a Domain User

Access to Exchange is required by the Avaya one-X Mobile Server to provide the Avaya one-X Mobile Visual Voicemail functionality. The Domain User is used by Avaya one-X Mobile Application Suite to access voice messages from user mail boxes for this purpose. To create a domain user: 1. In the Active Directory Users and Computer, create a domain user account in the domain where the Microsoft Exchange server resides. Note: If multiple Exchange Servers are being used, perform the following tasks on each Exchange Server used by the Avaya one-X Mobile Application Suite. 2. In the Exchange System Manager, assign the permissions to Domain User: a. Navigate down to the Mailbox Store of the Exchange Server. b. Right click on it and select Properties. c. Select the Security tab.
Note:
54
December 2008
d. Click the Add button and add the Domain User. e. Assign the following permissions to it:

Read Execute Delete Read permission Change permission List contents Read properties Write properties List object Open mail send queue Receive As Send As
Once these permissions have been applied to the Domain User, stop and restart the Microsoft Exchange System Attendant Service, Microsoft Exchange MTA Stacks service, and Microsoft Exchange Information Store service. Optionally, wait for the update period to pass (usually around 24 hours). The permissions assigned to the domain user read into the Microsoft Exchange Applications.
Validate Exchange Administrative User Permissions

Validate that the designated Exchange Administrative User has sufficient permissions to manage the end user mailbox. Perform this procedure to validate the Exchange Administrative User permissions for both the Avaya MMS and Cisco Unity voicemail installations. Perform the following steps: 1. Go to the Domain Controller for the specified domain that the Administrative user is a member of. 2. Go to Start > Programs > Administrative Tools > Active Directory Users and Computers to bring up the Management Console. 3. Click View > Advanced Features. 4. Expand the tree control for the specified domain of the Administrative user. 5. Click on Users. 6. Locate the user in the right-hand pane. 7. Right click on the designated user and click on Properties. 8. Locate the group in which the user is a member.
December 2008
55
9. In the Permissions frame, check all the listed permissions as allow except Full Control. Full Control should have neither allow nor deny checked. 10. Click Apply if changes were required. 11. Click OK to exit the property page. 12. Exit out of the Management Console.
56
December 2008
Chapter 4: Integration with Cisco Equipment

This chapter provides procedures to integrate Cisco CallManager with the Avaya one-X Mobile Server. Cisco CallManager must be configured to route calls to the Avaya one-X Mobile Server where the Avaya one-X Mobile Server can make routing decisions based on the users settings. Note: This chapter covers Cisco CallManager versions 4.1 through 5.0.
Note:
Integration Task Flow

To integrate Avaya one-X Mobile in a network containing Cisco equipment, perform these tasks:
Prepare Partitions and Calling Search Spaces for the Avaya one-X Mobile Server on page 62. Create the JTAPI user on page 68. Create CTI Route Points for Intercepting Calls on page 69. Create a Pool of CTI Route Ports for Outbound calls on page 81. Modify AXL Throttle Settings on page 82. Configure Phones for the Integration on page 82. Configure Cisco CallManager to Correctly Pass Caller ID on page 84.
About CTI Devices used by Avaya one-X Mobile Server to Intercept Calls
In order for the Avaya one-X Mobile Server to intercept and route calls, Cisco CallManager CTI objects must be used.
December 2008
57
CTI Route Points

CTI Route Points are virtual devices inside the Cisco CallManager. Route Points may be used to redirect calls before they ring to the IP phone. CTI applications may register CTI Route Points in order to intercept calls before routing them to the IP phone. The Avaya one-X Mobile Server uses CTI Route Points to intercept calls destined for a set of extensions specified by the directory number of the Route Point. The Avaya one-X Mobile Server application examines the preferences of the user before routing the call.
CTI Ports
CTI Ports are used by the Avaya one-X Mobile Server to make outbound calls to destinations specified by users. This includes mobile phones or other PSTN phones. A CTI port is a virtual phone. It can be configured just like a physical IP phone device.
About Partitions and Calling Search Spaces

The Avaya one-X Mobile Server uses Partitions and Calling Search Spaces to intercept incoming calls to Cisco CallManager. When a call comes in to Cisco CallManager, Cisco CallManager has to make a decision on how that call should be routed. Calling Search Spaces and Partitions help determine to what device a call is routed to and whether or not a device has permission to dial another device. For additional background on Calling Search Spaces and Partitions, see the Cisco CallManager document Partitions and Calling Search Spaces.
Partition
The frequently used analogy of a partition is that of a phone book. A Cisco CallManager directory number (DN) has a partition attribute. The partition is simply a name given to a set of numbers. Using the analogy, a partition named TraverseFremont would contain all the directory numbers which are in the Traverse Fremont location.
58
December 2008
Calling Search Space

A Calling Search Space (CSS) is an attribute held by both a Cisco CallManager device and the directory number(s) associated with that device. The Calling Search Space attribute determines what partitions a device or directory number is allowed to dial. Using the phone book analogy, the Calling Search Space is similar to a list of phone books. The device or directory number may dial anyone in the list of phone books. When a call is made, Cisco CallManager looks for potential matches for the digits dialed within the Calling Search Space of that device. One important concept to note for the Avaya one-X Mobile Server is that CallManager looks for exact matches first.
Example 1: Calling Search Space

In the following example, extension 3545 is making a call to extension 3544. Extension 3545 has the Calling Search Space CSS_Fremont and the directory number 3545 is in partition TraverseFremont. When 3545 dials 3544, CallManager looks for an exact match first in the Calling Search Space. In this case, it finds a match for 3544 in the TraverseSanRamon partition and routes the call to 3544.
Partition: TraverseFr em ont Par tition: Traver seSanRamon
3545
TraverseFr em ont VM Pilot TraverseSanRam on CSS_Fremont
3544
December 2008
59
Example 2: Exact Match Takes Precedence

In the following example 3545 is dialing 3544 again. This time, there is a device with a directory number 3XXX in partition TraverseSanJose. When evaluating the potential matches, Cisco CallManager first looks for an exact match. It finds an exact match in the TraverseSanRamon partition and routes the call to that device. During evaluation, it found a potential match in partition TraverseSanJose for the wildcard directory number 3XXX, it kept evaluating to make sure there was no exact match in the remaining partitions. Once an exact match is found, the call is routed to that device and evaluation is stopped.
Partition: TraverseFr em ont Par tition: Traver seSanRamon
3545
Tr averseFremont 3545 VMPilot Traver seSanJose 3XXX Traver seSanRamon 3544 CSS_Fremont
3544
60
December 2008
Example 3: Pattern Match

In this example, 3545 dials 3544. The partition TraverseSanRamon is not in the CSS_Fremont Calling Search Space and CallManager finds no exact match. It finds a wildcard match 3XXX in the TraverseSanJose partition and routes the call to that CTI Route Point device with directory number 3XXX. Upon receiving the call, the route point redirects the call to 3544. Cisco CallManager searches the CSS of the route point (CSS_SanRamon) and finds an exact match in the first partition, TraverseSanRamon and routes the call to 3544.
Par tition: Traver seSanRamon Partition: TraverseFr em ont
3544 3545
Tr averseFremont 3545 VMPilot Traver seSanJose 3XXX CSS_Fremont CTI Route Point TraverseSanRamon 3544 VMPilot Partition: Tr averseSanJose
3XXX
CSS_SanRamon
December 2008
61
Example 4: Two Managed Phones in Same Partition

In this example, 3545 dials 3544. The partition TraverseSanRamon is not in the CSS_Fremont Calling Search Space and CallManager finds no exact match. It finds a wildcard match 3XXX in the TraverseSanJose partition and routes the call to that CTI Route Point device with directory number 3XXX. Upon receiving the call, the route point redirects the call to 3544. CallManager searches the CSS of the route point (CSS_SanRamon) and finds an exact match in the first partition, TraverseSanRamon and routes the call to 3544.
Partition: TraverseSanRam on Partition: Tr averseSanRamon
3544 3545
VM Pilot TraverseSanJose 3XXX CSS_Fr em ont Partition: TraverseSanJose CTI Route Point
Tr averseSanRamon 3544, 3545 VMPilot
3XXX
CSS_SanRamon
Prepare Partitions and Calling Search Spaces for the Avaya one-X Mobile Server
Add a Partition for Avaya one-X Mobile Server Managed Phones
Calls for Avaya one-X Mobile users are intercepted by the Interceptor CTI Route Points and then redirected to the IP phone based on user preferences. In order for the Interceptor CTI Route Point to redirect the call to the IP phone, the phone needs to be in a partition which is dialable from the Interceptor Route Point. Moreover, the phones which are managed by the Avaya one-X Mobile Server should be in a separate partition.
62
December 2008
To create a partition for phones managed by the Avaya one-X Mobile Server, perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Click on the Route Plan menu. 2. Click on the Class of Control submenu. 3. Click on the Partition submenu. 4. Click the Add a New Partition hyperlink. 5. Enter the name of the Managed Phones partition you want to create, followed by the description. Example: TraverseManaged, Avaya one-X Mobile Server Managed Phones 6. Click the Insert button. 7. A popup dialog box should confirm the success of adding the partition. Click OK. This will navigate back to the Find and List Partitions page. 8. Confirm in the Find and List Partitions that the newly added partition exists in the list. Cisco CallManager 5.0X 1. Click on the Call Routing menu. 2. Click on the Class of Control submenu. 3. Select the Partition item. 4. Click the Add New button. 5. Enter the name of the Managed Phones partition you want to create, followed by the description. Example: TraverseManaged, Avaya one-X Mobile Server Managed Phones 6. Click the Save button. 7. Confirm in the Find and List Partitions that the newly added partition exists in the list.
Create a Partition for Interceptor CTI Route Points

In order to intercept calls, the Interceptor CTI Route Points must be in a separate partition. To create a partition for the Interceptor CTI Route Points perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Click on the Route Plan menu. 2. Click on the Class of Control submenu. Cisco CallManager 5.0X 1. Click on the Call Routing menu. 2. Click on the Class of Control submenu. 1 of 2
December 2008
63
Cisco CallManager 4.1X through 4.2X 3. Click on the Partition submenu. 4. Click the Add a New Partition hyperlink. 5. Enter the name of the Managed Phones partition you want to create, followed by the description. Example: TraverseManaged, Avaya one-X Mobile Server Managed Phones 6. Click the Insert button. 7. A popup dialog box should confirm the success of adding the partition. Click OK. This will navigate back to the Find and List Partitions page. 8. Confirm in the Find and List Partitions that the newly added partition exists in the list.
Cisco CallManager 5.0X 3. Select the Partition item. 4. Click the Add New button. 5. Enter the name of the Managed Phones partition you want to create, followed by the description. Example: TraverseManaged, Avaya one-X Mobile Server Managed Phones 6. Click the Save button. 7. Confirm in the Find and List Partitions that the newly added partition exists in the list.
2 of 2
Create a Calling Search Space for Interceptor CTI Route Points

Interceptor CTI Route Points will need their own Calling Search Space. Perform the following steps in the Cisco CallManager Administration User Interface to create a Calling Search Space: Cisco CallManager 4.1X through 4.2X 1. Click on the Route Plan menu. 2. Click on the Class of Control submenu. 3. Click on the Calling Search Space submenu. 4. Click the Add a New Calling Search Space hyperlink. Cisco CallManager 5.0X 1. Click on the Call Routing menu 2. Click on the Class of Control submenu. 3. Select the Calling Search Space item. 4. Click the Add New button. 5. Enter a Calling Search Space Name: Example: CSS_RoutePoint 1 of 2
5. Enter a Calling Search Space Name: Example: CSS_RoutePoint
64
December 2008
Cisco CallManager 4.1X through 4.2X 6. If desired, enter a description: Example: Calling Search Space for Interceptor Route Points. 7. From the Available Partitions list box, include the managed phones partition created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. This will allow the Interceptor Route Point to route calls directly to the managed phones. From the Available Partitions list box, include the managed phones partition created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. This will allow the Interceptor Route Point to route calls directly to the managed phones.
Cisco CallManager 5.0X 6. If desired, enter a description: Example: Calling Search Space for Interceptor Route Points. 7. From the Available Partitions list box, include the managed phones partition created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. This will allow the Interceptor Route Point to route calls directly to the managed phones.
8.
8. From the Available Partitions list box, include the managed phones partition created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. This will allow the Interceptor Route Point to route calls directly to the managed phones.
9. Include any partitions required to reach Voicemail pilot numbers. 10. Do not include the Route Point Partition in this Calling Search Space. Doing so may cause a routing loop. 11. Click on the Insert button. 12. Click on the Back to Find/List Calling Search Spaces hyperlink to validate the new Calling Search Space was added to the list.
9. Include any partitions required to reach Voicemail pilot numbers. 10. Do not include the Route Point Partition in this Calling Search Space. Doing so may cause a routing loop. 11. Click on the Save button. 12. Click on the Back to Find/List Calling Search Spaces hyperlink to validate the new Calling Search Space was added to the list. 2 of 2
December 2008
65
Include the Route Point Partition in other Calling Search Spaces

After creating the Route Point Partition, you need to place it at the top of all other Calling Search Spaces except the Calling Search Space you created for the Interceptor Route Points in the Create a Partition for Interceptor CTI Route Points on page 63. This will make sure that all calls destined for managed numbers go through the Avaya one-X Mobile Server and have proper call handling settings applied. If you include the Route Point Partition in the Calling Search Space of the Interceptor Route Point, it may cause a routing loop.
Calling Search Space Example with Route Point Partition

The following example shows how the Interceptor Route Point works with Calling Search Spaces.
Partition: TraverseFremont CSS: CSS_Fremont Partition: TraverseManaged CSS: CSS_Fremont
Calling Search Spaces

CSS_RoutePoint TraverseManaged 3544 VMPilot
3545
3544
CSS_Fremont TraverseRoutePoint 3XXX TraverseFremont 3545 CTI Interceptor Rout e Point VMPilot
Part ition: TraverseRout ePoint CSS: CSS_RoutePoint
3XXX
1. Extension 3545 in Calling Search Space CSS_Fremont dials extension 3544 in partition TraverseManaged. 2. CSS_Fremont does not contain an exact match for 3544. However, it does contain a pattern match in the TraverseRoutePoint Partition which contains 3XXX. 3. Cisco CallManager routes the call to the Route Point (controlled by the Avaya one-X Mobile Server) first. 4. The Avaya one-X Mobile Server examines the signaling and current call handling settings for the user at extension 3544 and decides to route the call to the desk. 5. The Interceptor Route Point 3XXX has a Calling Search Space CSS_RoutePoint which includes the TraverseManaged Partition. The TraverseManaged Partition contains 3544 and the call is routed to the desk.
66
December 2008
Modify Other Calling Search Spaces to Include the Route Point Partition
For each Calling Search Space except the Calling Search Space created for the Interceptor Route Points, perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Click on the Route Plan menu. 2. Click on the Class of Control submenu. 3. Click on the Calling Search Space submenu. 4. Search for the Calling Search Space you want to modify using the Find button. 5. From the Available Partitions list box, select the Route Point Partition created in the section Create a Partition for Interceptor CTI Route Points on page 63. 6. Hit the down arrow to include it in the Selected Partitions list box. 7. Use the Up and Down arrows to the right of the Selected Partitions list box to move the Route Point Partition to the top of the Calling Search Space. Cisco CallManager 5.0X 1. Click on the Call Routing menu 2. Click on the Class of Control submenu. 3. Select the Calling Search Space item. 4. Search for the Calling Search Space you want to modify using the Find button. 5. From the Available Partitions list box, select the Route Point Partition created in the section Create a Partition for Interceptor CTI Route Points on page 63. 6. Hit the down arrow to include it in the Selected Partitions list box. 7. Use the Up and Down arrows to the right of the Selected Partitions list box to move the Route Point Partition to the top of the Calling Search Space. 8. Press the Save button.
8. Press the Update button. 9. Click on the Back to Find/List Calling Search Spaces hyperlink to modify additional Calling Search Spaces.
December 2008
67
Modify the MWI and Voicemail Ports Calling Search Space

Make sure that the Calling Search Spaces used for MWI and Voicemail ports include the Managed Partition(s) that you created in the section Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. Also ensure that the Route Point Partition is not included in these Calling Search Spaces. MWI will not work properly if the Route Point Partition is included in these Calling Search Spaces.
Create the JTAPI user

In order to route calls the JTAPI application on the Avaya one-X Mobile Server requires all CTI objects used by the application to be associated with a given JTAPI user. Perform the following steps in the Cisco CallManager Administration User Interface to create a JTAPI user for use by the Avaya one-X Mobile Server: Cisco CallManager 4.1X through 4.2X 1. Click on the User menu. 2. Click on the Add New User submenu. 3. Enter a first name. Example: traverse. 4. Enter a last name. Example: jtapi. 5. Enter a user ID. Example: tvjtapi 6. Enter a password. 7. Confirm the password. Cisco CallManager 5.0X 1. Click on the User Management menu. 2. Click on the Application User submenu. 3. Click on the Add New button. 4. Enter a user ID. Example: tvjtapi 5. Enter a password. 6. Confirm the password. 7. In the Groups box, make sure the permissions Standard CTI Allow Calling Number Modification and Standard CTI Enabled are present. 8. In the Roles list box, make sure the permissions Standard CTI Allow Calling Number Modification and Standard CTI Enabled are present. 9. Click the Save button. 1 of 2
8. Enter a PIN.
9. Confirm the PIN.
68
December 2008
Create CTI Route Points for Intercepting Calls
Cisco CallManager 4.1X through 4.2X 10. Check the Enable CTI Application Use checkbox. 11. Check the Call Park Retrieval Allowed checkbox. 12. Check the Enable Calling Party Number Modification checkbox. 13. Click the Insert button. 14. A status in red should read Status: Insert Completed.
Cisco CallManager 5.0X
2 of 2 You will be asked for the JTAPI username and password in the Avaya one-X Mobile Server Administration web site.

Interceptor CTI Route Points are created in the Cisco CallManager Administration Website. If desired, multiple Interceptor Route Points can be created and registered with the Avaya one-X Mobile Server.
Understanding Patterns in Directory Numbers

Before Creating Route Points, it is important to understand how Route Points use pattern matching in Directory Numbers. The Avaya one-X Mobile Server will intercept all calls that match the given pattern in the Directory Number field. For example, to make the Avaya one-X Mobile Server intercept all calls to the range of Directory Numbers 3000 to 3999, the Directory Number on the Route Point should be set to 3XXX. The following characters are valid entries in the Directory Number field: [ ^ 0 1 2 3 4 5 6 7 8 9 - ] + ? ! X * # +.
December 2008
69
Examples: Directory Number Pattern 3XXX 35XX 352[0-3] Matches Directory Numbers 3000 to 3999 3500 to 3599 3520, 3521, 3522, 3523
See "Wildcards and Special Characters in Route Patterns in Hunt Pilots" in the Cisco CallManager System Guide for a thorough explanation of each type.
Create an Interceptor Route Point

The Avaya one-X Mobile Server can utilize multiple Interceptor Route Points. It is not necessary to limit Interceptor Route Points to one. To create an Interceptor Route Point, perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Click on the Device menu. 2. Click on the CTI Route Point submenu. 3. Click on the Add a New CTI Route Point hyperlink. 4. Enter a Device Name. Example: MS_IntRP 5. If desired, enter a description: Example: Avaya one-X Mobile Server Interceptor Route Point Cisco CallManager 5.0X 1. Click on the Device menu. 2. Click on the CTI Route Point submenu. 3. Click on the Add New button. 4. Enter a Device Name. Example: MS_IntRP 5. If desired, enter a description: Example: Avaya one-X Mobile Server Interceptor Route Point 6. Select the appropriate Device Pool from the drop-down menu. 7. Select the Calling Search Space created in Create a Calling Search Space for Interceptor CTI Route Points on page 64. 8. Select the Location. 1 of 3
6. Select the appropriate Device Pool from the drop-down menu. 7. Select the Calling Search Space created in Create a Calling Search Space for Interceptor CTI Route Points on page 64. 8. Click the Insert button.
70
December 2008
Cisco CallManager 4.1X through 4.2X 9. When prompted to Add a Directory Number to the CTI Route Point, press the OK button. 10. In the Directory Number text box, enter the directory number for the route point. When entering the directory number for an Interceptor Route Point, patterns and wild cards may be used. For example, to make the Avaya one-X Mobile Server intercept all calls in the range 3000 to 3999, enter the directory number as 3XXX. 11. In the Partition drop-down menu, select the partition created in Create a Partition for Interceptor CTI Route Points on page 63.
Cisco CallManager 5.0X 9. Click the Save button.
10. Click on the Add a new DN hyperlink on the bottom of the page.
11. In the Directory Number text box, enter the directory number for the route point. When entering the directory number for an Interceptor Route Point, patterns and wild cards may be used. For example, to make the Avaya one-X Mobile Server intercept all calls in the range 3000 to 3999, enter the directory number as 3XXX. 12. In the Route Partition drop-down menu, select the partition created in Create a Partition for Interceptor CTI Route Points on page 63. 13. Leave the Voice Mail Profile set to <None>.
12. Leave the Voice Mail Profile set to <None>.
13. In the Calling Search Space drop-down, select the Calling Search space created in Create a Calling Search Space for Interceptor CTI Route Points on page 64.
2 of 3
December 2008
71
Cisco CallManager 4.1X through 4.2X 14. In the Forward No Answer Internal, Forward No Answer External, Forward Unregistered Internal (CCM 4.2 only), and Forward Unregistered External (CCM 4.2 only) fields, enter the Directory Number entered in step 10. Set the Calling Search Space drop-down to the same value entered in step 13. Important: this will ensure that calls are routed to the IP phone if the Avaya one-X Mobile Server is unavailable. 15. Click the Add button to add the directory number.
Cisco CallManager 5.0X 14. In the Calling Search Space drop-down, select the Calling Search space created in Create a Calling Search Space for Interceptor CTI Route Points on page 64.
15. In the Forward No Answer Internal and Forward No Answer External fields, enter the directory number entered in step 11. Set the Calling Search Space drop-down to the same value in step 14. Important: this will ensure that calls are routed to the IP phone if the Avaya one-X Mobile Server is unavailable. 16. Click the Save button to add the directory number. 3 of 3
Associate the JTAPI User with the Interceptor Route Points

After creating the Interceptor Route Points, you need to associate the Interceptor Route Points with the JTAPI user you created in Create the JTAPI user on page 68. To associate the Interceptor Route Points with the JTAPI user, perform the following steps in the Cisco CallManager Administration User Interface for each Interceptor Route Point you created: Cisco CallManager 4.1X through 4.2X 1. Click on the User menu in Cisco CallManager. 2. Click on the Global Directory menu. Cisco CallManager 5.0X 1. Click on the User Management menu. 2. Click on the Application User submenu. 1 of 2
72
December 2008
Transfer Route Points
Cisco CallManager 4.1X through 4.2X 3. In the User Search text box, enter the name of the JTAPI user you created in Create the JTAPI user on page 68. 4. Press the Search Button. 5. Click the hyperlink of the JTAPI user you created. 6. In the Application Profiles section on the left-hand side, click on the Device Association hyperlink. 7. On the Device Association page, search for the device name of the Interceptor CTI Route Point you created in Create an Interceptor Route Point on page 70. 8. Check the checkbox of the CTI Interceptor Route Point. 9. Press the Update Selected button to associate the device. 10. Repeat the process for other Interceptor Route Points you created.
Cisco CallManager 5.0X 3. In the User Search text box, enter the name of the JTAPI user you created in Create the JTAPI user on page 68. 4. Press the Find Button. 5. Click the hyperlink of the JTAPI user you created. 6. In the Device Information > Available Devices section of the page, select the Interceptor CTI Route Point you created in Create an Interceptor Route Point on page 70. 7. Select the CTI Route Point in the Available Devices section and press the down arrow to move it into the Controlled Devices list box.
8. Repeat the process for other Interceptor Route Points you created. 9. Press the Save button to update the user.
2 of 2

The Avaya one-X Mobile Server uses CTI Route Points to preserve caller ID on outbound calls to mobile phones and other PSTN phones. This is called a Transfer Route Point. When a call is made to a mobile phone, it actually routes through a Transfer Route Point. The Transfer Route Point preserves the caller ID so that the mobile phone can see the caller ID of the calling party.
December 2008
73
How the Avaya one-X Mobile Server uses Transfer Route Points
The following diagram illustrates how the Avaya one-X Mobile Server uses a Transfer Route Point.
Partition: TraverseManaged CSS: CSS_Fremont
Calling Search Spaces 3544

CSS_MS TraverseManaged 3544 VMPilot PSTN Phone: 408-555-1212 510-555-3544 CTI Interceptor Route Point PSTN Gateway CSS: CSS_Fremont CSS_Fremont
TraverseRoutePoint TraverseFremont 7777, 9.@ Route Pattern (PSTN access) VMPilot
Partition: TraverseRoutePoint CSS: CSS_MS
3XXX
DNIS: 650-555-1212 CID: 408-555-1212 CTI Transfer Route Point
8102 DNIS: 650-555-1212 CID: 8104 CTI Route Port Pool 8100 8101
User 3544's mobile phone: 408-555-1212
8104
Partition: TraverseFremont CSS: CSS_Fremont
7777
8103 Partition: TraverseFremont CSS: CSS_Fremont
1. A PSTN phone 408-555-1212 makes a call to a Cisco CallManager and Avaya one-X Mobile Server user at 510-555-3544. 2. The call goes through the PSTN gateway and routes to the CTI Interceptor Route Point as the gateway has Calling Search Space for inbound calls set to CSS_Fremont and the Interceptor Route Point is in the TraverseRoutePoint partition that is at the top of the CSS_Fremont Calling Search Space. 3. The Interceptor Route Point then routes the call to the desk at 3544. This works because the Route Point is in CSS_MS which has the TraverseManaged partition at the top of its CSS. 3544 is in TraverseManaged, so the Avaya one-X Mobile Server routes the incoming call to the desk.
74
December 2008
4. Simultaneously, the Avaya one-X Mobile Server needs to ring the user at 3544s mobile phone. The Avaya one-X Mobile Server initiates an outbound call from a CTI port from the CTI Port Pool to the Transfer Route Point at 7777. Note that the Calling Search Space of the CTI Ports is CSS_Fremont which includes the TraverseFremont partition at the top. The Transfer Route Point is in the TraverseFremont partition, so the call routes to the Transfer Route Point at 7777. The Transfer Route Point changes the calling party number to the calling party that originally called 510-555-3544; 408-555-1212 and simply lets the call pass through, only changing the signaling. 5. The Transfer Route Point has Calling Search Space CSS_Fremont and therefore has TraverseFremont (which has the 9.@ Route Pattern and PSTN access) and is able to complete the call to the mobile phone. 6. The mobile phone caller sees the call as originating from 408-555-1212.
Choose Directory Numbers for the Transfer Route Point

It is important to select an appropriate Directory Number for a Transfer Route Point to make sure calls route in a timely fashion.
Allowed Characters Transfer Route Point Directory Numbers

Use no special characters in the Directory Number for the Transfer Route Point. The Transfer Route Point must have specific Directory Number consisting of digits 0-9 only.
Interdigit Timeout Issues with Pattern Matching

The Directory Number entered must not conflict or match with any other route patterns, translation patterns, etc. This will cause a significant delay in calls made to the PSTN.
Example: Matching Route Pattern

For example, if there is a route pattern called 9.@, do not create a Transfer Route Point Directory Number of 9345. The route pattern will cause a match in calls made to the PSTN. This will cause the Cisco CallManager to wait for the interdigit timeout before routing the call and will result in significant delay.
Example: Matching Directory Number

If a device with the Directory Number 5432 exists in the Cisco CallManager, a Transfer Route Point with the Directory Number 543 will invoke the interdigit timeout before routing the call. Choose a Directory Number with more digits than any longer matching Directory Number.
December 2008
75
Route Plan Report

Before selecting the Directory Number, check the Route Plan Report in Cisco CallManager Administration to determine if undesirable potential matches exist for the Transfer Route Point Directory Number chosen. The Route Plan Report is accessible under the Route Plan menu and the Route Plan Report menu item.
Use Multiple Transfer Route Points to Preserve Users Calling Search Spaces
In general, one Transfer Route Point is necessary for each Calling Search Space that managed users use. For example, if users with CSS_Fremont and CSS_SanRamon are managed by the Avaya one-X Mobile Server, a Transfer Route Point should be created for each CSS. This will preserve the Calling Search Space of the user. For example, if the user is in CSS_Fremont, you would need to create a Transfer Route Point with the Calling Search Space CSS_Fremont to be used to route calls outbound to the PSTN for users with that Calling Search Space.
76
December 2008
The Avaya one-X Mobile Server automatically determines the Calling Search Space for each user and selects a Transfer Route Point with the appropriate Calling Search Space in order to preserve the users dialing rules. The following diagram illustrates how the Avaya one-X Mobile Server uses multiple Transfer Route Points to preserve the Calling Search Space of the user.
Calling Search Spaces
CSS_M S Part ition: TraverseManaged CSS: C SS_SanRamon Partition: TraverseManaged CSS: CSS_Fremont C SS_Fremont TraverseManaged 3544,3575 VMPilot
TraverseRoutePoint TraverseFremont 7777, 7778, 9.@ Route Pattern (PSTN access)
3575
3544
VMPilot
PSTN Phone: 408-555-1212 510-555-3544 510-555-3575 CTI Interceptor Route Point
CSS_SanRamon
TraverseRout ePoint TraverseSanRamon 9.@ Route Pat tern( PSTN access) TraverseFremont 7777, 7778, 9.@ Route Pat tern (PSTN access) VMPilot
C SS: CSS_Fremont
Partition: TraverseR outePoint C SS: C SS_MS
3XXX
DNIS: 510-555- 1212 CID: 408- 555-1212 User 3544's mobile phone : 510-555-1212
8102 DN IS: 7777 C ID: 8104 CTI R oute Port Pool 8100 8101
V
9.@ in Partition TraverseFremont
C TI Transfer Route Point Part ition: TraverseFremont C SS: CSS_Fremont CTI Transf er Route Point
8104
7777
8103 Partition: TraverseFremont CSS: CSS_Fremont D NIS: 7778 CID: 8103
D NIS 925-555-1212 : CID: 408-555-1212
User 3575's mobile phone : 925-555-1212
V
9 .@ in Partition TraverseSanRamon
7778
Part ition: TraverseFremont CSS: C SS_SanRamon
In the diagram, incoming calls are directed from a PSTN phone with CID 408-555-1212 to two different phones. The device with the Directory Number 3575 is in CSS_SanRamon and the device with Directory Number 3544 is in CSS_Fremont. Both use different outbound gateways. When a request to redirect the incoming calls to the users mobile phone is made, CTI ports from the pool make the outbound calls. They first make calls to Transfer Route Points. They direct the call to the Transfer Route Point that has the same Calling Search Space as the called user (in this case 3544 and 3575). The user with DN 3544 has Calling Search Space CSS_Fremont on their device. Their outbound call is initiated through a Transfer Route Point which has the same Calling Search Space as the called user: CSS_Fremont is the matching Calling Search Space so Transfer Route Point 7777 is used. This routes the call out of the Fremont Gateway. The call to the user at 3575 is routed through the Transfer Route Point 7778 as 3575 has the Calling Search Space CSS_SanRamon on their Directory Number. The call is then routed through the San Ramon Gateway, thus preserving the called users dialing rules.
December 2008
77
The Avaya one-X Mobile Server also has the ability to select a default Transfer Route Point for outbound calls. Selection of the default Transfer Route Point is discussed in the Avaya one-X Administration and Maintenance Guide, document number 18-602144.
Create a Transfer Route Point

Create Transfer Route Points according to the following steps to be performed in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Click on the Device menu. 2. Click on the CTI Route Point submenu. Cisco CallManager 5.0X 1. Click on the Device menu. 2. Click on the CTI Route Point submenu. 3. Click on the Add New button. 4. Enter a Device Name. Example: MS_TransferRP 5. If desired, enter a description: Example: Avaya one-X Mobile Server Transfer Route Point 6. Select the appropriate Device Pool from the drop-down menu. 7. Select a Calling Search Space which includes a partition that allows the PSTN to be reached. If you are creating multiple Transfer Route Points to preserve the Calling Search Spaces of users, select a Calling Search Space that maps to the specified group of users. 8. Select the Location. 9. Click the Save button.
3. Click on the Add a New CTI Route Point hyperlink. 4. Enter a Device Name. Example: MS_TransferRP 5. If desired, enter a description: Example: Avaya one-X Mobile Server Transfer Route Point 6. Select the appropriate Device Pool from the drop-down menu. 7. Select a Calling Search Space which includes a partition that allows the PSTN to be reached. If you are creating multiple Transfer Route Points to preserve the Calling Search Spaces of users, select a Calling Search Space that maps to the specified group of users. 8. Click the Insert button. 9. When prompted to Add a Directory Number to the CTI Route Point, press the OK button.
1 of 3
78
December 2008
Cisco CallManager 4.1X through 4.2X 10. In the Directory Number text box, enter the directory number for the route point. When entering the directory number for an Interceptor Route Point, patterns and wild cards may be used. For example, to make the Avaya one-X Mobile Server intercept all calls in the range 3000 to 3999, enter the directory number as 3XXX.
Cisco CallManager 5.0X 10. Click on the Add a new DN hyperlink on the bottom of the page.
11. In the Partition drop-down menu, select the partition which can be dialed from the Calling Search Space of the managed phones. Additionally, the partition should be dialable from the Calling Search Space of the CTI ports. The Calling Search Space should be the same as in step 7. 12. Leave the Voice Mail Profile set to <None>.
11. In the Directory Number text box, enter the directory number for the route point. When entering the directory number for an Interceptor Route Point, patterns and wild cards may be used. For example, to make the Avaya one-X Mobile Server intercept all calls in the range 3000 to 3999, enter the directory number as 3XXX. 12. In the Partition drop-down menu, select the partition which can be dialed from the Calling Search Space of the managed phones. Additionally, the partition should be dialable from the Calling Search Space of the CTI ports. The Calling Search Space should be the same as in step 7. 13. Leave the Voice Mail Profile set to <None>.
13. Select a Calling Search Space which includes a partition that allows the PSTN to be reached. If you are creating multiple Transfer Route Points to preserve the Calling Search Spaces of users, select a Calling Search Space that maps to the specified group of users.
2 of 3
December 2008
79
Cisco CallManager 4.1X through 4.2X 14. In the Forward No Answer Internal and Forward No Answer External fields, enter the directory number entered in step 10. Set the Calling Search Space drop-down to the same value as in step 13. Important: this will make sure that calls are routed to the IP phone if the Avaya one-X Mobile Server is unavailable. 15. Click the Add button to add the Directory Number.
Cisco CallManager 5.0X 14. Select a Calling Search Space which includes a partition that allows the PSTN to be reached. If you are creating multiple Transfer Route Points to preserve the Calling Search Spaces of users, select a Calling Search Space that maps to the specified group of users.
15. In the Forward No Answer Internal and Forward No Answer External fields, enter the directory number entered in step 11. Set the Calling Search Space drop-down to the same value as in step 14. Important: this will make sure that calls are routed to the IP phone if the Avaya one-X Mobile Server is unavailable. 16. Click the Save button to add the directory number. 3 of 3
Associate Transfer Route Points with the JTAPI User

After creating Transfer Route Points, you need to associate them with the JTAPI user you created in Create the JTAPI user on page 68. To associate a Transfer Route Point with the JTAPI user, perform the following steps in the Cisco CallManager Administration User Interface for the Transfer Route Point you created: Cisco CallManager 4.1X through 4.2X 1. Click on the User menu in Cisco CallManager. 2. Click on the Global Directory menu item. 3. In the User Search text box, enter the name of the JTAPI user you created in Create the JTAPI user on page 68. Cisco CallManager 5.0X 1. Click on the User Management menu. 2. Click on the Application User submenu. 3. In the User Search text box, enter the name of the JTAPI user you created in Create the JTAPI user on page 68. 1 of 2
80
December 2008
Create a Pool of CTI Route Ports for Outbound calls
Cisco CallManager 4.1X through 4.2X 4. Press the Search Button. 5. Click the hyperlink of the JTAPI User you created. 6. In the Application Profiles section on the left-hand side, click on the Device Association hyperlink. 7. On the Device Association page Search for the device name of the Transfer CTI Route Point you created in Create a Transfer Route Point on page 78. 8. Check the checkbox of the CTI Transfer Route Point. 9. Press the Update Selected button to associate the device.
Cisco CallManager 5.0X 4. Press the Find Button. 5. Click the hyperlink of the JTAPI User you created. 6. In the Device Information|Available Devices section of the page, select the Transfer CTI Route Points you created in Create a Transfer Route Point on page 78. 7. Select the CTI Route Points in the Available Devices section and press the down arrow to move it into the Controlled Devices list box.
8. Repeat the process for other Transfer Route Points you created. 9. Press the Save button to update the user. 2 of 2
Create a Pool of CTI Route Ports for Outbound calls

The Avaya one-X Mobile Server uses CTI Route Ports for making outbound calls. For example, when a user has the Simulring feature enabled, an Avaya one-X Mobile Server uses a CTI Port to make an outbound call to the users mobile phone. Since the number of CTI Route Ports needed depends on the number of users, the Avaya one-X Mobile Server administrative user interface provides an automated way to create CTI ports in a range. See Create CTI Ports on page 165.
December 2008
81
Modify AXL Throttle Settings

In order to retrieve configuration settings from the Cisco AXL Database layer, make the following temporary modifications to the AXL Settings. Cisco CallManager 4.1X through 4.2X 1. Click on the Service menu in Cisco CallManager Administration UI. 2. Click on the Service Parameters menu item. 3. For each node in the cluster, do the following: a. Select the node from the Server drop-down menu. b. Select Cisco Database Layer Monitor from the Service drop-down menu. c. Press the Advanced button. d. Scroll to the bottom of the page and set the Maximum AXL Writes Allowed per Minute to 300. e. Press the Update button. 4. Repeat steps 3a to 3e for each node in the cluster. Cisco CallManager 5.0X 1. Click on the System menu. 2. Click on the Service Parameters submenu. 3. For each node in the cluster do the following: a. Select the node from the Server drop-down menu. b. Select Cisco Database Layer Monitor from the Service drop-down menu. Ensure it is set to Active. c. Press the Advanced button. d. Scroll to the bottom of the page and set the Maximum AXL Writes Allowed per Minute to 300. e. Press the Save button.
Note:
Note: This configuration need only be temporarily set while licensing and provisioning of Cisco CallConnect users is taking place. After user licensing and provisioning are finished, this parameter may be set back to its previous setting.
Configure Phones for the Integration

Before the Avaya one-X Mobile Server can intercept calls, you must move IP phones into the Avaya one-X Mobile Server managed partition created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62.
82
December 2008
Configure Phones for the Integration
!
Important:
Important: You should perform this step after configuring the Avaya one-X Mobile Server Administration UI.
To move an IP phone into an Avaya one-X Mobile Server Managed Partition, perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Click on the Device menu. 2. Click on the Phone menu item. 3. In the Find and List Phones search for the phones you want to manage. 4. Click on the phone to go to the Phone Configuration page. 5. Click on the Directory Number in the left-hand side of the page. 6. Change the Partition to the one you created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. 7. In the Call Forward and Pickup Settings section, set the No Answer Ring Duration to 20 seconds. This will ensure that calls to the Mobile phone will have enough time to ring before rolling to voicemail. 8. In the Forwarded Call Information Display section, check the following four boxes: a. Caller Name b. Redirected Number c. Caller Number d. Dialed Number 9. Press the Update button. 10. Press the Reset Device button. 9. Check the Allow control of device from CTI box. 10. Press the Save button. 1 of 2 Cisco CallManager 5.0X 1. Click on the Device menu. 2. Click on the Phone menu item. 3. In the Find and List Phones search for the phones you want to manage. 4. Click on the phone to go to the Phone Configuration page. 5. Click on the Directory Number hyperlink on the left-hand side of the page. 6. Change the Partition to the one you created in Add a Partition for Avaya one-X Mobile Server Managed Phones on page 62. 7. In the Call Forward and Pickup Settings section, set the No Answer Ring Duration to 20 seconds. This will ensure that calls to the Mobile phone will have enough time to ring before rolling to voicemail. 8. In the Forwarded Call Information Display section, check the following four boxes: a. Caller Name b. Redirected Number c. Caller Number d. Dialed Number
December 2008
83
Cisco CallManager 4.1X through 4.2X 11. Press the OK button to reset the device. 12. Click on the Configure Device hyperlink to go back to the device.
Cisco CallManager 5.0X 11. Press the Reset button. 12. Repeat the process for each phone you want to manage. Important Note: If you have a large number of phones to move to the Managed Partition, Cisco does provide a Bulk Administration Tool (BAT) which can make the task easier. The BAT is located on the Applications and Install Plugins page.
13. Click on the Back to Find/List Phones hyperlink. 14. Repeat the process for each phone you want to manage. Important Note: If you have a large number of phones to move to the Managed Partition, Cisco does provide a Bulk Administration Tool (BAT) which can make the task easier. The BAT is located on the Applications and Install Plugins page. 2 of 2
Configure Cisco CallManager to Correctly Pass Caller ID

In order for the Avaya one-X Mobile Server to deliver the correct caller ID to the mobile phone you must use ISDN for connectivity to the PSTN. There are two possible ways to ensure that caller ID is correctly passed. The first method is the preferred method and should be used when there is a mapping or correlation between internal Directory Number and external Directory Number. For example: External Directory Number 510-555-1212 maps to internal Directory Number 1212. The second method can be used if there is no correlation between internal to external Directory Numbers but is not preferred as it is more time-intensive to set up.
Method One: Preserve Caller ID via Route Pattern

The following steps should be performed on the Route Pattern which routes traffic to your PSTN gateway. Typically, this is a 9.@ route pattern or something similar.
84
December 2008
Modify the Route Pattern

Perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Go to the Route Plan menu. 2. Select the Route Pattern menu item. 3. Search for the Route Pattern that routes calls to the PSTN. Most likely, this is a 9.@ Route Pattern. 4. Click on the hyperlink for that Route Pattern. 5. In the Calling Party Transformations section, leave unchecked the checkbox titled Use Calling Party's External Phone Number Mask. 6. For the Calling Party Transform Mask you can set some of the wildcards to mask off the internal Directory Numbers. For example XXXX. 7. For the Prefix Digits (Outgoing Calls) field enter the company wide prefix, for example 510555. This should make outbound calls go out with 510555XXXX where XXXX is the Internal Directory Number. 8. Set Calling Line ID Presentation to Allowed. Cisco CallManager 5.0X 1. Go to the Call Routing menu. 2. Select the Route/Hunt submenu. 3. Select the Route Pattern menu item.
4. Search for the Route Pattern that routes calls to the PSTN. Most likely, this is a 9.@ Route Pattern. 5. Click on the hyperlink for that Route Pattern.
6. In the Calling Party Transformations section, leave unchecked the checkbox titled Use Calling Party's External Phone Number Mask. 7. For the Calling Party Transform Mask you can set some of the wildcards to mask off the internal Directory Numbers. For example XXXX.
8. For the Prefix Digits (Outgoing Calls) field enter the company wide prefix, for example 510555. This should make outbound calls go out with 510555XXXX where XXXX is the Internal Directory Number. 9. Set Calling Line ID Presentation to Allowed.
December 2008
85
Modify the Route List Detail Configuration

Perform the following steps on the CallManager Administration Interface: Cisco CallManager 4.1X through 4.2X 1. Go to the Route Plan menu. 2. Select the Route Pattern menu item. 3. Search for the Route Pattern that routes calls to the PSTN. Most likely, this is a 9.@ Route Pattern. 4. Click on the hyperlink for that Route Pattern. 5. Click the Edit hyperlink adjacent to the Gateway or Route List drop-down. (Note: If the drop-down value is set to Not Selected, then skip the remaining steps.) 6. On the Route List Configuration page, click the Route List Details link on the left hand side. 7. In the Calling Party Transformations section set the User Calling Partys External Phone Number Mask to Default. Leaving the value set to on will not pass the CID correctly. Cisco CallManager 5.0X 1. Go to the Call Routing menu. 2. Select the Route/Hunt submenu. 3. Select the Route Pattern menu item.
6. Click the Edit hyperlink adjacent to the Gateway or Route List drop-down. (Note: If the drop-down value is set to Not Selected, then skip the remaining steps.) 7. On the Route List Configuration page, click the Route List Details link on the left hand side.
8. In the Calling Party Transformations section set the User Calling Partys External Phone Number Mask to Default. Leaving the value set to on will not pass the CID correctly.
Method Two: Preserve Caller ID via External Phone Number Mask.

Perform the following steps to preserve caller ID via the External Phone Number Mask: 1. Set the External Phone Number Mask on every Directory Number on every phone.
86
December 2008
2. Modify the Route Pattern for external calls. 3. Modify the H.323 Gateway settings in Cisco CallManager.
Set the External Phone Number Mask

To set the External Phone Number Mask, perform the following steps in the Cisco CallManager Administration User Interface for every phone that is managed by the Avaya one-X Mobile Server. Cisco CallManager 4.1X through 4.2X 1. Click on the Device menu. 2. Click on the Phone menu item. 3. In the Find and List Phones search for the phones you want to manage. 4. Click on the phone to go to the Phone Configuration page. 5. Click on the Directory Number in the left-hand side of the page. 6. Change the External Phone Number Mask to the full ten-digit number sent to the PSTN. 7. Press the Update button. 8. Press the OK button to reset the device. 9. Click on the Configure Device hyperlink to go back to the device. Cisco CallManager 5.0X 1. Click on the Device menu. 2. Click on the Phone menu item. 3. In the Find and List Phones search for the phones you want to manage. 4. Click on the phone to go to the Phone Configuration page. 5. Click on the Directory Number hyperlink on the left-hand side of the page. 6. Change the External Phone Number Mask to the full ten-digit number sent to the PSTN. 7. Press the Save button. 8. Press the Reset button to reset the device. 9. Repeat the process for every phone in Cisco CallManager. Important Note: Fill in the External Phone Number Mask for every phone in Cisco CallManager, not just the Avaya one-X Mobile Server managed phones. Otherwise, the caller ID will not work for outbound calls from non-managed phones. 1 of 2
December 2008
87
Cisco CallManager 4.1X through 4.2X 10. Click on the Back to Find/List Phones hyperlink. 11. Repeat the process for every phone in the CallManager. Important Note: Fill in the External Phone Number Mask for every phone in Cisco CallManager, not just the Avaya one-X Mobile Server managed phones. Otherwise, the caller ID will not work for outbound calls from non-managed phones.
Cisco CallManager 5.0X
2 of 2
Modify the Route Pattern for External Calls

You need to modify the Route Pattern for External Calls so that it does not mask off any digits. This will allow the Avaya one-X Mobile Server to pass the correct caller ID for calls originating from the PSTN. Perform the following steps in the Cisco CallManager Administration User Interface: Cisco CallManager 4.1X through 4.2X 1. Go to the Route Plan menu. 2. Select the Route Pattern menu item. 3. Search for the Route Pattern that routes calls to the PSTN. Most likely, this is a 9.@ Route Pattern. 4. Click on the hyperlink for that Route Pattern. 5. In the Calling Party Transformations section, check the checkbox titled Use Calling Party's External Phone Number Mask. 6. Set the Calling Party Transform Mask to XXXXXXXXXX. These ten Xs will ensure that the entire ten digits are delivered to the mobile phone. Cisco CallManager 5.0X 1. Go to the Call Routing menu. 2. Select the Route/Hunt submenu. 3. Select the Route Pattern menu item.
6. In the Calling Party Transformations section, check the checkbox titled Use Calling Party's External Phone Number Mask. 1 of 2
88
December 2008
Cisco CallManager 4.1X through 4.2X 7. Leave the Prefix Digits (Outgoing Calls) field blank.
Cisco CallManager 5.0X 7. Set the Calling Party Transform Mask to XXXXXXXXXX. These ten Xs will ensure that the entire ten digits are delivered to the mobile phone. 8. Leave the Prefix Digits (Outgoing Calls) field blank. 9. Set Calling Line ID Presentation to Allowed. 10. Set Calling Name Presentation to Allowed. 2 of 2
8. Set Calling Line ID Presentation to Allowed. 9. Set Calling Name Presentation to Allowed.
Modify the H.323 Gateway Settings in Cisco CallManager

Modify the gateway settings so the Avaya one-X Mobile Server can pass the correct ten-digit caller ID to the mobile phone (or other PSTN phone). Perform the following steps in the Cisco CallManager Administration User Interface. Cisco CallManager 4.1X through 5.0X 1. Go to the Device menu. 2. Click on the Gateway menu item. 3. Search for the appropriate H.323 Gateway in the Find and List Gateways search page. 4. Click on the hyperlink for the appropriate gateway. 5. Under the Outbound Calls section, set the field Calling Party Selection to Originator. 6. Set the field Calling Party Presentation to Allowed or Default. 7. If using National ISDN, set the field Called party IE number type unknown* to National. 8. If using National ISDN, set the field Calling party IE number type unknown* to National. 9. Set the Called Numbering Plan* to Cisco CallManager. 10.Set the Calling Numbering Plan* to ISDN. 1 of 2
December 2008
89
Cisco CallManager 4.1X through 5.0X 11.Set the Caller ID DN to XXXXXXXXXX. These ten Xs allow the Avaya one-X Mobile Server to set the caller ID to an outside PSTN caller. 12.Check the checkbox titled Display IE Delivery. 13.Check the checkbox titled Redirecting Number IE Delivery Outbound. 2 of 2
Modify the Route List Detail Configuration

Perform the following steps on the Cisco CallManager Administration Interface: Cisco CallManager 4.1X through 4.2X 1. Go to the Route Plan menu. 2. Select the Route Pattern menu item. 3. Search for the Route Pattern that routes calls to the PSTN. Most likely, this is a 9.@ Route Pattern. 4. Click on the hyperlink for that Route Pattern. 5. Click the Edit hyperlink adjacent to the Gateway or Route List drop-down. (Note: If the drop-down value is set to Not Selected, then skip the remaining steps.) 6. On the Route List Configuration page, click the Route List Details link on the left-hand side. Cisco CallManager 5.0X 1. Go to the Call Routing menu. 2. Select the Route/Hunt submenu. 3. Select the Route Pattern menu item.
6. Click the Edit hyperlink adjacent to the Gateway or Route List drop-down. (Note: If the drop-down value is set to Not Selected, then skip the remaining steps.) 1 of 2
90
December 2008
Cisco CallManager 4.1X through 4.2X 7. In the Calling Party Transformations section set the User Calling Partys External Phone Number Mask to Default. Leaving the value set to on will not pass the CID correctly.
Cisco CallManager 5.0X 7. On the Route List Configuration page, click the Route List Details link on the left hand side.
8. In the Calling Party Transformations section set the User Calling Partys External Phone Number Mask to Default. Leaving the value set to on will not pass the CID correctly. 2 of 2
December 2008
91
92
December 2008
Chapter 5: Avaya one-X Mobile Administrative Interface

This chapter provides information to get started using the Avaya one-X Mobile administrative interface. It provides information about the Avaya one-X Mobile license and configuring the Avaya one-X Mobile server.
Obtain the Avaya one-X Mobile License

Before you begin working with the Avaya one-X Mobile administrative interface, you must install the Avaya one-X Mobile license. Follow these steps to obtain and install the Avaya one-X Mobile license: 1. To obtain the correct MAC address, go to a command line and type ipconfig /all. (If the information scrolls off the screen, type ipconfig /all | more.) 2. Find the network adapter for which you want to know the MAC address. 3. Locate the number next to the Physical Address. This is the MAC address. The MAC address is displayed in the form 00-02-2D-11-55-4D. Following is an example of the ipconfig /all output: Ethernet adapter Wired: Connection-specific DNS Suffix . : roundfile.com Description . . . . . . . . . . . : ORiNOCO PC Card (5 Volt) Physical Address .. . . . . . . . : 00-02-2D-11-55-4D 4. Use your established RFA web procedures for obtaining licenses for Avaya servers. a. Use the MAC address you obtained in step 3. b. Go to the RFA web site at http://rfa.avaya.com and download the license file to where you can upload later on, typically to a location on a laptop used by services personnel. 5. Log in to the Avaya one-X Mobile server and launch the web browser. 6. Go to the address https://127.0.0.1:8443/WebLM/LicenseServer. 7. Select Access WebLM. The system displays the WebLM application screen.
December 2008
93
Note:
Note: The disable pop-ups option will need to be disabled if the WebLM browser screen does not launch. 8. From the WebLM screen, select License Administration and then enter the WebLM default administrative password. 9. After your initial login to WebLM, the system prompts you to change the password. When you do, WebLM logs you out and expects you to log back in with your new password. 10. Select Install license. 11. Select Browse and navigate to the location where you saved the license file in step 4. 12. Select Install. The proxy server will renew acquired licenses every 5 minutes. Initially, however, it has not acquired any licenses (since none were installed) so the proxy server will attempt to acquire licenses every 60 seconds. After it has acquired all licenses, it will renew them every 5 minutes. 13. Proceed with the Avaya one-X Mobile Server administrative interface.
To access the Avaya one-X Mobile Server administrative user interface, first install the Avaya one-X Mobile Server Software. See the Avaya one-X Mobile Installation Guide, document number 18-602135, for instructions on how to install the software. The Avaya one-X Mobile Server administration user interface is available at the following address: http(s)://<server ip or name>/Admin. Microsoft Windows credentials are required to log in to the Avaya one-X Mobile Server Administrative Web site. This includes credentials for the local host of the Avaya one-X Mobile Server or for the domain for the Avaya one-X Mobile Server.
94
December 2008
Avaya one-X Mobile Administration Status Screen
Avaya one-X Mobile Administration Status Screen

The status screen is displayed by default when navigating to the Avaya one-X Mobile Server administrative interface.
Various administrative tasks can be accessed by clicking tabs on this screen. If the Avaya one-X Mobile Server is being configured for the first time, click the Server Setup tab.
Configure the Avaya one-X Mobile Server

The Server Setup section of the Avaya one-X Mobile administrative interface enables the configuration of the servers authentication credentials. It also enables configuration of administrative information related to the various servers that the Avaya one-X Mobile Server communicates with. The Server Setup page provides two tabs:
Settingsenables configuration of the SMTP Settings and Mobile Client Settings. The Avaya one-X Mobile Server uses the SMTP server to send notifications of new voicemail. Split Server Configurationenables configuration of internal and external servers when multiple servers are used. The Split Server Configuration settings can be configured only if a split server setup was chosen at the time of installation.
December 2008
95
Configure the Server Settings

To configure the Avaya one-X Mobile Server Settings: 1. Click Server Setup > Settings.
2. In the SMTP Username field, enter the username that will be used to login to the SMTP server. 3. In the SMTP Password field, enter the SMTP password. Asterisks will appear in the field for security purposes. 4. In the SMTP Server field, enter the IP address or hostname of the SMTP server. For example: 192.168.20.6 (Enter the SMTP Username and Password only if the server requires authentication.) 5. In the SMTP Port field, enter the number of the SMTP port. The default port number for SMTP is typically 25. 6. In the Senders email field, enter the senders email address. This email address is the address that the end user will see as the sender of messages sent to various web clients. Use a descriptive name such as notifier@example.com. 7. In the Administrators email field, enter the Avaya one-X Mobile Server administrators email address. This is the email address of the administrator that will be setting up and managing the system. When certain events occur, the Avaya one-X Mobile Server can send an email to notify the IT administrator. An example of this is when an account is locked out due to exceeding the allowed number of login retries. 8. In the User Interface Language drop-down box, select the appropriate language.
96
December 2008
Configure the Avaya one-X Mobile Server
9. In the Mobile Client Settings section, click the checkbox to Allow iPhone software updates on the server from app.avaya.com for iPhone clients. 10. Click Save Changes. See the Avaya one-X Mobile Installation Guide, document number 18-602135, for more information if using a split server configuration. The Avaya one-X Mobile Server will need to know the IP addresses of external servers for security purposes. This will prevent connections from non-approved servers.
Configure Split Server Settings

The Split Server Configuration settings can be configured only if a split server setup was chosen at the time of installation. To configure the split server settings: 1. Select Server Setup > Split Server Configuration.
The Split Server Configuration page identifies the IP address of the internal server as it appears to the external servers. It also identifies the IP addresses of all servers allowed access to the internal server. Note: The localhost field is pre-populated with the loopback IP address 127.0.0.1 2. Modify the fields as appropriate, and then click Save Changes. 3. To add a server that will be allowed access to the internal server, click Add Trusted Server.
Note:
December 2008
97
4. In the Server Name field, enter a name for this server. 5. In the Server IP Address field, enter the server IP address as appropriate. 6. In the Server Type drop-down box, select the type of server. 7. Click Save.
98
December 2008
Chapter 6: Avaya Setup

The Avaya Setup section of the Avaya one-X Mobile administrative interface allows you to set up the Avaya one-X Mobile Server for systems that use Avaya Communication Manager. If your system uses only Cisco CallManager, see Chapter 11: Cisco Setup on page 145. Perform the Avaya Setup tasks in the following order: 1. Setup Profiles: a. Create a Provisioning Profile b. Create a CTI Profile c. Create a Voicemail Profile d. Create a Corporate Directory Profile Note: Steps a through d can be completed in any order. e. Create a Class of Service 2. Configure CTI Resources: a. Configure CTI Ports b. Create VDNs 3. Administer Users: a. Import Users b. Manage Unlicensed Users c. Manage Licenses Users 4. Configure Dial Plans
Note:
Create a Provisioning Profile

The Provisioning Profile must be completed before any further steps are taken. The Provisioning Profile task imports the users from the Active Directory and is used for two purposes:
To indicate the source of user accounts that will be imported into the Avaya one-X Mobile database. To indicate the source for user account authentication.
December 2008
99
Avaya one-X Mobile is capable of using LDAP v3 directories for the Provisioning Profile. To create a new Provisioning Profile: 1. Select Avaya Setup > Setup Profiles > Provisioning Profile.
2. Click New Provisioning Profile.
3. In the Profile Name field, enter the name of the new profile. 4. In the Description field, enter a description of the profile. 5. In the LDAP Search Type drop-down box, select the appropriate search type. This field defines the type of LDAP search based on the LDAP platform. A specific search routine is provided for Active Directory, SunOne, and Netscape_iPlanet. In addition, a generic search routine is provided that is platform independent. Choosing the appropriate platform will provide better search performance.
100
December 2008
6. In the LDAP User DN field, enter the LDAP user DN (for example, cn=administrator, ou=users, dc=example, dc=com). This is the user that will be used to search the directory for Avaya one-X Mobile users. 7. In the LDAP Hostname field, enter the LDAP hostname. 8. In the LDAP Port Number field, enter the LDAP port. The default value for Microsoft Active Directory is 389. 9. In the LDAP Password field, enter the password for this user. Asterisks appear in the field for security purposes. 10. In the LDAP Base DN field, enter the search base DN (for example, ou=users, dc=example, dc=com.) Depending on the Directory setup, it may be necessary to fill out the advanced settings for LDAP attributes. The LDAP Attributes section allows for parameterization of the required fields as different directory implementations may use different attribute names to store the information required by the Avaya one-X Mobile Server. Upon installation, Avaya one-X Mobile defaults many of these LDAP attributes to commonly used Microsoft Active Directory attribute names. These LDAP attributes may need to be changed depending on the implementation of the Directory. 11. To change the LDAP attribute settings, click Show Advanced Settings.
12. In the Extension field, enter the attribute name used to hold the extension. If the extension is not housed in the directory, it may be derived as part of the import process. Note: This field is used to determine the extension if the field Determine Extension from is set to From LDAP extension attribute in the Advanced Settings of the Class of Service. See step 33 in Create a Class of Service on page 115 for more information. 13. In the 10 Digit Phone Number field, enter the attribute name for phone number.
Note:
December 2008
101
Note:
Note: This field is used to determine the extension if the field Determine Extension from is set to 10-digit phone number manually in the Advanced Settings of the Class of Service. See step 33 in Create a Class of Service on page 115 for more information. 14. In the Handle or UserID field, enter the attribute name user ID. 15. In the First Name field, enter the name users first name. 16. In the Last Name field, enter the attribute name for the users last name. 17. In the Email field, enter the attribute name for the users email address. 18. In the Department field, enter the attribute name for the users department. 19. In the Directory Fetch Size field, enter the appropriate number. The LDAP administrator may have limited the return value size of requests by setting an LDAP page size limit. If this has been done, you must set the Directory Fetch Size to be equal to or less than the LDAP page size limit. Otherwise, requests to the LDAP server may time out. 20. In the Search Referrals drop-down box, select the appropriate setting. The options are:
None select None if your User DN contains your LDAP Base DN, or if your User DN is at a higher level in the hierarchy than the LDAP Base DN. Follow select Follow if your LDAP User DN is deeper than the LDAP Base DN in the DN hierarchy, or if your User DN is in a completely different tree. The LDAP server must allow for this type of search. Ingore this option is not recommended. Throw this option is not recommended.
21. Click Save to save the Provisioning Profile settings. Note: If an entry was not configured correctly, an error message appears. Red text indicates the section(s) that contain errors.
Note:
102
December 2008
Create a CTI Profile

The CTI Profile is necessary to create a link to the AES to manage inbound and outbound calls for the Avaya one-X Mobile users. Note: Before setting up the CTI Profile, make sure that the AES integration steps have been completed. See Configure Integration with Avaya Application Enablement Services on page 40 for instructions on configuration of AES for Avaya one-X Mobile. create a new CTI Profile copy an existing CTI Profile
Note:
To create a new CTI Profile, you can:

Procedures for both methods are provided in this section.
Create a New CTI Profile

There are two steps involved in creating a new CTI Profile. You must: 1. Configure TSAPI and get TSAPI links 2. Create the CTI Profile using the selected TSAPI link To create a new CTI Profile: 1. Select Avaya Setup > Setup Profiles > CTI Profile.
December 2008
103
2. Click New CTI Profile.
3. In the CTI Profile Name field, enter the name for this profile. 4. In the Description field, enter a description of this profile. 5. In the AES Hostname field, enter the hostname of the Application Enablement Services. Use the Avaya sites Administration tool for more information. Make sure the hostname entered is resolvable from the Avaya one-X Mobile Server. 6. In the JTAPI Port field, enter the JTAPI port number. The default value for the JTAPI port is 450. 7. Click Next. A status screen appears. Processing may take a few minutes. Note: The Avaya one-X Mobile Server should be able to see the domain where AES is available, or AES is visible. If DNS is not setup for the AES server, then a hosts file entry should be made for the AES hostname entered in the AES hostname field. After processing, additional fields appear on the New CTI Profile screen.
Note:
8. In the TLinks drop-down box, choose the appropriate link. This should match the TLink that was created in the AES configuration. See Configure Integration with Avaya Application Enablement Services on page 40 for more information.
104
December 2008
9. In the JTAPI Username field, enter the JTAPI username that was created in the AES configuration. See Configure Integration with Avaya Application Enablement Services on page 40 for more information. 10. In the JTAPI Password field, enter the JTAPI password that was created in the AES configuration. See Configure Integration with Avaya Application Enablement Services on page 40 for more information. 11. In the Switch Name field, enter the name of the switch as it is known in the AES configuration. 12. In the DMCC Username field, enter the DMCC username that was created in the AES configuration. See Configure Integration with Avaya Application Enablement Services on page 40 for more information. 13. In the DMCC Password field, enter the DMCC password that was created in the AES configuration. See Configure Integration with Avaya Application Enablement Services on page 40 for more information.
14. In the Communication Manager Login field, enter the login used to make changes in the Avaya Communication Manager. Note: The Communication Manager login must have administrative privileges. 15. In the Communication Manager Password field, enter the password for the Avaya Communication Manager login. 16. In the Communication Manager Hostname field, enter the Avaya Communication Manager hostname. 17. For the Enable Virtual Endpoint support checkbox, click this checkbox to enable the virtual endpoint feature. This feature is available on Avaya Communication Manager 5.0 and above only and requires the switch to be configured with MFE.
Note:
December 2008
105
Note:
Note: If the Enable Virtual Endpoint support checkbox is grey and you are not able to select it, check to see if Apache Tomcat is running. If it is not, start the service using either services.msc or Avaya one-X Mobile administration. 18. If you selected Enable Virtual Endpoint support in the previous step, in the MFE Port field, enter the MFE port configured on the switch. The MFE Port field appears only when Enable Virtual Endpoint support is checked. In the Switch Feature Access Codes section, you must collect the FACs from the switch and enter them into the Avaya one-X Mobile Server on this page. The server needs these FACs to perform call control actions on behalf of the user. 19. In the EC500 Enable FAC field, enter the FAC to enable EC500. This FAC turns EC500 on. 20. In the EC500 Disable FAC field, enter the FAC to disable EC500. This FAC turns EC500 off. 21. In the EC500 SAFE FAC field, enter the EC500 SAFE FAC. This FAC changes the destination of the EC500 mobile phone. 22. In the SAC enable FAC field, enter the FAC to enable SAC. This FAC enables Send All Calls (SAC). 23. In the SAC disable FAC field, enter the FAC to disable SAC. This FAC disables Send All Calls (SAC). Note: When you save the CTI Profile, you may receive the error "Unable to configure TSAPI. Invalid AES hostname or JTAPI port." If this error occurs, one possible resolution is to configure an additional internal server IP address when you configure the split server settings. Do the following: 1. Select Server Setup > Split Server Configuration. 2. Click Add Trusted Server. 3. Follow steps 4 through 7 in Configure Split Server Settings on page 97. In step 6, be sure to select Internal as the server type.
Note:
106
December 2008
Create a Voicemail Profile
Copy a CTI Profile

To create a new CTI Profile by copying an existing CTI Profile: 1. Select Avaya Setup > Setup Profiles > CTI Profile.
2. Click Copy Profile next to the profile to be copied.
3. In the CTI Profile Name field, rename the profile. 4. Change information in the other fields as appropriate. 5. Click Next. A status screen appears. Processing may take a few minutes. After processing is complete, the New CTI Profile screen appears. The profile reflects the new profile information.

Although the Voicemail Profile types are different for Avaya and Cisco setups, a Voicemail Profile created under the Avaya setup can be used in a Cisco Class of Service, and a Voicemail Profile created under the Cisco setup can be used in an Avaya Class of Service.
December 2008
107
There are two types of Voicemail Profiles:
Modular Messaging with Exchange Integrationthe settings displayed under this type of Voicemail Profile are LDAP Settings and Exchange Administrative User Setting. Note: The user specified in the Exchange Administrative User Setting section must be a member of the Domain Administrators group and have permissions to log on as a Service locally on the Avaya one-X Mobile Server. See Configure the Exchange Administrative User on page 54 to create an Exchange Administrative User with the required permissions.
Note:
Modular Messaging with MSS (Default for Avaya)the settings displayed under this type of Voicemail Profile are MSS Administrative User Setting, MSS LDAP Settings, and Voicemail Mailbox Setting. Note: The server specified in the MSS Administrative User Setting section should be set up in the Trusted Servers section on the MSS Admin page. See Configure Integration with Avaya Modular Messaging on page 51 for more information.
Note:
To create a new Voicemail Profile: 1. Select Avaya Setup > Setup Profiles > Voicemail Profile.
2. Click New Voicemail Profile.
3. In the Profile Name field, enter a profile name. 4. In the Profile Type drop-down box, select the profile type. 5. In the Voicemail Platform Hostname field, enter the hostname of the voicemail platform.
108
December 2008
6. In the IMAP Port field, enter the IMAP port. In the previous field, if you selected Modular Messaging with MSS, the IMAP Port should be a secure port. For the Modular Messaging with Exchange Integration profile type, the IMAP port is often 993. 7. In the Voicemail Audio Format drop-down box, select the format that matches the audio encoding set for the voicemail domain on the Modular Messaging System. 8. Depending on the Profile Type you selected in step 4, do one of the following:
If you selected Modular Messaging with Exchange Integration, see Configure Modular Messaging with Exchange Integration on page 109. If you selected Modular Messaging with MSS, see Configure Modular Messaging with MSS on page 111.
Configure Modular Messaging with Exchange Integration

If you selected Modular Messaging with Exchange Integration in the Profile Type field in the New Voicemail Profile, the LDAP Settings and Exchange Administrative User Setting sections appear as shown below.
The LDAP Settings section enables the configuration of the location and authentication credentials of the Active Directory associated with the Microsoft Exchange Server. The Avaya one-X Mobile Server must be a member of a domain that is trusted by the Microsoft Exchange Server(s) where Avaya Modular Messaging deposits voicemail. Access to Active Directory is required by the Avaya one-X Mobile Server for the following tasks:

To accurately map received voice messages with the person that left the message. To retrieve configuration information such as the hostname of the Microsoft Exchange Server for a particular user. To retrieve the Microsoft Exchange Alias of a particular user.
December 2008
109
The Exchange Administrative User Setting section enables the configuration of the location and authentication credentials of the Exchange Server. Access to the Exchange Server is required by the Avaya one-X Mobile Server to provide Visual Voicemail functionality. You must enter authentication credentials of the Exchange Administrator User so that the Avaya one-X Mobile Server can access voicemail for any user. Complete these fields as follows: 1. In the Active Directory IP Address field, enter the Active Directory IP address or hostname. 2. In the Active Directory Port Number field, enter the Active Directory LDAP port number. In Active Directory deployments, port 389 is the default LDAP port. 3. In the Administrator User DN field, enter the Active Directory administrator user DN (for example, cn=administrator, cn=users, dc=example, dc=com). 4. In the Administrator Password field, enter the Active Directory administrator password. Asterisks appear for security purposes when the password is entered. 5. In the User Base DN field, enter the Active Directory user base DN (for example, cn=users, dc=example, dc=com). This should be the base DN where all users of Modular Messaging are stored. 6. In the Exchange Username field, enter the username for the Exchange Administrative User you wish to use for Visual Voicemail to access end user messages. Note that the domain name must be included here for Visual Voicemail to work correctly (for example, mydomain/administrator). Note: This user must be a member of the Domain Administrators group. Additionally, the user must have permissions to log on as a Service locally on the Avaya one-X Mobile Server. See Configure the Exchange Administrative User on page 54 for more information. 7. In the Exchange Password field, enter the Exchange Administrative User password. Asterisks appear for security purposes when the password is entered. 8. Click Save to save the Voicemail Profile settings. Note: If an entry was not configured correctly, an error message appears. Red text indicates the section(s) that contain errors.
Note:
Note:
110
December 2008
Configure Modular Messaging with MSS

If you selected Modular Messaging with MSS in the Profile Type field in the New Voicemail Profile, the MSS Administrative User Settings, MSS LDAP Settings, and Voicemail Mailbox Settings sections appear as shown below.
Complete these fields as follows: 1. In the Trusted Server Name field, enter the name. 2. In the Trusted Server Password field, enter the password. Note: The name and password specified in the Trusted Server Name and Trusted Server Password fields, should be set up in the Trusted Servers section on the MSS Admin page. See Configure Integration with Avaya Modular Messaging on page 51 for more information. 3. In the LDAP User DN field, enter the LDAP user DN (for example, cn=<trusted_server_name> such as oneXMobile, dc=Avaya). 4. In the LDAP Hostname field, enter the LDAP hostname (for example, <your_mss_server> such as IP address/FQDN of the MSS). 5. In the LDAP Port Number field, enter the LDAP port number (for example, <LDAP Port/ SSL LDAP Port from the MSS> such as 389). 6. In the LDAP Password field, enter the LDAP password.
Note:
December 2008
111
7. In the LDAP Base DN field, enter the search base DN (for example, ou=People, dc=Avaya). 8. In the Voicemail Mailbox ID Source drop-down box, select the source for the voicemail mailbox ID. 9. Click Save to save the Voicemail Profile settings. Note: If an entry was not configured correctly, an error message appears. Red text indicates the section(s) that contain errors.
Note:
Create a Corporate Directory Profile

In order to provide the Avaya one-X Mobile client Corporate Directory Lookup feature, the Avaya one-X Mobile Server must integrate with a directory source such as Avaya one-X Mobile Server or Active Directory. This integration is known as a Corporate Directory Profile and may later be applied to a Class of Service which can be applied to a user group. To create a Corporate Directory Profile: 1. Select Avaya Setup > Setup Profiles > Corporate Directory Profile.
112
December 2008
2. Click New Corporate Directory Profile.
3. In the Profile Name field, choose a unique profile name which will identify this profile. Note: This is the name that is used when specifying a Corporate Directory Profile for a Class of Service. 4. In the Description field, enter a description of this profile. 5. In the LDAP Search Type drop-down box, select the LDAP search type. This field defines the type of LDAP search based on the LDAP platform. A specific search routine is provided for Active Directory, SunOne, and Netscape_iPlanet. In addition, a generic search routine is provided that is platform independent. Choosing the appropriate platform will provide better search performance. 6. In the LDAP User DN field, enter the LDAP user DN (for example, cn=Administrator, ou=users, dc=example, dc=com). 7. In the LDAP Hostname field, enter the LDAP hostname. 8. In the LDAP Port Number field, enter the LDAP port number. The default value for Microsoft Active Directory is 389. 9. In the LDAP Password field, enter the LDAP password. 10. In the Corporate Directory Search Base DN field, enter the corporate directory search base DN (for example, ou=users, dc=example, dc=com). This is the default value for the Avaya one-X Mobile Server.
Note:
December 2008
113
11. Click Show Advanced Settings to view the LDAP Attributes section.
12. In the User LDAP Filter field, enter the user LDAP filter. This field provides for an LDAP search filter specification used to build the Corporate Directory. 13. In the Extension field, enter the attribute name used to hold the extension. If the extension is not housed in the directory, it may be derived as part of the import process. 14. In the 10 Digit Phone Number field, enter the attribute name for phone number. 15. In the Handle or UserID field, enter the attribute name user ID. This should be capitalized and will be the same as what was entered in the LDAP Attributes section of the Provisioning Profile tab in the Setup Profile section. 16. In the First Name field, enter the attribute name for the users first name. 17. In the Last Name field, enter the attribute name for the users last name. 18. In the Email field, enter the attribute name for the users email address. 19. In the Department field, enter the attribute name for the users department address. 20. In the Directory Fetch Size field, enter the appropriate number. The LDAP administrator may have limited the return value size of requests by setting an LDAP page size limit. If this has been done, you must set the Directory Fetch Size to be equal to or less than the LDAP page size limit. Otherwise, requests to the LDAP server may time out. 21. In the Search Referrals drop-down box, select the appropriate setting. The options are:
None select None if your User DN contains your LDAP Base DN, or if your User DN is at a higher level in the hierarchy than the LDAP Base DN. Follow select Follow if your LDAP User DN is deeper than the LDAP Base DN in the DN hierarchy, or if your User DN is in a completely different tree. The LDAP server must allow for this type of search. Ingore this option is not recommended.
114
December 2008
Create a Class of Service
Throw this option is not recommended.
22. Click Save to save the Corporate Directory Profile settings. Note: If an entry was not configured correctly, an error message appears. Red text indicates the section(s) that contain errors.
Note:

After completing the profiles, a Class of Service is required. Class of Service is a representation of ways in which an Avaya one-X Mobile user will interact with the system. Class of Service settings include profiles (as described earlier in this chapter) as well as non-aggregated settings. Note: A valid Provisioning Profile is required to create a Class of Service. An error message appears if there is an attempt to create a Class of Service using an invalid Provisioning Profile. 1. Select Avaya Setup > Setup Profiles > Class of Service.
Note:
To create a new Class of Service:
December 2008
115
2. Click New Class of Service.
3. In the Class of Service Name field, enter the name for this Class of Service. 4. In the Description field, enter a description of this Class of Service. 5. In the Provisioning Profile drop-down box, select the appropriate profile. 6. In the Voicemail Profile drop-down box, select the appropriate profile. Note: Select No Voicemail Profile to configure this Class of Service so that users will not have voicemail on their mobile client.The mobile client will provide Call Control only and will not be integrated with a voicemail platform. 7. In the Corporate Directory Profile drop-down box, select the appropriate profile. 8. In the CTI Profile drop-down box, select the appropriate profile.
Note:
9. Click the checkbox to Allow voicemail to be stored on the mobile device. Note: Do not click this checkbox if you want to disable voicemail download to the Avaya one-X Mobile Web portal or Avaya one-X Mobile client. When the voicemail download feature is disabled, the user will not be able to download or save voicemail on the client, or download, save, or forward voicemail from the Web portal. If voicemail download is disabled, to listen to voicemail from the Web portal or client, the user will call corporate voicemail directly. 10. Click the checkbox to Allow voicemail to be forwarded via email.
Note:
116
December 2008
Note:
Note: Do not click this checkbox if you want to disable the forward via email feature available on Avaya one-X Mobile Web portal. 11. Click the checkbox to Require login each time one-X Mobile is launched on mobile device, if required. 12. Set the Maximum number of attempts before user is locked out (default is 5). 13. Set the Time period for which a user is locked out in minutes (default is 90).
14. Set the Maximum number of phones to Send Calls to. Note: For Avaya Setup, the minimum and maximum number of phones to send calls to is 2 and 5 respectively. 15. Set the PSTN Prefix (which is the number necessary to dial to reach an outside line). 16. Click the checkbox to Require DTMF during Callback via PBX, if required. Note: If you require DTMF during callback, the EC500 Confirmed Answer feature should be disabled. If it is not disabled, the system will not operate properly. The Confirmed Answer feature is available with Avaya Communication Manager 5.0 and above only. 17. Click the checkbox to Translate 10-digit numbers to extensions, if required. 18. Click the checkbox to Use Dial Plan for EC500 if EC500 numbers used in the Avaya one-X Mobile clients need to be modified before using in a dialable EC500 Self-Administration Access string. This checkbox is used in conjunction with Dial Plans in the Avaya one-X Mobile administrative web. A dialable EC500 Self-Administration Access string is in the format <EC500 self-administration access code> <station number><EC500 number># Avaya one-X Mobile uses the EC500 Self-Administration Access string:
Note:
Note:
while updating the mobile phone number using Avaya one-X Mobile end user web
December 2008
117
for the destination where the user will take the call during Callback calls using the Avaya one-X Mobile clients.
For example, if you click the checkbox for Use Dial Plan for EC500 and you have a dial plan like the sample shown below, then any number that follows the format 123XXXX would be modified into format 1510123XXXX for use with the EC500 Self-Administration Access Code to modify a stations EC500 destination.
19. Click the checkbox to Use National Prefix if EC500 numbers used in the Avaya one-X Mobile clients need a National Direct Dialing prefix. This modified number is in a dialable EC500 Self-Administration Access string. The value for the National Direct Dialing prefix is set in the Dial Plans tab in the Avaya one-X Mobile administrative web.
20. Click the checkbox to Require client software upgrades, if required. 21. Set the Number of days to warn users before making updates mandatory. 22. In the RIM Blackberry Connection Settings drop-down box, select the appropriate setting. 23. In the User Interface Language drop-down box, select the appropriate language. 24. In the End user website server URL, enter the appropriate URL. 25. If this is a secure server, click the checkbox to set this as is a secure server.
118
December 2008
26. Click Show Advanced Settings to view the LDAP Attribute Source Profiles. In the LDAP Attribute Source Profiles section, there is an opportunity to fine tune the Avaya one-X Mobile Server to use different directory sources for different data fields collected from directories. In some enterprise deployments, one directory may contain some information such as first name, last name; while another may contain information such as the 10-digit phone number. The Avaya one-X Mobile Server can map from one directory to another; where the sources are the Corporate Directory Profile and the Provisioning Profile. The Provisioning Profile will always be used for authentication and the Corporate Directory Profile may be used for name resolution. In all cases, the Handle or UserID must be the key between the two directory sources. That is, if mapping is done, the UserID in one directory must match that of the other directory. Use the drop-down boxes to tell the Avaya one-X Mobile Server from what directory to source the different attributes.
27. In the Handle or UserID drop-down box, select the appropriate profile. 28. In the 10 digit Phone Number drop-down box, select the appropriate profile. 29. In the First Name drop-down box, select the appropriate profile. 30. In the Last Name drop-down box, select the appropriate profile. 31. In the Email drop-down box, select the appropriate profile. 32. In the Department drop-down box, select the appropriate profile. 33. In the Determine Extension from drop-down box, select the appropriate source. Note: For the Determine Extension from drop-down box, extensions for users can be determined either directly from the LDAP attribute or manually from the 10-digit phone number. Manual determination can be done in one of two ways:

Note:
automatically using AES conversion and AES dial plan rules. algorithmically by entering the number of leading digits to strip from the 10-digit phone number and/or adding a prefix after the digits have been stripped.
December 2008
119
34. In the LDAP Extension Source drop-down box, select the appropriate profile. 35. Click Save.
Configure CTI Ports

CTI Ports are used to make outbound calls from the switch. An example of when this would be used is when a user has their Simulring feature enabled. A CTI Port would be used to make a call to the mobile phone so both the desk phone and the mobile phone would ring. The Avaya one-X Mobile Server can automatically create CTI Ports for use by the application. The Avaya one-X Mobile database provides the option to create database entries for CTI Ports/ VDNs for CTI Ports that already exist. This allows creation of CTI Ports/VDNs in the database if they already exist. To view CTI Port information, select Avaya Setup > CTI Resources > CTI Ports.
120
December 2008
Configure CTI Ports
To make CTI Ports available to the Avaya one-X Mobile Server: 1. Click Create New Directory Range.
2. In the Directory Number Range fields, enter the directory number range of the CTI Ports to be added. Choose a range of numbers which do not conflict with any other stations or directory numbers in Avaya Communication Manager. 3. In the Class of Service drop-down box, select the Avaya one-X Mobile Class of Service which was created in the Class of Service section. This Class of Service should have a properly configured CTI Profile. 4. In the Switch Class of Restriction field, enter a Class of Restriction for the CTI Ports. It may be helpful to use a special one so they can be administered as a group. 5. In the Switch Class of Service field, enter a Switch Class of Service that is preconfigured on Avaya Communication Manager. For Avaya one-X Mobile to work properly, console permissions must be set to y in the Class of Service table. 6. If ports already exist on the switch that will be used, enter all the information relating to those ports in the appropriate fields, then click the checkbox next to Create CTI Ports in one-X Mobile database only. Note: If the checkbox remains unchecked before clicking Save, new CTI ports will be created in the next step. 7. Click Save to save the CTI Ports you have created. A message appears notifying you that the ports are being created. After the process is complete, it is recommended that you test the ports to ensure they were created correctly. This will ensure that all calls are routed successfully.
Note:
December 2008
121
Create VDNs
!
Important:
Important: If your communications system is running Avaya Communication Manager Release 5.0 or above, instead of creating VDNs, the preferred method to ensure the voicemail system does not answer a callback and then connect the callback destination party to the voicemail platform is to configure the Confirmed Answer feature on Avaya Communication Manager. See Configure the Confirmed Answer Feature (for CM 5.0 and above) on page 27 for more information.
Vector Directory Numbers (VDNs) are used to collect Dual Tone Multi Frequency (DTMF) tones to ensure that a network voicemail platform does not answer a callback and then connect the callback destination party to the voicemail platform. To avoid this situation, a tone is collected to ensure that a human being answers the first leg of the callback. As part of this, VDNs are used to play a prompt to the user when they answer the first leg of a callback call. For example, if a user wishes to place a callback to their mobile phone, they will hear a message, stating to press a digit or tone to complete the call. Once Avaya one X Mobile detects the DTMF entry by the user, the second leg of the callback is placed. If the caller does not press the appropriate key, the server will not initiate the second leg of the callback. This prevents the second leg of the callback from being placed if mobile phone connectivity is lost before the call is completed. The Avaya one-X Mobile platform must have knowledge of provisioned VDNs to function. VDNs can be created from the Avaya one-X Mobile administration interface and from Avaya Communication Manager. They can also simply be uploaded if they already exist. Note: Using VDNs to collect DTMF tones is not supported for virtual extensions.
Note:
To view VDN information, select Avaya Setup > CTI Resources > VDNs.
122
December 2008
Create VDNs
To make VDNs available to the Avaya one-X Mobile Server, click Create New Directory Range.
This page is where you create VDN triplets. A triplet consists of two VDNs and one CTI Port. Note: If the VDNs already exist on the switch and you do not want to create new VDNs, click the checkbox for Create VDNs in one-X Mobile database only. This will create VDNs only in the Avaya one-X Mobile Server database. How many triplets you create depends on how many callbacks you expect at your busy hour, since it is a busy hour calculation. One triplet is needed to service a callback. They are returned to the pool after use. If you run out of VDN triplets, the call is placed, but no DTMF tone is collected. The second leg of the call is immediately placed.
Note:
Some important information about triplets:
For each triplet, follow these steps: 1. In the Virtual Directory Number Range field, enter the directory number range of the VDNs and CTI Ports to be added. Choose a range of numbers which do not conflict with any other stations or directory numbers in Avaya Communication Manager. Note: This range must be a multiple of 3 to accommodate two VDNs and a CTI Port triplet. You will receive an error if your range is not valid. 2. In the CTI Profile drop-down box, select the Avaya one-X Mobile CTI Profile which was created in the CTI Profile section. 3. In the Switch Class of Service, enter the Class of Service in the switch. The Switch Class of Service should be one that is preconfigured on Avaya Communication Manager. For Avaya one-X Mobile to work properly, console permissions must be set to y in the Class of Service table. 4. In the Class of Restriction field, enter a Class of Restriction for the CTI Ports. It may be helpful to use a special one so they can be administered as a group.
Note:
December 2008
123
5. In the TN field, enter a tenant number. A TN is a tenant partition number and identifies the partition for the phone you are administering. The default value for this field is 1. 6. Click the checkbox for Create VDNs in one-X Mobile database only if the VDNs already exist on the switch and you do not want to create new VDNs. This will create VDNs only in the Avaya one-X Mobile Server database. If the checkbox remains unchecked, new VDNs will be created. 7. Click Save to create the VDNs in the switch and Avaya one-X Mobile platform. 8. Before proceeding, make sure all required triplets were created. 9. See Configure VDN Triplets on page 30 for instructions on how to configure the VDNs that have been created.
Administer Users
This section describes how to provision users for whom the Avaya one-X Mobile Server services will be available. This section describes how to:

Import Users Manage Unlicensed Users Manage Licensed Users
Import Users
To import users: 1. Select Avaya Setup > Users > Import Users.
2. In the Class of Service drop-down box, select the appropriate Class of Service.
124
December 2008
Administer Users
3. In the Filter field, enter the filter. Valid filters are similar to those entered directly in LDAP.
To import a single user, use sAMAccountName=<pbxusername>. For example, to import a single user enter sAMAccountName=edge8. To import several users, use wildcards cn=*, objectclass=user. For example, to import several users, enter cn=edge*, cn=*, mail=*mydom.com.
Note:
Note: The screen does not refresh itself during a user import. 4. Click Import Users.
Manage Unlicensed Users

To view all imported user accounts that are not yet licensed: 1. Select Avaya Setup > Users > Unlicensed User Management.
2. To search for specific users, enter text in the Search field. 3. To search for all users, leave the Search text box blank and press Enter or click Show All, if it is available. 4. To navigate to a particular section of users when a large number of results are returned, use the Sort by drop-down box.
License Selected Users

To license a user: 1. On the Unlicensed User Management screen, click the checkbox next to the users name you want to license.
December 2008
125
2. Click License Selected Users. This will license the user in the Avaya one-X Mobile Server database and decrement the number of licenses available for assignment. A message appears letting you know that it is importing users in a background process. Licensing users can take some time depending on the size of the user base. When users are licensed, the Avaya one-X Mobile Server works in the background to retrieve required provisioning information for the user. When complete, you will be able to locate the new users in the Licensed User Management tab.
Manage Licensed Users

To view all imported user accounts that are licensed: 1. Select Avaya Setup > Users > Licensed User Management.
2. To search for a user, in the Search field enter the users last name, first name, extension, Class of Service, or department. 3. To change the page displayed, in the Show drop-down box, select the appropriate page. 4. To change the way the information is sorted on the page, in the Sort by drop-down box, make the appropriate selection. To manage licensed users, the following features are available:

Change Class of Service Reprovision Selected Users
126
December 2008
Administer Users
Unlicense Selected Users Delete Selected Users
Change Class of Service

To change the Class of Service for a user or group of users: 1. On the Licensed User Management screen, click the checkbox next to each user for whom you want to change the Class of Service. 2. Click Change Class of Service.
3. In the Class of Service drop-down box, select the new class of service. 4. Click Yes.
Reprovision Selected Users

To reprovision users or a group of users: 1. On the Licensed User Management screen, click the checkbox next to each user or user group that you want to reprovision. 2. Click Reprovision Selected Users.
3. Click Yes. The Avaya one-X Mobile Server retrieves the new user information and updates the Avaya one-X Mobile Server database.
December 2008
127
Unlicense Selected Users

Unlicensed users are not able to log in to their Avaya one-X Mobile account from either the Avaya one-X Mobile Web site or their mobile device. To unlicense a user: 1. On the Licensed User Management screen, click the checkbox next to the user you want to unlicense. 2. Click Unlicense Selected Users. This will increment the number of licenses available for assignment.
!
Important:
Important: When you remove a license from a user, remember to move the user back into a Partition which is not managed by the Avaya one-X Mobile Server. This will prevent the Avaya one-X Mobile Server from managing the call.
Delete Selected Users

Deleting a user will delete all the call logs and any other data associated with that user in the Avaya one-X Mobile database. The user will not be able to login to their Avaya one-X Mobile account from either the Avaya one-X Mobile Web site or their mobile device. To delete a user: 1. On the Licensed User Management screen, click the checkbox next to the user(s) you want to delete. 2. Click Delete Selected Users. This will decrement the number of used licenses and remove the user from the Avaya one-X Mobile Server database. It will not remove the user from the LDAP directory.
128
December 2008
Administer Users
View User Details

Click on Details next to any user on the Licensed User Management or Unlicensed User Management screens to display more information about that user.
From the User Details screen you can:

Reprovision a user Delete a user Take action on a users account if the user has lost their mobile phone Take action on a users account if the user is no longer an employee Unlock a locked user account Configure a user as virtual
Lost or Stolen Mobile Phone

If a users mobile phone has been lost or stolen, click on Lost or Stolen Mobile on the User Details screen. This screen will provide instructions for further steps you should take. This may include resetting the users password and loss of local data on their mobile phone.
December 2008
129
No Longer an Employee
If a user is no longer an employee, click on No Longer an Employee on the User Details screen. This screen will provide further instructions depending on whether the user account needs to be retained or completely removed from the Avaya one-X Mobile Database.
Unlock one-X Mobile Account

A user account may get locked out by the Avaya one-X Mobile Server if the user enters an incorrect login too many times. This will prevent a user from logging into the Avaya one-X Mobile application on both their mobile phone and the Avaya one-X Mobile Web site. A user account that is locked will automatically be unlocked after the lockout time (as set in the Class of Service for the user) has expired. If a user account needs to be unlocked before the lockout time expires, click on Unlock one-X Mobile Account on the User Details screen. This will unlock the user account, and access to the Avaya one-X Mobile Web site and the Avaya one-X Mobile application on their mobile phone will be allowed. Note: This does not unlock a users voicemail mailbox.
Note:
Configure a User as Virtual

Avaya one-X Mobile provides support for virtual extensions which allows users who do not have a physical desk phone or Softphone to make and receive calls using the Avaya one-X Mobile application. To configure a user as virtual: 1. Click on This user is virtual on the User Details screen. 2. Specify the Virtual End Point CTI port for this user. Note: It is important that the correct CTI port is specified. See Configure CTI Links in Avaya Communication Manager on page 21 for more information. 3. Click Save.
Note:
Configure Dial Plans

The Dial Plans section shows how the dial plans are configured. Dial Plan settings tell the Avaya one-X Mobile Server how to send calls. For Avaya Setup, this is based on the Class of Service. For Cisco Setup, this is based on the Calling Search Base. For international support, the phone numbers in LDAP must have a format that includes the country code.
130
December 2008
To configure Dial Plans: 1. Select Avaya Setup > Dial Plans.
2. In the Country Code box, enter the country code of the country where the office phone system (PBX) is located. Note: The only configuration currently supported is one where all PBXs have the same country code. 3. In the IDD box, enter the International Direct Dialing (IDD) prefix of the office phone system (PBX) where the extension is managed. Note: This value must be provided to the managed users in order for them to dial an international number using the appropriate IDD. 4. In the National Direct Dialing Prefix box, enter the appropriate NDD prefix. The NDD prefix is the access code used to make a call within a particular country from one city to another. When calling from one city to another in the same vicinity, an NDD prefix may not be necessary. The NDD prefix is followed by the city/area code for the place you are calling. Phone numbers are often written in the format +44-(0)1224-XXXX-XXXX. This represents the numbers used for both international and national long-distance calls. In this example, +44 is the country code and (0) indicates the NDD. When dialing from outside the country, the NDD would not be used after dialing the country code; when dialing from within that country, the NDD would be used, but the country code would not.
Note:
Note:
December 2008
131
5. In the National Number Length box, enter the appropriate National Number Length. For any country, the National Number Length is the total number of digits you dial to make up a complete phone number. For example, in the USA, to dial the number 408-XXX-XXXX, the National Number Length would be 10. 6. Click Save to save the PBX settings. In the Dial Plans section of the screen, you can view the dial plan rules that are applied to each switch hostname. These rules are applied for national and local numbers. There is a default set of rules. The default settings are appropriate for the United States. Verify the settings are accurate for the installed system. Additional rules can be configured if necessary. For example, if an enterprise has phone numbers set up as seven digits in order to take advantage of toll savings, you would configure the dial plan to dial seven digits instead of ten (the default). For phone systems in other countries, you may want to redefine the default settings completely. 7. To configure additional rules, click Edit next to the appropriate switch hostname.
8. Edit the information as appropriate. 9. Click Save Changes.
Add a New Dial Plan

To add a new Dial Plan: 1. Select Avaya Setup > Dial Plans.
132
December 2008
2. Click Add New Dial Plan.
3. In the Switch Hostname drop-down box, select the appropriate switch hostname. 4. In the Matching Pattern box, enter the prefix or matching pattern to be identified, as follows:

Enter ALL if you want to match on any numeric pattern. Enter the specific pattern if you want to match on that pattern. For example, if you want to set up a rule for dialing phone numbers beginning with 510, you would enter 510 in this box.
5. In the Number Length box, enter the length of the number for which the rule applies. For example, if you want the rule to apply only to numbers that begin with 510 and are 10 digits in length, you would enter 10 in this box. 6. In the Strip Digits box, enter the number of digits to delete from the beginning of the number. 7. In the Add Prefix box, enter the prefix to add to the number. 8. Click Save.
December 2008
133
134
December 2008
Chapter 7: Serviceability
The Serviceability section of the Avaya one-X Mobile administrative interface allows monitoring and management of services, and provides information about Avaya one-X Mobile Server components and allows fine tuning of these components.
View Control Center

To view the Control Center, select Serviceability > Control Center.
Control Center allows you to stop, start, and monitor services controlled by the Avaya one-X Mobile Server. All components show whether they are installed or not.
December 2008
135
View Route Points

To view Route Points, select Serviceability > Route Points.
Route Points lists the status of Route Points used in the Cisco Setup.
View Trace Components

To view Trace Components, select Serviceability > Trace Components.
Trace Components allow you to manipulate the data stored in logs. The default setting on each field on this page is to debug. This provides the most information and will also allow you to troubleshoot more thoroughly.
136
December 2008
View Component Info
View Component Info

To view Component Info, select Serviceability > Component Info.
Component Info provides information about various components such as version numbers and last known status.
December 2008
137
138
December 2008
Chapter 8: Licenses
The Licenses section of the Avaya one-X Mobile administrative interface displays the most current information about licenses being used, licenses available, and licenses acquired.
View License Information

To view License Information: 1. Select Licenses > License Information.
2. In the WebLM Hostname URL field, enter the hostname of the WebLM server to get accurate information about licenses. There are 3 Application Modes in which WebLM will operate:
Grace allows users to be licensed for a trial period of 30 days. The number of grace days remaining will be displayed on the License Information page if the server is in Grace mode. Normal indicates that WebLM is functioning normally. Restricted indicates the Grace period has expired and users cannot log in to their accounts.
December 2008
139
Chapter 8: Licenses
140
December 2008
Chapter 9: Carrier Offset

The Carrier Offset section of the Avaya one-X Mobile administrative interface allows you to control the amount of time between when a call reaches the carrier network and is answered by the carriers voicemail system. This allows the Avaya one-X Mobile Server to redirect a call that was answered by carrier voicemail to the Enterprise voicemail platform. For example, if a user has their call handling settings set to To Mobile, a CTI port makes an outbound call to the mobile phone. If the call is answered in less than the carrier offset seconds, the call is diverted to Cisco Unity or Modular Messaging voicemail.
Set Carrier Offset Settings

To set the Carrier Offset Settings for a particular carrier: 1. Select Carrier Offset > Carrier Offset Settings.
Note:
Note: The Carrier Offset Setting is set on a per-wireless carrier basis because some networks are much faster than others. 2. In the appropriate carrier field, enter the offset in milliseconds. A value of 100 milliseconds means that if a call to a mobile phone is answered in less than 100 milliseconds, the Avaya one-X Mobile Server will redirect the incoming call into Cisco Unity Voicemail. 3. Click the Save Changes.
December 2008
141
Chapter 9: Carrier Offset
142
December 2008
Chapter 10: Direct Call PBX Numbers

The Direct Call PBX Numbers section of the Avaya one-X Mobile administrative interface allows numbers that are not managed by Avaya one-X Mobile to use the Avaya one-X Mobile callback and simulring features. You are able to configure mapping rules to numbers that are extensions on the PBX but not managed by Avaya one-X Mobile. To configure mapping rules for PBX numbers: 1. Select Direct Call PBX Numbers.
2. Click New Direct Call PBX Number.
3. In the Switch Hostname drop-down box, select the appropriate host name. 4. In the Leading String field, enter the extension number (or wild cards) that represents the set of extensions. 5. In the Digit Count field, enter the number of digits in the extension or set of extensions. 6. Click Save.
December 2008
143
Chapter 10: Direct Call PBX Numbers
144
December 2008
Chapter 11: Cisco Setup

The Cisco Setup section of the Avaya one-X Mobile administrative interface allows you to set up the Avaya one-X Mobile Server for systems that use Cisco CallManager. Perform the Cisco setup tasks in the following order: 1. Configure Cisco CallManager settings. 2. Set up Profiles: a. Create a Provisioning Profile. b. Create a Voicemail Profile. c. Create a Corporate Directory Profile. d. Create a Class of Service. 3. Create CTI Ports. 4. Set up Route Points: a. Import Route Points. b. Manage Route Points. 5. Administer Users: a. Import Users. b. Manage Unlicensed Users. c. Manage Licensed Users. 6. Configure Dial Plans.
Configure Cisco CallManager Settings

Cisco CallManager Settings enables you to configure the Avaya one-X Mobile Server with the location and administrative information related to the various servers with which the Avaya one-X Mobile Server communicates. The Cisco CallManager Settings that must be configured are:
AXL Settings enables the Avaya one-X Mobile Server to communicate with the Cisco AXL interface on the CallManager. This is required to provision other user functions on the Avaya one-X Mobile Server.
December 2008
145
LDAP Settings enables configuration of the location of the Cisco CallManager LDAP directory. The Avaya one-X Mobile Server requires access to the LDAP server to enable end user logins and corporate directory searches. JTAPI Settings enables the configuration of the Cisco CallManager JTAPI authentication credentials. JTAPI is the protocol used by the Avaya one-X Mobile Server to communicate with Cisco CallManager for call handling services.
To configure Cisco CallManager Settings: 1. Select Cisco Setup > Cisco CallManager Settings.
2. In the AXL Hostname field, enter the Cisco AXL hostname. This should be the IP address of a published Cisco CallManager (for example, 192.168.98.6). 3. In the AXL Port field, enter the Cisco AXL port number (for example, 80). This port is the port on which Cisco AXL services run. By default this is set to port 80 during Cisco CallManager installation. 4. In the AXL Username field, enter the Cisco AXL username. This is the username used to access AXL (for example, administrator).
146
December 2008
Configure Cisco CallManager Settings
5. In the AXL Password field, enter the Cisco AXL password. Asterisks appear in the field for security purposes.
The Cisco CallManager LDAP structure has two main trees which it needs to access. The first is the User Base Distinguished Name (DN) and the second is the Cisco Configuration Base DN. All Cisco CallManager users are stored under the User Base DN. Specific profile information about users is stored under the Cisco Configuration Base DN. When the Avaya one-X Mobile Server performs corporate directory lookups or logins, the search is initiated from the User Base DN. The common name (CN) for Cisco CallManager users contains pointers to the Cisco Configuration Base DN where all the CallManager specific information is kept. Cisco CallManager hosts its own LDAP DC Directory. If you have integrated Cisco CallManager LDAP with Active Directory, then the fields in the LDAP Settings section should point to Active Directory instead of Cisco CallManager LDAP. 6. In the LDAP User DN field, enter the LDAP user DN (for example, cn=Directory Manager, o=cisco.com). If you have not integrated Active Directory with Cisco CallManager, then this User DN is the default that was created when you installed Cisco CallManager. The default name for the Directory Manager account is Directory Manager. 7. In the LDAP Hostname field, enter the LDAP host IP address (for example, 193.148.88.5). If Active Directory has been integrated, then this will be the IP address of Active Directory; otherwise, it should be the IP address of Cisco CallManager. 8. In the LDAP Port Number field, enter the number of the LDAP port. The default value for Cisco CallManager DC Directory LDAP is 8404. If Active Directory and Cisco CallManager have been integrated, then the default value for Active Directory is 389. 9. In the LDAP Password field, enter the LDAP Password. Asterisks appear in the field for security purposes. 10. In the Cisco Configuration Base DN field, enter the Cisco Configuration Base DN (for example, ou=CCN, o=cisco.com). The value given in the example is the default set when Cisco CallManager is installed. If Active Directory has been integrated, then this value was set during the integration of Active Directory and Cisco CallManager.
December 2008
147
11. In the Cisco Base DN field, enter the Cisco User Base DN (for example, ou=Users, o=cisco.com). The example is the default set when Cisco CallManager is installed. If Active Directory has been integrated, then this value was set during the integration of Active Directory and Cisco CallManager.
12. In the CallManager Cluster Node IP Addresses field, enter the Cisco CallManager IP addresses or hostnames.
!
Important:
Important: If you have a clustered environment, be sure to enter a comma-separated list which includes each node in the cluster.
13. In the JTAPI Username field, enter the JTAPI username you created (for example, jtapiuser). 14. In the JTAPI Password field, enter the JTAPI password for the JTAPI user. Asterisks appear in the field for security purposes. 15. If you have taken steps to integrate Cisco CallManager LDAP with Microsoft Active Directory, click the checkbox for Cisco CallManager is integrated with Microsoft Active Directory. 16. Click Save Changes. 17. To check for Jtapi updates, click Check for Jtapi Updates. Be sure to click this link when the Cisco CallManager version has been updated to keep the Avaya one-X Mobile Server application in sync with Cisco CallManager.
148
December 2008

The Provisioning Profile task imports the users from the Active Directory and is used for two purposes:
To indicate the source of user accounts that will be imported into the Avaya one-X Mobile database. To indicate the source for user account authentication.
Avaya one-X Mobile is capable of using LDAP v3 directories for the Provisioning Profile. To create a new Provisioning Profile: 1. Select Cisco Setup > Setup Profiles > Provisioning Profile.
2. Click New Provisioning Profile.
December 2008
149
3. In the Profile Name field, enter the name of the new profile. 4. In the Description field, enter a description of the profile. 5. In the LDAP Search Type drop-down box, select the appropriate search type. This field defines the type of LDAP search based on the LDAP platform. A specific search routine is provided for Active Directory, SunOne, and Netscape_iPlanet. In addition, a generic search routine is provided that is platform independent. Choosing the appropriate platform will provide better search performance. 6. In the LDAP User DN field, enter the LDAP user DN (for example, cn=administrator, ou=users, dc=example, dc=com). This is the user that will be used to search the directory for Avaya one-X Mobile users. 7. In the LDAP Hostname field, enter the LDAP hostname. 8. In the LDAP Port Number field, enter the LDAP port. The default value for Microsoft Active Directory is 389. 9. In the LDAP Password field, enter the password for this user. Asterisks appear in the field for security purposes. 10. In the LDAP Base DN field, enter the search base DN (for example, ou=users, dc=example, dc=com). 11. To view LDAP Attributes fields, click Show Advanced Settings.
12. In the Extension field, enter the attribute name used to hold the extension. If the extension is not housed in the directory, it may be derived as part of the import process. 13. In the 10 Digit Phone Number field, enter the attribute name for phone number. 14. In the Handle or UserID field, enter the attribute name user ID. This should be capitalized and will be the same as what was entered in the LDAP Attributes section of the Provisioning Profile tab in the Setup Profile section. 15. In the First Name field, enter the name users first name. 16. In the Last Name field, enter the attribute name for the users last name. 17. In the Email field, enter the attribute name for the users email address.
150
December 2008
18. In the Department field, enter the attribute name for the users department. 19. Click Save to save the Provisioning Profile settings. Note: If an entry was not configured correctly, an error message appears. Red text indicates the section(s) that contain errors.
Note:
Copy a Provisioning Profile

You can create a new Provisioning Profile by copying an existing profile, and changing the settings as appropriate. To create a new Provisioning Profile by copying an existing Provisioning Profile: 1. Select Cisco Setup > Setup Profiles > Provisioning Profile. 2. Click Copy Profile next to the profile to be copied. The New Provisioning Profile screen appears. 3. In the Profile Name field, rename the profile. 4. Change information in the other fields as appropriate. 5. Click Save.

In order to provide the Cisco CallConnect client Visual Voicemail feature, the Avaya one-X Mobile Server must integrate with Unity or Unity Connections. This integration is known as a Voicemail Profile and may later be applied to a Class of Service which can be applied to a user group.
December 2008
151
To create a new Voicemail Profile: 1. Select Cisco Setup > Setup Profiles > Voicemail Profile.
2. Click New Voicemail Profile.
3. In the Profile Name field, enter a profile name. Note that this is the name that is used when specifying a voicemail profile for a Class of Service. 4. In the Profile Type drop-down menu, select either Unity or Unity Connections, depending on your network configuration. 5. In the Voicemail Pilot Number field, enter the Voicemail pilot number. Note that this will only be used if the Avaya one-X Mobile Server is unable to provision the pilot number directly via the AXL interface. 6. In the Unity Connection IP Address field, enter the appropriate IP address.
152
December 2008
Note:
Note: The Unity Connection IP Address field appears only if you selected Unity Connection as the Profile Type.
The Avaya one-X Mobile Server must be a member of a domain that is trusted by the Microsoft Exchange server(s) where Cisco Unity or Unity Connections deposits voicemail. The Microsoft Active Directory Server section enables the configuration of the location and authentication credentials of the Active Directory associated with the Microsoft Exchange Server. Access to Active Directory is required by the Avaya one-X Mobile Server for the following tasks:

To accurately map received voice messages with the person that left the message. To retrieve configuration information such as the hostname of the Microsoft Exchange Server for a particular user. To retrieve the Microsoft Exchange Alias of a particular user.
7. In the Active Directory IP Address field, enter the Active Directory IP address or hostname (for example, 192.168.20.7). 8. In the Active Directory Port Number, enter the Active Directory LDAP port number. In Active Directory deployments, port 389 is the default LDAP port. 9. In the Administrator User DN field, enter the Active Directory administrator user DN (for example, cn=administrator, cn=users, dc=example, dc=com). 10. In the Administrator Password field, enter the Active Directory administrator password. Asterisks appear for security purposes when the password is entered.
December 2008
153
11. In the User Base DN field, enter the Active Directory user base DN (for example, cn=users, dc=example, dc=com). This should be the base DN where all users of Cisco Unity are stored.
The Exchange Administrative User Setting section enables the configuration of the location and authentication credentials of the Exchange Server. Access to the Exchange Server is required by the Avaya one-X Mobile Server to provide Visual Voicemail functionality. You must enter the authentication credentials of the Exchange Administrator User so that the Avaya one-X Mobile Server can access voicemail for any user. 12. In the Exchange Username field, enter the username for the Exchange Administrative User you wish to use for Visual Voicemail to access end user messages. Note that the domain name must be included here for Visual Voicemail to work correctly (for example, mydomain/administrator). This user should be a member of the Domain Administrators group. Additionally, the user must have permissions to log on as a Service locally on the Avaya one-X Mobile Server. See Ensure the Exchange Administrative User has Sufficient Permissions on page 155 for more information. 13. In the Exchange Password field, enter the Exchange Administrative User password. Asterisks appear in the field for security purposes. 14. Setup the Win32 Service Logon Rights: a. Go to Start > Control Panel > Administrative Tools. b. Double-click on the Services control panel element. c. Locate the Edge MapiMgr Service in the list. d. Open the properties of the service. e. Click on the LogOn tab. f. Click on the This Account radio button. g. Enter the fully qualified username and password. h. Click OK and start the service. 15. Click Save to save the Voicemail Profile settings.
154
December 2008
Note:
Note: If your settings are configured correctly, a Test Successful message appears following each setup area. If an entry was not configured correctly, an error message appears. Red text indicates the section(s) that contain errors. Sections which tested correctly will have green text indicating that the test for that section was successful.
Copy a Voicemail Profile

You can create a new Voicemail Profile by copying an existing profile, and changing the settings as appropriate. To create a new Voicemail Profile by copying an existing Voicemail Profile: 1. Select Cisco Setup > Setup Profiles > Voicemail Profile. 2. Click Copy Profile next to the profile to be copied. The New Voicemail Profile screen appears. 3. In the Profile Name field, rename the profile. 4. Change information in the other fields as appropriate. 5. Click Save.
Edit a Voicemail Profile

To edit a Voicemail Profile: 1. Select Cisco Setup > Setup Profiles > Voicemail Profile. 2. Click Edit Profile next to the profile you want to edit. 3. Edit the appropriate fields. 4. Click Save.
Ensure the Exchange Administrative User has Sufficient Permissions

The designated Exchange Administrative User must have permissions to log on locally and be able to manage the end user mailbox. 1. To ensure the Exchange Administrative User has permissions to log on locally: a. Go to Start > Run on the Avaya one-X Mobile Server.
December 2008
155
b. In the Open field, enter secpol.msc. c. Double click Local Policies. d. Click on User Rights Assignment. e. On the right panel double click Log on as Service. f. Click the Add button. g. In the Look in: drop-down box, choose the domain of the administrative user. h. In the Name list box, locate the administrative user. i. Double-click on the user name. This should add the user to the bottom section of the dialog box. j. Click OK. You should see the user name and the domain name in the Local Setting column. k. Close the Local Security Settings window. 2. To ensure the designated Exchange Administrative User has sufficient permissions to manage the end user mailbox: a. Go to the Domain controller for the specified domain that the Administrative user is a member of. b. Go to Start > Programs > Administrative Tools > Active Directory Users and Computers to bring up the Management Console. c. Click on View > Advanced Features. d. Expand the tree control for the specified domain of the Administrative user. e. Click on Users. f. Locate the user in the right-hand pane. g. Right click on the designated user and click on Properties. h. Locate the group in which the user is a member. i. In the Permissions frame, check all the listed permissions as allow except Full Control. Full Control should have neither allow nor deny checked. j. Click Apply if changes are required. k. Click OK to exit the property page. l. Exit out of the Management Console.
156
December 2008

In order to provide the Cisco CallConnect client Corporate Directory Lookup feature, the Avaya one-X Mobile Server must integrate with a Directory Source such as Cisco CallManager or Active Directory. This integration is known as a Corporate Directory Profile and may later be applied to a Class of Service which can be applied to a user group. To create a Corporate Directory Profile: 1. Select Avaya Setup > Setup Profiles > Corporate Directory Profile.
2. Click New Corporate Directory Profile.
3. In the Profile Name field, choose a unique profile name which will identify this profile. Note: This is the name that is used when specifying a corporate directory profile for a Class of Service. 4. In the Description field, enter a description of this profile. 5. In the Profile Type drop-down box, select one of the following:
Note:
December 2008
157
Select LDAP. The LDAP Settings section appears.
a. In the LDAP Search Type drop-down box, select the LDAP search type. This field defines the type of LDAP search based on the LDAP platform. A specific search routine is provided for Active Directory, SunOne, and Netscape_iPlanet. In addition, a generic search routine is provided that is platform independent. Choosing the appropriate platform will provide better search performance. b. In the LDAP User DN field, enter the LDAP user DN (for example, cn=Directory Manager, o=cisco.com, dc=example, dc=com). c. In the LDAP Hostname field, enter the LDAP hostname. d. In the LDAP Port Number field, enter the LDAP port number. The default value for Cisco CallManager DC Directory LDAP is 8404. If you are pointing the corporate directory search to Active Directory the default value for Active Directory is 389. e. In the LDAP Password field, enter the LDAP password. f. In the Corporate Directory Search Base DN field, enter the corporate directory search base DN (for example, ou=users, o=cisco.com). This is the default value for Cisco CallManager. The Avaya one-X Mobile Server will pull users under this root when searching the corporate directory.
Select AXL (for Cisco CallManager 5.0 and above) The AXL Settings section appears.
a. In the AXL Hostname field, enter the AXL hostname. b. In the AXL Port Number field, enter the AXL port number. c. In the Administrator Username field, enter the appropriate username. d. In the Administrator Password field, enter the password.
158
December 2008
6. Click Show Advanced Settings to view the LDAP Attributes section.
7. In the User LDAP Filter field, enter the appropriate filter. This field provides for an LDAP search filter specification used to build the Corporate Directory. 8. In the Extension field, enter the attribute name used to hold the extension. If the extension is not housed in the directory, it may be derived as part of the import process. 9. In the 10 Digit Phone Number field, enter the attribute name for phone number. 10. In the Handle or UserID field, enter the attribute name user ID. This should be capitalized and will be the same as what was entered in the LDAP Attributes section of the Provisioning Profile tab in the Setup Profile section. 11. In the First Name field, enter the attribute name for the users first name. 12. In the Last Name field, enter the attribute name for the users last name. 13. In the Email field, enter the attribute name for the users email address. 14. In the Department field, enter the attribute name for the users department address. 15. Click Save to save the Corporate Directory Profile settings.
Copy a Corporate Directory Profile

You can create a new Corporate Directory Profile by copying an existing profile, and changing the desired settings. To create a new Corporate Directory Profile by copying an existing Corporate Directory Profile: 1. Select Cisco Setup > Setup Profiles > Corporate Directory Profile. 2. Click Copy Profile next to the profile to be copied. The New Corporate Directory Profile screen appears. 3. In the Profile Name field, rename the profile.
December 2008
159
4. Change information in the other fields as appropriate. 5. Click Save.
Edit a Corporate Directory Profile

To edit a Corporate Directory Profile: 1. Select Cisco Setup > Setup Profiles > Corporate Directory Profile. 2. Click Edit Profile next to the profile you want to edit. 3. Edit the appropriate fields. 4. Click Save.

After completing the profiles, a Class of Service is required. Class of Service is a representation of ways in which an Avaya one-X Mobile user will interact with the system. Class of Service settings include profiles (as described earlier in this chapter) as well as non-aggregated settings. Note: A valid Provisioning Profile is required to create a Class of Service. An error message appears if there is an attempt to create a Class of Service using an invalid Provisioning Profile. 1. Select Cisco Setup > Setup Profiles > Class of Service.
Note:
To create a new Class of Service:
160
December 2008
2. Click New Class of Service.
3. In the Class of Service Name field, enter the name for this class of service. 4. In the Description field, enter a description of this class of service. 5. In the Provisioning Profile drop-down box, select the appropriate profile. 6. In the Voicemail Profile drop-down box, select the appropriate profile. 7. In the Corporate Directory Profile drop-down box, select the appropriate profile.
8. Click the checkbox to Allow voicemail to be stored on the mobile device. Note: Do not click this checkbox if you want to disable voicemail download to the Avaya one-X Mobile Web portal or Avaya one-X Mobile client. When the voicemail download feature is disabled, the user will not be able to download or save voicemail on the client, or download, save, or forward voicemail from the Web portal. If voicemail download is disabled, to listen to voicemail from the Web portal or client, the user will call corporate voicemail directly. 9. Click the checkbox to Allow voicemail to be forwarded via email. Note: Do not click this checkbox if you want to disable the forward via email feature available on Avaya one-X Mobile Web portal. 10. Click the checkbox to Require login each time one-X Mobile is launched on mobile device, if required.
Note:
Note:
December 2008
161
11. Set the Maximum number of attempts before user is locked out (default is 5). 12. Set the Time period for which a user is locked out in minutes (default is 90). 13. Click the checkbox to Require CallManager PIN reset upon reprovisioning.
14. Set the Maximum number of phones to Send Calls to. 15. Set the PSTN Prefix (which is the number necessary to dial to reach an outside line). 16. Click the checkbox to Allow International Dialing, if required. 17. Click the checkbox to Translate 10-digit numbers to extensions, if required.
18. Click the checkbox to Require client software upgrades, if required. 19. Set the Number of days to warn users before making updates mandatory. 20. In the RIM Blackberry Connection Settings drop-down box, select the appropriate setting.
162
December 2008
21. Click the checkbox for This organization uses Forced Authorization Codes (FACs), if applicable.
22. In the CMC Usage drop-down box, select the appropriate usage. 23. In the User Interface Language drop-down box, select the appropriate language. 24. In the End user website server URL field, enter the appropriate URL. 25. If this is a secure server, click the checkbox to set this as a secure server. 26. To view the LDAP Attribute Source Profiles section, click Show Advanced Settings.
December 2008
163
In the LDAP Attribute Source Profiles section, there is an opportunity to fine tune the Avaya one-X Mobile Server to use different directory sources for different data fields collected from directories. In some enterprise deployments, one directory may contain some information such as first name, last name; while another may contain information such as the 10-digit phone number. The Avaya one-X Mobile Server can map from one directory to another; where the sources are the Corporate Directory Profile and the Provisioning Profile. The Provisioning Profile will always be used for authentication and the Corporate Directory Profile may be used for name resolution. In all cases, the Handle or UserID must be the key between the two directory sources. That is, if mapping is done, the UserID in one directory must match that of the other directory. Use the drop-down boxes to tell the Avaya one-X Mobile Server from what directory to source the different attributes. 27. In the Handle or UserID drop-down box, select the appropriate profile. 28. In the 10 Digit Phone Number drop-down box, select the appropriate profile. 29. In the First Name drop-down box, select the appropriate profile. 30. In the Last Name drop-down box, select the appropriate profile. 31. In the Email drop-down box, select the appropriate profile. 32. In the Department drop-down box, select the appropriate profile. 33. In the Determine Extension from drop-down box, select the appropriate source. Note: For the Determine Extension from drop-down box, extensions for users can be determined either directly from the LDAP attribute or manually from the 10-digit phone number. Manual determination can be done in one of two ways:

Note:
automatically determined automatically using dial plan rules algorithmically by entering the number of leading digits to strip from the 10-digit phone number and/or adding prefixed after the digits have been stripped
34. In the LDAP Extension Source drop-down box, select the appropriate profile. 35. Click Save.
164
December 2008
Create CTI Ports
Create CTI Ports

Different types of call handling settings require different CTI Ports usage schemes. The following table illustrates the number of CTI Ports used for a particular call handling setting. Call Handling Setting To Voicemail Ring office Ring office and PSTN phone Ring PSTN phone Ring two other PSTN phones Ring three other PSTN phones Ring four other PSTN phones Ring five other PSTN phones Ring four PSTN and office Ring other office phone CTI Ports Used Per Call 0 0 1 2 3 4 5 6 5 2
The Avaya one-X Server uses a pool of CTI Ports to make outbound calls. You should decide what scenarios from the above tables are the most commonly used and base the number of CTI ports you need to create on your expected user base usage patterns. Once you determine this, a busy hour calculation can help to determine the number of CTI Ports you need to create to support your enterprise. For example, if you expect to support 30 simultaneous incoming calls for 30 managed users, you should create a minimum of 30 CTI Ports and a maximum of 90 depending on the expected user usage patterns. If most users are set to Office with Simulring on, then a number closer to 30 would be sufficient. If most users choose to ring their mobile phone and one other PSTN phone, then a number closer to 90 would be more appropriate.
!
Important:
Important: If the Avaya one-X Mobile Server runs out of CTI Ports, all subsequent calls will be routed directly to the desk as in the Office setting.
December 2008
165
To create CTI Ports: 1. Select Cisco Setup > CTI Resources > CTI Ports.
2. Click Create New Directory Range. This screen allows you to specify the parameters for automated creation of CTI Ports for use by the Avaya one-X Mobile Server.
3. In the Directory Number Ranges fields, enter the range of CTI Ports to be added. Choose a range of numbers which does not conflict with any Route Patterns or Translation Patterns in the Cisco CallManager. Not doing so will lead to Interdigit timeouts. 4. In the Partition drop-down box, select a partition for the CTI Ports which has the following attributes:
It can be dialed from the Calling Search Space of the Transfer Route Point you created. It can be dialed by the Calling Search Space of the managed phones.
5. In the Calling Search Space drop-down box, select the Cisco CallManager Calling Search Space associated with the partition. The Calling Search Space for the CTI Ports should have the following attributes:
It should include at the top of the Calling Search Space, the partition you created for the Interceptor CTI Route Point. It should include a partition which has access to the Route Pattern which routes calls to the PSTN. Typically, this is a 9 @ Route Pattern.
166
December 2008
Import Route Points
It should include the partition that contains the Transfer Route Point.
1. In the Device Pool drop-down box, identify the Device Pool associated with the CTI Ports. 2. Click Create CTI Ports.
Import Route Points

Before proceeding with the Import Route Points task, be sure the following tasks have been performed:
At least one Transfer CTI Route Point and one or more Interceptor Route Points have been configured within Cisco CallManager. These tasks should have been performed prior to configuring the Avaya one-X Mobile Server. If they have not, you must perform them before proceeding. You must configure the Cisco CallManager Settings in order for the correct information to appear in the Import Route Points screen. If the Cisco CallManager Settings have not yet been configured, you must do so before proceeding. See Configure Cisco CallManager Settings on page 145 for more information.
To import route points: 1. Select Cisco Setup > Setup RoutePoints > Import RoutePoints.
The Import Route Points screen provides a list of all CTI Route Points configured within Cisco CallManager. 2. Click the checkbox for the CTI Route Point(s) on the list that you established as the Interceptor Route Points and Transfer Route Points in Create CTI Route Points for Intercepting Calls on page 69. Interceptor Route Points are used to intercept calls for users and apply the call handling settings of the user to the call. 3. Click Add to one-X Server Database to save the settings in the Avaya one-X Mobile Server.
December 2008
167
Manage Route Points

Once Route Points are imported, you can edit a Transfer CTI Route Point or Interceptor Route Point. You can also delete them from the Avaya one-X Mobile Server database. 1. Select Cisco Setup >Setup Route Points > Manage RoutePoints.
2. In the Default Transfer RoutePoint drop-down box, choose a route point. This is the route point that will be used as the Transfer Route Point in the event that there is no Transfer Route Point to match the particular CSS of a given user. 3. For each imported route point, denote the Route Point Type as either a Transfer Route Point (used to change CID and manage calling permissions) or Interceptor Route Point (used to intercept incoming calls).
!
Important:
Important: In order for call handling services to work correctly, you must specify at least one Transfer Route Point and at least one Interceptor Route Point.
168
December 2008
Administer Users
Administer Users
This section describes how to provision users for whom the Avaya one-X Mobile Server services will be available. This section describes how to:

Import Users Manage Unlicensed Users Manage Licensed Users
Import Users
To import users: 1. Select Cisco Setup > Users > Import Users.
The first time you navigate to the Import Users page, the list of users will be empty (as shown above). 2. Click Import Users to import the users from the CallManager LDAP (or Active Directory if the integration has been performed) into the Avaya one-X Mobile Server database. Note: For very large user populations, this can take some time. Users which appear in the Manage Users list are retrieved from the Cisco CallManager LDAP Directory (or Active Directory, if the integration has been performed). To search for all users use cn=*. When a large number of results are returned, you can use the alphabetical bar to navigate to a particular section of users beginning with that letter. The sort attribute is whatever attribute you are currently sorting on (that is, First, Last, Extension, or Department).
Note:
December 2008
169
Manage Unlicensed Users

To view all imported user accounts that are not yet licensed: 1. Select Cisco Setup > Users > Unlicensed User Management.
2. To search for specific users, enter text in the Search field. 3. To search for all users, leave the Search text box blank and press Enter or click Show All, if it is available. 4. To navigate to a particular section of users when a large number of results are returned, use the Sort by drop-down box.

Once users have been imported, they are all configured with the Default Class of Service. To change the Class of Service of a user group: 1. On the Unlicensed User Management screen, click the checkbox for the users for whom you want to change the Class of Service. 2. Click Change Class of Service. 3. In the Choose a Class of Service drop-down box, choose a Class of Service. 4. Click Save. The new Class of Service will be applied to all the selected users.
License Selected Users

To license a user: 1. On the Unlicensed User Management screen, click the checkbox next to the users name you want to license.
170
December 2008
Administer Users
2. Click License Selected Users. This will license the user in the Avaya one-X Mobile Server database and decrement the number of licenses available for assignment. A message appears letting you know that it is importing users in a background process. Licensing users can take some time depending on the size of your user base. When users are licensed, the Avaya one-X Mobile Server works in the background to retrieve required provisioning information for the user. When complete, you will be able to locate the new users in the Licensed User Management tab.
!
Important:
Important: The Avaya one-X Mobile Server associates a users device with the JTAPI user specified in the Setup screen. If you are licensing more than 1500 users, you must do this through the Cisco CallManager Administration User Interface as there are limitations on the size of AXL queries. Follow the same procedure as provided in section 6.3, Associating the JTAPI User with the Interceptor Route Points, of the Cisco CallManager Integration Guide. The only difference is that you will be associating the remaining CallConnect user devices with the JTAPI user instead of the CTI Route Points.
Manage Licensed Users

To view all imported user accounts that are licensed: 1. Select Cisco Setup > Users > Licensed User Management.
December 2008
171
2. To search for a user, in the Search field enter the users last name, first name, extension, Class of Service, or department. 3. To change the page displayed, in the Show drop-down box, select the appropriate page. 4. To change the way the information is sorted on the page, in the Sort by drop-down box, make the appropriate selection. To manage licensed users, the following features are available:

Change Class of Service Reprovision Selected Users Unlicense Selected Users Delete Selected Users

To change the Class of Service for a user or group of users: 1. On the Licensed User Management screen, click the checkbox next to each user for whom you want to change the Class of Service. 2. Click Change Class of Service. 3. In the Class of Service drop-down box, select the new class of service. 4. Click Yes.
Reprovision Selected Users

You may need to reprovision users when:

You are changing Voicemail Pilot numbers and it affects these users. You are changing Microsoft Exchange Server hostnames or IP addresses and it affects these users. You are changing Microsoft Exchange Server aliases used by Cisco Unity.
To reprovision users or a group of users: 1. On the Licensed User Management screen, click the checkbox next to each user or user group that you want to reprovision. 2. Click Reprovision Selected Users. The Avaya one-X Mobile Server retrieves the new user information and updates the Avaya one-X Mobile Server database.
172
December 2008
Administer Users
Unlicense Selected Users

Unlicensed users are not able to log in to their Avaya one-X Mobile account from either the Avaya one-X Mobile Web site or their mobile device. To unlicense a user: 1. On the Licensed User Management screen, click the checkbox next to the user you want to unlicense. 2. Click Unlicense Selected Users. This will increment the number of licenses available for assignment.
!
Important:
Important: When you remove a license from a user, remember to move the user back into a Partition which is not managed by the Avaya one-X Mobile Server. This will prevent the Avaya one-X Mobile Server from managing the call.
Delete Users
Deleting a user will delete all the call logs and any other data associated with that user in the Avaya one-X Mobile database. The user will not be able to login to their Avaya one-X Mobile account from either the Avaya one-X Mobile Web site or their mobile device. To delete a user: 1. On the Licensed User Management screen, click the checkbox next to the user(s) you want to delete. 2. Click Delete Selected Users. This will decrement the number of used licenses and remove the user from the Avaya one-X Mobile Server database. It will not remove the user from the LDAP directory.
December 2008
173
View User Details

Click on Details next to any user on the Licensed User Management or Unlicensed User Management screens to display more information about that user.
From the User Details screen you can:

Reprovision a user Delete a user Take action on a users account if the user has lost their mobile phone Take action on a users account if the user is no longer an employee Unlock a locked user account
Lost or Stolen Mobile Phone

If a users mobile phone has been lost or stolen, click on Lost or Stolen Mobile on the User Details screen. This screen will provide instructions for further steps you should take. This may include resetting the users password and loss of local data on their mobile phone.
No Longer an Employee
If a user is no longer an employee, click on No Longer an Employee on the User Details screen. This screen will provide further instructions depending on whether the user account needs to be retained or completely removed from the Avaya one-X Mobile Database.
174
December 2008
Unlock one-X Mobile Account

A user account may get locked out by the Avaya one-X Mobile Server if the user enters an incorrect login too many times. This will prevent a user from logging into the Avaya one-X Mobile application on both their mobile phone and the Avaya one-X Mobile Web site. A user account that is locked will automatically be unlocked after the lockout time (as set in the Class of Service for the user) has expired. If a user account needs to be unlocked before the lockout time expires, click on Unlock one-X Mobile Account on the User Details screen. This will unlock the user account, and access to the Avaya one-X Mobile Web site and the Avaya one-X Mobile application on their mobile phone will be allowed. Note: This does not unlock a users voicemail mailbox.
Note:

The Dial Plans section shows how the dial plans are configured. Dial Plan settings tell the Avaya one-X Mobile Server how to send calls. For Cisco Setup, this is based on the Calling Search Base. For Avaya Setup, this is based on the Class of Service. For international support, the phone numbers in LDAP must have a format that includes the country code. To configure Dial Plans: 1. Select Cisco Setup > Dial Plans.
2. In the Country Code box, enter the country code of where the office phone system (PBX) is located. Note: The only configuration currently supported is one where all PBXs have the same country code.
Note:
December 2008
175
3. In the IDD box, enter the International Direct Dialing (IDD) prefix of the office phone system (PBX) where the extension is managed. Note: This value must be provided to the managed users in order for them to dial an international number using the appropriate IDD. 4. Click Save to save the PBX settings.
Note:
In the Dial Plans section of the screen, you can view the dial plan rules that are applied to each switch hostname. These rules are applied for national and local numbers. There is a default set of rules. The default settings are appropriate for the United States. Verify the settings are accurate for the installed system. Additional rules can be configured if necessary. For example, if an enterprise has phone numbers set up as seven digits in order to take advantage of toll savings, you would configure the dial plan to dial seven digits instead of ten (the default). For phone systems in other countries, you may want to redefine the default settings completely. 5. To configure additional rules, click Edit next to the appropriate switch hostname.
6. Edit the information as appropriate. 7. Click Save Changes.
176
December 2008
Add a New Dial Plan

To add a new Dial Plan: 1. Select Cisco Setup > Dial Plans. 2. Click Add New Dial Plan.
3. In the CSS drop-down box, select the appropriate CSS. 4. In the Matching Pattern box, enter the prefix to be identified in the number for which the rule applies. 5. In the Number Length box, enter the length of the number for which the rule applies. 6. In the Strip Digits box, enter the number of digits to delete from the beginning of the number. 7. In the Add Prefix box, enter the prefix to add to the number. 8. Click Save.
December 2008
177
178
December 2008
Appendix A: Log Cleaning Utility

This appendix provides the procedure to configure the Tomcat log cleaning utility so that it automatically runs on a specified schedule. This task is performed on the Windows server running the Avaya one-X Mobile Server software.
Schedule the Tomcat Log Cleaning Utility

To schedule the Tomcat log cleaning utility: 1. Select Start > Setting > Control Panel > Schedule Tasks.
December 2008
179
2. Double-click Add Scheduled Task.
3. Click Next.
180
December 2008
4. Browse to the folder <Edge installation folder>\Utilities, for example, C:\Edge\Utilities.
5. Open the file tnlogDeleter.exe.
December 2008
181
6. Select Daily.
7. Click Next.
182
December 2008
8. In the Start time: box, set the time to 12:30 AM, and then click Next.
9. Enter the user name and password. 10. Enter the password again to confirm, and then click Next.
11. Click Finish to close the Scheduled Task Wizard. The task will be performed at 12:30 AM, every day.
December 2008
183
184
December 2008

Avaya One X Mobile 1.1

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avaya One X Mobile 1.1

Uploaded by

Copyright:

Available Formats

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

18-602153 Issue 2 December 2008

Configure Integration with Avaya Application Enablement Services . . . . . . . . . . Validate Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Create the JTAPI user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

What You Need to Know

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Documentation

Acronym LDAP MAPI MSS SAC SAFE SMTP SSL

Avaya one-X Mobile Documentation

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Document Number 18-602903 18-602150 2 of 2

Other Product Documentation

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya one-X Mobile Overview

Whats New in this Release

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

MS Exchange Other Application Enablement Services (AES)

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Before You Begin

Before You Begin

SE Linux must be disabled AES license must be installed

Required Tasks for New Installations

Avaya Communication Manager

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Avaya Application Enablement Services

Avaya one-X Mobile Integration, Administration, and Maintenance Guide

Required Tasks for New Installations

See TR87 Configuration on page 47.

See SMS Configuration on page 49.

Avaya Modular Messaging

Avaya one-X Mobile Integration, Administration, and Maintenance Guide