Avaya one-X Mobile Installation Guide · Avaya one-X™ Mobile Installation Guide November 2007 5...

Avaya one-X™ MobileInstallation Guide

18-602135Issue 1

November 2007

© 2007 Avaya Inc.All Rights Reserved.

NoticeWhile 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 number03-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 disclaimerAvaya 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 disclaimerAvaya 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.

WarrantyAvaya 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.

CopyrightExcept 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 supportAvaya 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.

http://www.avaya.com/support



http://www.avaya.com/support/

Avaya one-X™ Mobile Installation Guide November 2007 3

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Document Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2: Pre-Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Supported Backend Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8CTI Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Voicemail Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 3: Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9General Topology Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Topology One: Avaya one-X Mobile Server in the DMZ . . . . . . . . . . . . . . . . . . 10Topology Two: Avaya one-X Mobile Server in the Same Network as other Servers . . 11Topology Three: Avaya one-X Mobile in a Reverse Proxy Configuration . . . . . . . . 12

Benefits of the Reverse Proxy Configuration . . . . . . . . . . . . . . . . . . . . . 13Topology Four: Avaya one-X Mobile Server in a Split Server Configuration . . . . . . 14

Benefits of the Split Server Configuration . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 4: Avaya one-X Mobile Server Installation . . . . . . . . . . . . . . . . . . . . . . 17Single Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Split Server Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Common Screens for all Installation Types . . . . . . . . . . . . . . . . . . . . . . . . 24

License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Customer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Choose Destination Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Ready To Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Installation Wizard Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Contents

Contents

4 Avaya one-X™ Mobile Installation Guide November 2007

Appendix A: Pre-Installation Required Documents . . . . . . . . . . . . . . . . . . . . . . 29Avaya one-X Mobile Site Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Avaya one-X Mobile Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . 35Create a Domain User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Avaya one-X Mobile System Acceptance/Signoff . . . . . . . . . . . . . . . . . . . . . 44Avaya one-X Mobile Getting Started Checklist . . . . . . . . . . . . . . . . . . . . . . 47

Appendix B: Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Appendix C: SSL Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Task 1: Download the SSL Application. . . . . . . . . . . . . . . . . . . . . . . . . . . 55Task 2: Remove Existing Security Certificates . . . . . . . . . . . . . . . . . . . . . . 56Task 3: Get the AES SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Task 4: Get the MSS SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Task 5: Import the New Security Certificates . . . . . . . . . . . . . . . . . . . . . . . 59


Chapter 1: Introduction

About This GuideThe Avaya one-X™ Mobile Installation Guide describes the physical connections, networking, and integration with the call server. Included in this document are procedures to install the Avaya one-X Mobile application on the server.

Intended Audience This document is intended for personnel who install and administer the Avaya one-X Mobile Server.

Document OrganizationThe guide contains the following sections:

Chapter Description

Chapter 1: Introduction Provides an overview of this guide

Chapter 2: Pre-Installation Requirements

Describes the system requirements and the backend supported requirements

Chapter 3: Network Configuration Describes the Network Configuration and Topography options

Chapter 4: Avaya one-X Mobile Server Installation

Provides instructions to install the Avaya one-X Mobile Server software using the installation wizard

Appendix A: Pre-Installation Required Documents

Provides the documents that need to be completed by the customer and the personnel installing the server before installation begins

1 of 2

Chapter 1: Introduction


Customer Support The support number for the customer and installer of the Avaya one-X Mobile Server is: 1-800-242-2121

Information about Avaya Products can be obtained at the following URL: http://www.avaya.com/support

Appendix B: Related Documentation

Lists additional documents that relate to the installation of this product and the peripheral hardware

Appendix C: SSL Certification Provides instructions for securing the Secure Sockets Layer Certificate on the server

Chapter Description

2 of 2



System RequirementsBefore beginning installation, verify that all the following requirements are met. There are basic hardware and software requirements that need to be in place in order to install the Avaya one-X Mobile Server. Two documents located in Appendix A will assist in the installation preparation:

● The Avaya one-X Mobile Site Survey on page 30 should be completed by the customer to confirm system compatibility with the Avaya one-X Mobile Server product.

● The Avaya one-X Mobile Pre-Installation Checklist on page 35 should be completed by the Installation Personnel to confirm the requirements are in place.

Hardware RequirementsHardware requirements for the installation of the Avaya one-X Mobile Server are:

● S8500C for hardware option

● Server should have a minimum of 2GB RAM

● The free space on the target Drive should not be a multiple of 4GB

● 100MB Ethernet

● At least 40GB of disk space

Software RequirementsThe following items must be installed or configured before installation:

● Microsoft Windows 2003 Server Service Pack 1 or higher

● Windows components of IIS and ASP.NET

● Permission settings on IIS

● A time synchronization mechanism between the Avaya one-X Mobile Server and the voicemail platform



Supported Backend RequirementsThis section identifies the supported telephone communication systems, voicemail, directory, and CTI servers necessary for Avaya one-X Mobile functionality.

CTI Integration● Avaya Communications Manager 4.0

● Cisco® CallManager 4.1 and above

● Application Enablement Service (AES) 4.01

