Avaya one-X™ Mobile Pre-Installation Checklist

Avaya one-X™ Mobile
Pre-Installation Checklist
18-602133
Issue 1
November 2007
© 2007 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, Avaya’s 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.
Cisco is a registered trademark of Cisco Systems, Inc.
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 18002422121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://www.avaya.com/support.
Pre-Installation Checklist
Review this checklist and complete the tasks prior to the Avaya one-X™ Mobile Server installation date.
General Information
Company Name:
Address:
Main Contact:
Email:
Office Phone:
Cell Phone:
Technical Contact:
Email:
Office Phone:
Cell Phone:
Task
Pre-Installation Checklist
Task Completed By:
Date:
Customer Pre-Installation
Identify server racks for the Avaya one-X Mobile Server.
Note: The Avaya one-X Mobile Server requires the AES Server.
Install server(s) into rack and provide:
Power
Ethernet
Internal IP address
Ping connection from Avaya one-X Mobile internal server to AES, PBX switch and MSS servers.
Note: The internal Avaya one-X Mobile Server should be on the same subnet as the Exchange server if using Exchange as your message store.
Install Microsoft Windows Server 2003 (Standard or Enterprise edition) with Service Pack 2 or higher on the Avaya one-X Mobile Server and add Windows components of ASP.NET and IIS.
Note: If the customer purchases the Avaya hardware/software product, it comes with Windows Server 2003 Standard Edition. If the customer purchases their own hardware, they can select Standard or Enterprise.
Harden servers per corporate security standards.
Apply SSL certificate on outside server as required by corporate security standards.
Make sure the free space on the target drive is at least 6 GB and is not an even multiple of 4 GB. (This is a Microsoft Installer requirement.)
Note: For the AES server, follow the instructions in the AES Installation Guide.
If this is a dual server environment, complete the following tasks for the external server.
Identify an external IP address and set up the mapping from external to internal IP.
Validate that the IMAP service is running on Exchange Server if Exchange is used as message store.
Create a DNS mapping to the external IP address so handset users do not need to remember the IP address.
Note: There is a 30-character limit. Keep as short as possible for ease of use for the Avaya one-X Mobile users.
Do the following:
Open Port 80 or 443 to your external IP for Avaya one-X Mobile access.
Note: Port 443 is used if SSL is deployed. Customer is responsible for acquiring and maintaining SSL certificate. See Appendix C in the Avaya one-X Mobile Installation Guide, document number 18-602135, for instructions on securing SSL certification.
Open Port 8080 and 1433 between inside and outside servers.
Enable resolution to outside DNS from external server.
Provide terminal services access to the Avaya one-X Mobile Server open to the Avaya IP range for installation support and troubleshooting.
Note: If security limitations do not allow for this, establish VNC access as needed.
Do the following:
Join Avaya one-X Mobile internal server to the company domain.
Join external server to part of the work group.
Note: See “Create a Domain User” for additional information.
Create a domain user which is a member of the Domain Administrators group called Avaya one-X Mobile (or a similar name).
Note: See “Create a Domain User” for additional information.
Establish a trusted relationship between the Modular Messaging Server and the Avaya one-X Mobile Server. Make note of the server name and trusted server password established when configuring the application server.
Setup Information (Required For Installation Configuration)
Avaya Communication Manager
Gather administrative user name and password for:
Avaya Communication Manager
Modular Messaging
Impacted switches involved in the deployment
AES
Gather the following information:
LDAP User DN
Switch Configuration Base DN
Switch User Base DN
Gather the following switch Feature Access Codes for input to Avaya one-X Mobile Admin Configuration:
EC500 Enable Code
EC500 Disable Code
EC500 SAFE Code
SAC Enable Code
SAC Disable Code
All users should have EC500 Appearance removed from their desk phone. Avaya one-X Mobile manages this through the application.
Set EC500 mapping mode to termination.
Do the following:
Request EC500 set up.
Provide user mobile number for the EC500.
Note: Mapping mode is set to termination for EC500.
Avaya Communication Manager and AES Licenses Required
Avaya one-X Mobile requires additional licensing for Avaya Communication Manager and AES. This licensing is included in a material code when the product is ordered. Prior to configuring Avaya one-X Mobile, perform the following steps:
Validate that the following Avaya Communication Manager licenses exist:
FEAT_ADJLK
FEAT_BSCVEC
FEAT_PRTVEC
FEA_RCNAA_CFF
REGISTRATION IP_API_A*
FEAT_EC500
FEAT_XCOV_ADMIN
VALUE_OPT_EC500
Validate that the following AES licenses exist:
VALUE_CVLAN_VERSION
VALUE_AEC_CONNECTIONS
VALUE_TSAPI_VERSION
VALUE_AEC_VERSION
VALUE_NOTES
VALUE_TSAPI_USERS
Cisco® CallManager
Gather administrative user name and password for:
Cisco CallManager
Unity
Impacted switches involved in the deployment
Gather the following information:
LDAP User DN
Switch Configuration Base DN
Switch User Base DN
Directory
Gather the following information:
Microsoft Active Directory IP
Administration User DN
User Base DN
Administrator password
Gather the following information:
Microsoft Exchange username and password.
Add user to the admin group of the local machine.
SMTP Settings
Gather the following information:
SMTP username
SMTP password
IP address
IP port number
Corporate email address
Dial Plan Validation (local 10-digit numbers)
Provide a list of any Local NPA-NXXs that require 10-digit dialing without pre-pending a 1 to the dialed number. (Permissive Dialing).
Note: Configuration is required.
Test Extensions for Installation Team
Set up two test extensions for installation team testing. Support and submit IT request to add users. Then do the following:
Establish extension in switch.
For Avaya Communication Manager only, apply EC500 settings and set mapping mode to termination.
Establish test users in Active Directory for authentication. Note: Avaya one-X Mobile administrative user must be able to authenticate to this organizational unit.
Set up for Avaya one-X Mobile Users
Compile and list user names and extensions.
Identify the user’s:
Wireless carrier
Mobile numbers
Handset model
Handset manufacturer
Set up data plans and SMS with user’s wireless carrier.
Note: It is recommended that users subscribe to an unlimited data plan and SMS messaging with 200 text messages per month. An example of a data plan is Cingular - Media Net. An example of an unlimited text messaging plan is Text/Instant Messaging 200.)
Schedule users for a 30- to 60-minute training session on the morning following Avaya one-X Mobile Server installation.
1 of 6
Create a Domain User
Access to Microsoft 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 the Avaya one-X Mobile Application Suite to access voice messages from user mail boxes for this purpose.
To create a domain user:
In the Active Directory Users and Computer, create a domain user account in the domain where your Microsoft Exchange server resides.
NOTE:
If you have multiple Microsoft Exchange Servers, perform the following tasks on each Microsoft Exchange Server used by the Avaya one-X Mobile Application Suite.
In the Microsoft Exchange System Manager, assign the permissions to Domain User as follows:
Navigate to the Mailbox Store of the Microsoft Exchange Server.
Right click Mailbox Store and select Properties.
Select the Security tab.
Click the Add button and add the Domain User.
Assign the following permissions to the Domain User:
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, you can wait for the update period to pass (usually around 24 hours) when the permissions assigned to the Domain User read into the Microsoft Exchange Applications.
|