Voicemail Platforms● Modular Messaging with MSS backend

● Modular Messaging with Exchange backend

- 2000- 2003

● Cisco Unity 4.0

● Cisco Unity Connections

Directories● Active Directory

● Modular Messaging LDAP (resolution purposes only)


Chapter 3: Network Configuration

General Topology RecommendationsThe Avaya one-X Mobile Server makes connections to the following servers in the Enterprise:

● Avaya Communication Manager/Cisco CallManager

● Active Directory

● Microsoft Exchange

The Avaya one-X Mobile Server receives inbound connections from handsets from the internet. Typically, port 80 or port 443 is used for this.

In general, it is recommended that the Avaya one-X Mobile Server be located in close proximity to the Avaya Communication Manager/Cisco CallManager. This will help to reduce any network latency. In particular, it is recommended that they be located on the same VLAN to reduce routing requirements.

Depending on the configuration of your network, four different network topologies are possible:

1. Avaya one-X Mobile Server in the DMZ

2. Avaya one-X Mobile Server in the same network as other servers

3. Avaya one-X Mobile Server in a reverse proxy configuration

4. Avaya one-X Mobile Server in a split server configuration

These four topologies are further described in the following sections.



Topology One: Avaya one-X Mobile Server in the DMZThe following diagram illustrates a topology where the Avaya one-X Mobile Server is homed inside the DMZ. Typically, servers that are kept in the DMZ have inbound connections from the outside, and outbound connections to the inside on specific ports.

The following firewall modifications are necessary for this topology:

● Allow port 80 or 443 traffic inbound from any IP address to the Avaya one-X Mobile Server. Note that it is problematic to restrict access-list entries to certain IP ranges for wireless networks as these networks are constantly changing their IP address ranges.

● Allow outbound traffic from the Avaya one-X Mobile Server to the Avaya Communication Manager/Cisco CallManager Cluster Nodes. The required ports are as follows:

- Port 80 for AXL needs to be opened to every Node in the Avaya Communication Manager/Cisco CallManager cluster.

- Port 2748 for JTAPI needs to be opened to every Node in the Cisco CallManager cluster.

- Port 450 needs to be open to AES for JTAPI communication.

Topology Two: Avaya one-X Mobile Server in the Same Network as other Servers


- Port 8404 for Avaya Communication Manager/Cisco CallManager LDAP needs to be opened to every Node in the Communication Manager/Cisco CallManager cluster.

- Port 389 for Microsoft Active Directory needs to be opened to the Active Directory Server.

- Port 143 for IMAP needs to be opened to the Microsoft Exchange Servers which home Avaya one-X Mobile users.

- Port 135 needs to be opened to the Microsoft Exchange Servers which home Avaya one-X Mobile users. This allows the MAPI protocol to access the Exchange Servers.

- Additionally, users in the inside network should be able to reach the DMZ via HTTP. This is typically allowed by default on most firewalls.

Topology Two: Avaya one-X Mobile Server in the Same Network as other Servers

The following diagram illustrates a topology where the Avaya one-X Mobile Server is homed in the inside network and has unfettered access to the internal servers including Avaya Communication Manager/Cisco CallManager.



The only firewall modification necessary for this configuration is to allow port 80 or port 443 traffic to access the Avaya one-X Mobile Server from the outside. Note that it is problematic to restrict access-list entries to certain IP ranges for wireless networks as these networks are constantly changing their IP address ranges.

Topology Three: Avaya one-X Mobile in a Reverse Proxy Configuration

The following diagram illustrates a topology where a reverse proxy infrastructure is used to hide the location of the Avaya one-X Mobile Server and the internal network structure from exposure to the internet.

Topology Three: Avaya one-X Mobile in a Reverse Proxy Configuration


Benefits of the Reverse Proxy ConfigurationThe Reverse Proxy configuration provides the following security benefits:

● Only the external IP address of the Reverse Proxy is exposed to the Internet. Note that the DMZ address is still hidden.

● Using statically NAT’d addresses make it much more difficult for hackers to gather real information about the network.

● Reverse proxy infrastructure narrows the HTTP/HTTPS traffic origination to one server; the reverse proxy. Traffic can be monitored from one point.

● In order to hack into the internal network, a hacker will have to break through the following checkpoints:

- outside firewall interface- Reverse Proxy- DMZ firewall interface- Avaya one-X Mobile Server

● If the Reverse Proxy is compromised, the hacker can only gain access to servers on the DMZ.



Topology Four: Avaya one-X Mobile Server in a Split Server Configuration

The following diagram illustrates a topology where the Avaya one-X Mobile Server functionality is split across two servers to keep only the parts necessary in the DMZ.

The Avaya one-X Mobile Server Handset Component can be homed in the DMZ with port 80/443 access from the outside. The Avaya one-X Mobile Server is homed on the inside with LAN access to the Avaya Communication Manager/Cisco CallManager and other servers it needs to communicate with. Communication between the DMZ and the inside is limited to Port 8080 (Tomcat) and port 1433 (ODBC).

Topology Four: Avaya one-X Mobile Server in a Split Server Configuration


Benefits of the Split Server ConfigurationThe Split Server configuration provides the following advantages:

● Incoming traffic from handsets can be easily load balanced in the DMZ.

● Access to port 80 and 443 is limited to the DMZ only.

● Firewall modifications to the inside interface is limited to 8080 and 1433.

● Critical Call Control functionality still resides on the inside next to the Avaya Communication Manager/Cisco CallManager. This is important in load situations.

● VPN software may be installed on the Mobile Handset Components.

● In order to break into the network, a hacker would have to cross the following checkpoints:

- outside firewall interface- Avaya one-X Mobile handset component- DMZ interface on port 8080 and port 1433- Avaya one-X Mobile Server



Avaya one-X ™ Mobile Installation Guide November 2007 17


The Avaya one-X Mobile Server software can be installed by CD or downloaded from the network. Presently, remote installation is not supported. Before installing the Avaya one-X Mobile Server software, do the following:

● Review the Avaya one-X Mobile Getting Started Checklist on page 47.

● Know the IP address for the Internal Server.

● Know the IP address for the External Server.

Once the application is loaded on the computer, the installation wizard directs you through the installation process. The first screen that appears is the Welcome to the InstallShield Wizard for Avaya one-X Mobile, as shown below.


18 Avaya one-X ™ Mobile Installation Guide November 2007

1. Click the Next button to navigate to the next window.

A screen prompting you to select a Single Server or Split Server installation appears.

2. Do one of the following:

● For a single server installation, see Single Server Installation on page 18.

● For a split server installation, see Split Server Installation on page 19.

Single Server Installation

1. To install the software on one server, select Single Server Installation, and then click the Next button.

Split Server Installation


2. Complete the following screens provided by the installation wizard:

● License Agreement

● Customer Information

- User Name

- Company Name

● Choose Destination Location

● Ready to Install

See Common Screens for all Installation Types on page 24 for more information about these screens.




1. To install the software on two servers, select Split Server Installation, and then click the Next button.

The Select Server Type screen appears as shown below.

Note:Note: The Split Server installation requires that the External Server be installed before

the Internal Server.

2. Select External Server Installation, and then click the Next button.

A dialog box appears asking if you want to install the User Web on the External Server, as shown below.



3. Click the Yes button.

Note:Note: Installing the User Web on the External Server is optional.

The Internal Server Information dialog box appears as shown below.

4. Enter the IP Address of the Internal Server for the ODBC data source.

5. Click the Next button.

6. Continue with the installation and complete the following screens for the External Server:



- User Name

- Company Name






After you have completed these screens, the Select Server Type screen appears again as shown below.

7. Select Internal Server Installation, and then click the Next button.

A dialog box appears asking if you want to install the User Web on the Internal Server, as shown below.



8. Click the Yes button.

Note:Note: Installing the User Web on the Internal Server is optional.

The Internal Server Information dialog box appears as shown below.

9. Enter the Internal Server IP address as it appears to the External Server.

10. Click the Next button.

11. Continue with the installation and complete the following screens for the Internal Server:



- User Name

- Company Name






Common Screens for all Installation TypesThe following screens are used in both the Single Server and Split Server installations. For the Split Server installation, these screens are used once for the External Server, and again for the Internal Server.

License AgreementRead the License Agreement and then click the I accept the terms of the license agreement button. This button must be clicked in order to proceed with the installation.

Common Screens for all Installation Types


Customer InformationThe Customer Information screen requires the User Name and the Company Name.



Choose Destination LocationAvaya one-X Mobile will automatically be located in a folder on the C drive.

If a different location is preferred, click the Change button. Then Identify the folder where you want Avaya one-X Mobile stored on the hard drive.

Common Screens for all Installation Types


Ready To InstallWhen the installation settings are complete, click the Install button to begin the installation.

Upon completion of these entries, if the available disk space in the target drive is less than 6GB, a message window appears advising that at least 6GB is required for installation of this software and the installation will be aborted.

Once the Installation is started, a progress bar and progress message appears that identifies what is occurring in each stage of the installation.



Installation Wizard CompleteWhen installation is complete the following screen appears and prompts you to restart your computer:

A status bar appears to indicate the progress of the Installation.

● Single Server Installation takes 10 minutes to load and 6-7 minutes to install.

● Split Server installation takes approximately the same time.

● The installation continues for several minutes after clicking the Finish button.

The system will reboot. After the reboot, you are prompted to log in again. The installation wizard restarts by itself and finishes the installation.

Once the installation is complete, see the Avaya one-X Mobile™ Administration and Maintenance Guide, document number 18-602144, for information on how to administer and configure the Avaya one-X Mobile Server.



The documents that must be completed before installing the Avaya one-X Mobile Server are listed in the following table and provided in this appendix.

Document Title Document Number For Use By:

Avaya one-X™ Mobile Site Survey 18-602143 Customer

Avaya one-X™ Mobile Pre-Installation Checklist

18-602133 Installation Personnel

Avaya one-X™ Mobile System Acceptance/Signoff

18-602433 Installation Personnel

Avaya one-X™ Mobile Getting Started 18-602134 Customer



Avaya one-X Mobile Site SurveyPrior to installation of Avaya one-X Mobile, conduct a preliminary site survey and complete the information in this survey.

General Information Date:

Company Name:

Address:

Main Contact:

Email:

Office Phone:

Cell Phone:

Technical Contact:

Email:

Office Phone:

Cell Phone:

Avaya one-X Mobile Site Survey


Avaya Communication Manager/Cisco® CallManagerUse additional paper as needed

Cluster Setup – This information is needed for Avaya Communication Manager(s) where Avaya one-X Mobile is deployed.

1. What version and release of Avaya Communication Manager/Cisco CallManager do you wish to deploy with Avaya one-X Mobile?

2. What is the total number of users on your Avaya Communication Manager/Cisco CallManager?

3. Is the Avaya Communication Manager/Cisco CallManager clustered?

● Are there multiple Avaya Communication Managers?

● If so, how are they connected together?

4. If using Cisco CallManager, how many servers are in this cluster?

Note:Note: One Avaya one-X Mobile server is required per

Cisco CallManager cluster.

5. What is the total number of users are on each Avaya Communication Manager/Cisco CallManager? (Identify each cluster and list the number of users separately.)

6. What hardware is hosting the Avaya Communication Manager/Cisco CallManager where Avaya one-X Mobile is deployed?

7. How many users will use Avaya one-X Mobile?

8. For Avaya Communication Manager only: Are the Avaya one-X Mobile users configured for EC500 in Avaya Communication Manager?

1 of 4



9. Do you have additional PBXs in your network that are not Avaya Communication Managers or Cisco CallManagers? If yes, provide the following information:

● Type of PBX.

● How is Avaya Communication Manager/Cisco CallManager involved in the routing of calls to/from the other PBXs (if at all)?

Dial Plan – This information is needed for Avaya Communication Manager(s)/Cisco CallManager(s) and/or cluster(s) where Avaya one-X Mobile is deployed.

10. How many digits are used in your internal dial plan?

11. How is an outside line reached (dial 9, etc.)?

12. If a 1 is not required for 10-digit dialing of local numbers, provide a list of the NPA-NXXs for those numbers.

13. Do all users use the same dial plan(s) for outside lines? If no, explain how they differ.

14. How many digits are passed on the T1 circuit connected with your switch?

15. Do you use long distance authorization codes supplied by a carrier or external party?

● Does each user have a unique PIN?

● Does the user enter the PIN before or after the number is dialed?

16. Are forced authorization codes and/or client matter codes used on Avaya Communication Manager where Avaya one-X Mobile is deployed?

17. Provide information about the source (for example, Avaya, Cisco, or external party), management, and use of these codes.


2 of 4

Avaya one-X Mobile Site Survey


Directories

18. Is Active Directory your Enterprise Directory Source? If not, what directory is used?

19. What version of Active Directory do you use?

Note:Note: If you use a version other than Microsoft Active

Directory, an engineer may need to be consulted.

20. Confirm the following user information is in the Active Directory:

● Are the 10-digit numbers for your users available?

● What attribute holds this information?

● Are the user extensions stored in Active Directory?

● What attribute holds this information?

● What format is used for the user phone numbers in the Active Directory? (for example, 1xxxyyyzzzz, xxxyyyzzzz)

21. Is the Directory Authentication Source different from the Directory Look-up Source? If yes, contact an engineer.

CTI Applications

22. Are there any other CTI applications that use JTAPI running on the Avaya Communication Manager/Cisco CallManager? (for example, call center applications).

23. If yes, are the same users that use Avaya one-X Mobile using these CTI applications?

24. What version of AES is currently installed?

25. Is it being used for a call center environment?

26. For Avaya Communication Manager only: Is EC500 licensed and installed on the extensions on which Avaya one-X Mobile will be working?


3 of 4



Voicemail

27. What voicemail platform is used?

28. What software version is used?

29. What message store is used? (for example, Exchange)

30. If Exchange is the message store, which version is used?

31. If Exchange is the message store, which version of Active Directory is used?

32. How many Exchange servers are in your network?

33. Are all your users that will be using Avaya one-X Mobile contained within the same message store database?

Network Configuration

34. Is this a single or split server deployment? (See Network Configuration on page 9 for information about single and split server configurations.)

Wireless Carrier/Handset – This information is needed for the users licensed for Avaya one-X Mobile

35. List each user’s wireless handset with the following information:

● IP phone number

● IP phone model

● Wireless phone number

● Wireless carrier (for example, Sprint, Verizon)

● Handset manufacturer (for example, Blackberry, Motorola)

● Handset model (for example, RAZR, Treo700)

Note:Note: Complete this information on the Avaya one-X™

Mobile Subscriber Information Form.


4 of 4

Avaya one-X Mobile Pre-Installation Checklist


Avaya one-X Mobile Pre-Installation ChecklistReview 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

1 Identify server racks for the Avaya one-X Mobile Server.Note: The Avaya one-X Mobile Server requires the AES Server.

2 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.

3 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.

1 of 6



If this is a dual server environment, complete the following tasks for the external server.

4 Identify an external IP address and set up the mapping from external to internal IP.

5 Validate that the IMAP service is running on Exchange Server if Exchange is used as message store.

6 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.

7 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 SSL Certification on page 55 or instructions on securing SSL certification. ● Open Port 8080 and 1433 between inside and

outside servers.● Enable resolution to outside DNS from external

server.

8 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.

9 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 on page 42 for additional information.


2 of 6



10 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 on page 42 for additional information.

11 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

12 Gather administrative user name and password for:● Avaya Communication Manager● Modular Messaging ● Impacted switches involved in the deployment● AES

13 Gather the following information:● LDAP User DN● Switch Configuration Base DN ● Switch User Base DN

14 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.


3 of 6



15 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

16 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


4 of 6



Cisco® CallManager

17 Gather administrative user name and password for:● Cisco CallManager● Unity● Impacted switches involved in the deployment

18 Gather the following information:● LDAP User DN● Switch Configuration Base DN● Switch User Base DN

Directory

19 Gather the following information:● Microsoft Active Directory IP● Administration User DN● User Base DN● Administrator password

20 Gather the following information: ● Microsoft Exchange username and password.● Add user to the admin group of the local

machine.

SMTP Settings

21 Gather the following information:● SMTP username● SMTP password● IP address● IP port number ● Corporate email address

Dial Plan Validation (local 10-digit numbers)

22 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.


5 of 6



Test Extensions for Installation Team

23 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

24 Compile and list user names and extensions.

25 Identify the user’s:● Wireless carrier● Mobile numbers● Handset model● Handset manufacturer

26 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.)

27 Schedule users for a 30- to 60-minute training session on the morning following Avaya one-X Mobile Server installation.


6 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:

1. In the Active Directory Users and Computer, create a domain user account in the domain where your Microsoft Exchange server resides.

Note: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.

2. In the Microsoft Exchange System Manager, assign the permissions to Domain User as follows:

a. Navigate to the Mailbox Store of the Microsoft Exchange Server.

b. Right click Mailbox Store and select Properties.

c. Select the Security tab.

d. Click the Add button and add the Domain User.

e. 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

Create a Domain User


3. 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.



Avaya one-X Mobile System Acceptance/SignoffUse this form to complete the system setup, testing, and customer acceptance for the Avaya one-X Mobile Server.

General Information

Company Name:

Address:

Main Contact:

Email:

Office Phone:

Cell Phone:

Technical Contact:

Email:

Office Phone:

Cell Phone:

Avaya one-X Mobile System Acceptance/Signoff


Task System Acceptance/Signoff Task Completed By: Date:

1 Validate that the test lines are functional and perform Avaya one-X Mobile basic set of tests including the following:● Redirect calls to voicemail.● Redirect calls to mobile device.● Simulring.● Redirect incoming call to office phone.● Make a call back.Perform the following tests for the Avaya one-X Mobile Web application and mobile devices:● Validate that the call logs show incoming calls.● Validate that the call logs show outbound calls.● Perform a corporate directory lookup.● Initiate a call back via corporate directory

lookup.● Initiate a call back via personal directory

lookup.● Leave a voicemail message for the test user.● Check that the message shows up in the

applications.● Play the message from the applications.● Save the test message.● Delete the test message.

Set up for Avaya one-X Mobile Users

2 Have users download the Avaya one-X Mobile application on their mobile device and assist if necessary.

3 Train users on the Avaya one-X Mobile Web application.

4 Train users on the Avaya one-X Mobile application on their mobile device.

5 Verify message delivery, playback, and call redirection with a few users.

1 of 2



Access to Avaya one-X Mobile Server after Installation

6 Document how Avaya Support will access the Avaya one-X Mobile Server after initial implementation is completed.

Customer Installation Acceptance

7 Customer acknowledges Avaya one-X Mobile Service has been established and all users have been configured to their satisfaction. List any outstanding issues that may need to be addressed.

________________________________________

________________________________________

________________________________________

Note:Note: Provide customer with Avaya

Support contact telephone number 1-800-242-2121.

Customer Signature:

_______________________________________

Date:__________________________________

Task System Acceptance/Signoff Task Completed By: Date:

2 of 2

Avaya one-X Mobile Getting Started Checklist


Avaya one-X Mobile Getting Started ChecklistUse this checklist in preparation for the Avaya one-X Mobile Server installation and configuration.

General Information

Company Name:

Address:

Main Contact:

Email:

Office Phone:

Cell Phone:

Technical Contact:

Email:

Office Phone:

Cell Phone:



Task Getting Started Checklist Task Completed By: Date:

Server Installation and Network Configuration

1 Validate that Avaya one-X Mobile has been installed without any error.

2 Validate internal server has been joined to the domain and that a domain admin user password has been set up.

3 Validate terminal services port connection or other method to access the Avaya one-X Mobile Server(s) are open to the Avaya IP range for upgrading, collecting usage statistics, and troubleshooting.

Validate Ports are Opened

4 Validate access to port 80 or 443 if using SSL.

5 Validate network connectivity to the Microsoft Exchange Server, Avaya Communication Manager, Cisco® CallManager, Active Directory, and SMTP Server from the Avaya one-X Mobile Server.Note: See Network Configuration on page 9 for different ways to structure the network access.

Test Lines Set Up

6 Validate that two PBX test lines with full PSTN connectivity have been established for the installation testing. Note the extensions and PINs to be used.

7 Request and Install the license file.

1 of 5



Avaya one-X Mobile Administrative Configuration

Avaya AES and Communication Manager Licenses

8 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


9 Identify the users to be managed by the Avaya one-X Mobile application and ensure the following: ● The user is set up in the Active Directory.● The user’s phone extension is added to the Active

Directory Profile.● There is EC500 service for all Avaya one-X Mobile

users.

10 Validate the person with access to the administrative passwords is available for the configuration of Avaya Communication Manager and Avaya one-X Mobile.


2 of 5



11 Complete the following set up for Avaya Communication Manager:● Complete AES configuration.● TR87 configuration required on the AES server (See

the TR87 Implementation Guide).● Create a JTAPI user on the AES server.● Create CTI ports on the switch.● Add test users in appropriate Class of Restriction

and Class of Service.

Cisco CallManager

12 Identify the users to be managed by the Avaya one-X Mobile application.● Identify the Partitions and Calling Search Spaces on

the users’ mobile devices.● Ensure that the designated Avaya one-X Mobile

users in the organization:- are associated with their mobile devices - have their primary extension set up

13 Validate the person with access to the administrative passwords is available for the configuration of Cisco CallManager and Avaya one-X Mobile.

14 Complete the following setup for Cisco CallManager (see the Cisco CallManager Integration Guide):● Prepare Partitions and Calling Search Spaces for

the integration.● Validate the MWI is not in the same Calling Search

Space as the managed phones. Note: If MWI is in this Calling Search Space, the MWI will not work on managed phones.● View and understand the route plan report (route

patterns used by customer).● Create a JTAPI user.● Create CTI route points.● Configure phones for the integration.● Configure Cisco CallManager to correctly pass

Caller ID.● Add test users in proper Partitions and Calling

Search Spaces.


3 of 5



Avaya one-X Mobile Configuration


15 Log into the Avaya one-X Mobile Administrative User Interface and configure the following sections on the setup page:● Server Set-up● Provisioning Profile – Create new profile, complete

the information, and save the profile.● CTI Profile – Create new profile, complete the

information, and save the profile.● Voice Mail Profile – Create new profile, complete the

information, and save the profile.● Corporate Directory Profile –- Create new profile,

complete the information, and save the profile.● Class of Service – Utilize the profiles specified

above.


4 of 5



Cisco CallManager

16 Log into the Avaya one-X Mobile Administrative User Interface and configure the following sections on the setup page:● Server Set-up:- AXL Settings- LDAP Settings- Is Avaya Communication Manager Integrated with

Active Directory? (yes/no)- JTAPI Settings- Dial Plan- SMTP Settings- Microsoft Active Directory Settings- Microsoft Exchange Settings- Make any changes required for 10-digit local

dialing, if permissive dialing is not allowed via PRI.- Import Route Points

● Provisioning Profile – Create new profile, complete the information, and save the profile.

● CTI Profile – Create new profile, complete the information, and save the profile.

● Voice Mail Profile – Create new profile, complete the information, and save the profile.

● Corporate Directory Profile –- Create new profile, complete the information, and save the profile.

● Class of Service – Utilize the profiles specified above.

Avaya one-X Mobile Administrator User Interface - Users

17 Add CTI Ports.

18 Import Users.

19 License Users.

20 Assign Class of Service.


5 of 5



All documents related to Avaya one-X Mobile are listed in the following table.

Document Title Document Number

Description

Avaya one-X™ Mobile Site Survey 18-602143 Planning document for customer.

Avaya one-X™ Mobile Administration and Maintenance Guide

18-602144 Describes how to configure, administer, and maintain the Avaya one-X Mobile Server.

Avaya one-X™ Mobile Integration Guide 18-602153 Describes how to integrate solution components including AES, CM, Modular Messaging, Exchange and Active Directory, CallManager, and Cisco Unity.

Avaya one-X™ Mobile Pre-Installation Checklist

18-602133 Planning for installation.

Avaya one-X™ Mobile Getting Started 18-602134 Planning for installation and configuration.

Avaya one-X™ Mobile System Acceptance/Signoff

18-602433 Confirms system setup, testing, and customer acceptance for the Avaya one-X Mobile Server.

Avaya one-X™ Mobile Installation Guide 18-602135 Describes physical connections, networking, and integration with the call server.

Avaya one-X™ Mobile J2ME User Guide 18-602147 End user document that describes key features and how to use them on the mobile device.

Avaya one-X™ Mobile BlackBerry User Guide

18-602148 End user document that describes key features and how to use them on the mobile device.

Avaya one-X™ Mobile Palm Treo User Guide

18-602149 End user document that describes key features and how to use them on the mobile device.

1 of 2



Avaya one-X™ Mobile Web User Guide 18-602150 End user document that describes key features and how to use them on the mobile device.

Interactive Tutorial N/A Shows how to use the Avaya one-X Mobile clients.

Document Title Document Number

Description

2 of 2


Appendix C: SSL Certification

Secure Sockets Layer (SSL) is a Netscape protocol developed for transmitting private documents over the Internet. SSL creates a secure connection between a client and a server, over which any amount of data can be sent securely.

The customer is responsible for securing SSL Certification. Instructions on how to secure SSL certification is provided in this appendix.

Perform the following tasks in the order provided:

● Task 1: Download the SSL Application on page 55

● Task 2: Remove Existing Security Certificates on page 56

● Task 3: Get the AES SSL Certificate on page 57

● Task 4: Get the MSS SSL Certificate on page 58

● Task 5: Import the New Security Certificates on page 59

Task 1: Download the SSL ApplicationPerform the following steps to download the SSL application and run the executable file Win32OpenSSL-0_9_8e.exe.

1. Open your internet browser on the application server.

2. Go to www.openssl.org.

3. Click the Binaries link.

4. Click the OpenSSL for Windows link.

5. Scroll to the download section.

6. Click the Win32openSSL v0.9.8e link to get the application.

Note:Note: The direct link to the application that was valid as of 06/28/2007 is

http://www.slproweb.com/products/Win32OpenSSL.html



Task 2: Remove Existing Security CertificatesPerform the following steps to remove the existing security certificates.

1. Navigate to the Windows directory C:\Program Files\Java\jdk1.5.0_10\bin.

2. Run the keytool command with the following options and parameters:

keytool -delete -v -noprompt -alias com.avaya.edge.aescert -keystore"C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\classes\trusted_weblm_certs.jks" -storepass password

keytool -delete -v -noprompt -alias com.avaya.edge.aescert -keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\lib\trusted_weblm_certs.jks" -storepass password

keytool -delete -v -noprompt -alias com.avaya.edge.aescert -keystore"C:\Program Files\Java\jdk1.5.0_10\jre\lib\security\cacerts" -storepass changeit

keytool -delete -v -noprompt -alias com.avaya.edge.msscert -keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\classes\trusted_weblm_certs.jks" -storepass password

keytool -delete -v -noprompt -alias com.avaya.edge.msscert -keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\lib\trusted_weblm_certs.jks" -storepass password

keytool -delete -v -noprompt -alias com.avaya.edge.msscert –keystore "C:\Program Files\Java\jdk1.5.0_10\jre\lib\security\cacerts" –storepass changeit

keytool -delete -v -noprompt -alias com.avaya.edge.ldapcert -keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\classes\trusted_weblm_certs.jks" -storepass password

keytool -delete -v -noprompt -alias com.avaya.edge.ldapcert -keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\lib\trusted_weblm_certs.jks" -storepass password

keytool -delete -v -noprompt -alias com.avaya.edge.ldapcert -keystore "C:\Program Files\Java\jdk1.5.0_10\jre\lib\security\cacerts" –storepass changeit

Task 3: Get the AES SSL Certificate


Task 3: Get the AES SSL CertificatePerform the following steps to get the AES SSL certificate.

1. Navigate to the Windows directory C:\OpenSSL\bin.

2. Run openssl with the following parameters:-openssl s_client -connect <ip.of.aes.server>:443

3. Copy the following output and save it in a file called aes.pem.

BEGIN CERTIFICATE-----

MIIDMzCCApygAwIBAgIBADANBgkqhkiG9w0BAQQFADB1MQswCQYDVQQGEwJVUzEL

MAkGA1UECBMCQ08xDzANBgNVBAcTBkRlbnZlcjEOMAwGA1UEChMFQXZheWExKTAn

BgNVBAsTIEF2YXlhIENvbnZlcmdlZCBTeXN0ZW1zIERpdmlzaW9uMQ0wCwYDVQQD

EwRNVkFQMB4XDTA0MDkxNDAxMjczMloXDTM0MDkwNzAxMjczMlowdTELMAkGA1UE

BhMCVVMxCzAJBgNVBAgTAkNPMQ8wDQYDVQQHEwZEZW52ZXIxDjAMBgNVBAoTBUF2

YXlhMSkwJwYDVQQLEyBBdmF5YSBDb252ZXJnZWQgU3lzdGVtcyBEaXZpc2lvbjEN

MAsGA1UEAxMETVZBUDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAr2xeyriH

uwNQ8iA0TvTGdd1+Dbl9uE9G2eo8k020v6i70V8BViA3LgWkiNDWq9Vh/kIO/1Xj

OCjk4IEjUEmU2eH2N+EMpPH5Zg1PnVsV+V3Mqvyi2ZrA+d38QGh5+/dY8iWpqvsq

ZkVHC3OEHK55dS81UZdSD6WfRfT1gdiyiEUCAwEAAaOB0jCBzzAdBgNVHQ4EFgQU

j4D0MItnzawG6J8pQtcwywJQfXMwgZ8GA1UdIwSBlzCBlIAUj4D0MItnzawG6J8p

QtcwywJQfXOheaR3MHUxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJDTzEPMA0GA1UE

BxMGRGVudmVyMQ4wDAYDVQQKEwVBdmF5YTEpMCcGA1UECxMgQXZheWEgQ29udmVy

Z2VkIFN5c3RlbXMgRGl2aXNpb24xDTALBgNVBAMTBE1WQVCCAQAwDAYDVR0TBAUw

AwEB/zANBgkqhkiG9w0BAQQFAAOBgQCN9E2VblWV3ROXnrflRTEDhIttU059V805

1w72+e3Y1loYKStNHZOsi3Z3lhJknNaHWeaafSyxBwX6ObJblozc7RldaznaEmSB

p7j/9SnAqktVBFfBwYnD99zsTcEM4rQugpbhYTWSJr5HfzLVCtjyJXEvL6LwxR1O

yUMTWKm6wg==

END CERTIFICATE-----

4. Save the aes.pem file you just created to C:\Program Files\Java\jdk1.5.0_10\bin.



Task 4: Get the MSS SSL CertificatePerform the following steps to get the MSS SSL certificates.

1. Navigate to the Windows directory C:\OpenSSL\bin.

2. Run openssl with the following parameters:-openssl s_client -connect <ip.of.mss.server>:993

3. Copy the following output and save it in a file called mss.pem.

BEGIN CERTIFICATE-----

MIICxDCCAi2gAwIBAgIBADANBgkqhkiG9w0BAQQFADBRMQswCQYDVQQGEwJVUzET

MBEGA1UEChMKQXZheWEgSW5jLjESMBAGA1UECxMJTWVzc2FnaW5nMRkwFwYDVQQD

ExBxYW1zczEucWFkb20uY29tMB4XDTA3MDUxNzAwMTYzN1oXDTM3MDUwOTAwMTYz

N1owUTELMAkGA1UEBhMCVVMxEzARBgNVBAoTCkF2YXlhIEluYy4xEjAQBgNVBAsT

CU1lc3NhZ2luZzEZMBcGA1UEAxMQcWFtc3MxLnFhZG9tLmNvbTCBnzANBgkqhkiG

9w0BAQEFAAOBjQAwgYkCgYEA0SOeEqSjC+vIuKxkUPMppIcsF2l+vujWoiv+kMMR

c6yxiv5N7UqiZhwnX1u5ZDuUaJBZNC8X849gR4Pf/NjXDyMNfmtbXmdFNGqd1BDB

GAjfmsBe5tDwIhbisMZpHPlsfPvTtB4IDjmOOrE/ZsbvUwiXO0huJBec9rRugIDn

fX0CAwEAAaOBqzCBqDAdBgNVHQ4EFgQUm5eGad7166gEkXMsdHXd2EXjazYweQYD

VR0jBHIwcIAUm5eGad7166gEkXMsdHXd2EXjazahVaRTMFExCzAJBgNVBAYTAlVT

MRMwEQYDVQQKEwpBdmF5YSBJbmMuMRIwEAYDVQQLEwlNZXNzYWdpbmcxGTAXBgNV

BAMTEHFhbXNzMS5xYWRvbS5jb22CAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0B

AQQFAAOBgQAaqF7sOZfrHaACOS+fQhziNxilZ0wkNWHKDTB4pIdoLzlcjyXvxCUB

mxWRziGSnvE5qWJP5+zVrkaK9YrqOoO9X3Zym8A4n10hFKNh2m0YyA+9Mzk+0O9U

P0mZdUklaeFIEcBXKhwL9Y+696YEcuR2+w+fOtwy5CjgZ6SaslkydA==

END CERTIFICATE-----

4. Save the mss.pem file you just created to C:\Program Files\Java\jdk1.5.0_10\bin.

Task 5: Import the New Security Certificates


Task 5: Import the New Security CertificatesPerform the following steps to import the new security certificates.

1. Navigate to the Windows directory C:\Program Files\Java\jdk1.5.0_10\bin.

2. Run the keytool command with the following options and parameters:

Note:Note: When prompted, answer with y.

keytool -import -file "aes.pem -trustcacerts –alias com.avaya.edge.aescert -keystore "C:\Program Files\Java\jdk1.5.0_10\jre\lib\security\cacerts" -storepass changeit

keytool -import -file "aes.pem -trustcacerts –alias com.avaya.edge.aescert -keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\classes\trusted_weblm_certs.jks" -storepass password

keytool -import -file "aes.pem -trustcacerts –alias com.avaya.edge.aescert –keystore "C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\lib\trusted_weblm_certs.jks" -storepass password

keytool -import -file "mss.pem -trustcacerts –alias com.avaya.edge.msscert -keystore "C:\Program Files\Java\jdk1.5.0_10\jre\lib\security\cacerts" -storepass changeit

keytool -import -file "mss.pem -trustcacerts –alias com.avaya.edge.msscert -keystore"C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\classes\trusted_weblm_certs.jks" -storepass password

keytool -import -file "mss.pem -trustcacerts –alias com.avaya.edge.msscert -keystore"C:\Edge\Utilities\apache-tomcat-5.5.23\webapps\edge\WEB-INF\lib\trusted_weblm_certs.jks" -storepass password

The certification process is now complete. Follow the instructions for applying SSL Certificates on the outside of the server as required by corporate security standards.



Date post:	20-Apr-2020
Category:	Documents
Upload:	others
View:	26 times
Download:	0 times