Print

Checklist for integrating AE Services with Microsoft Live Communications Server 2005

Use the following checklist to perform the necessary tasks to integrate AE Services in a Communications Server environment:

# Task Description
1 Administer a switch connection from AE Services to Communication Manager. See AE Services integration for Microsoft Office Live Communications Server 2005 or Microsoft Office Communications Server 2007 - checklist, in Chapter 3 of the Administering and Maintaining Avaya Aura® Application Enablement Services, 02-300357.
2 Check the status of the switch connection (from AE Services to Communication Manager).
3 Administer a TSAPI Link.
4 Enable the TR/87 Port in the AE Services Management Console. See Enabling the TR/87 port.
5 Administer certificates for AE Services and Microsoft Live Communications Server. See Trusted certificate installation on Communications Server.
See Server certificate installation for the Communications Server of this document.
See Trusted certificate installation on the AE Services server of this document.
See Creating a server certificate request for AE Services of this document.
See Server certificate creation for AE Services of this document.
See Importing the server certificate into AE Services of this document.
6 Administer settings for the dial plan. See Dial Plan settings in AE Services of this document.
7 Administer settings for Active Directory. See Administering AE Services access to Active Directory of this document.
8 Configure the Microsoft Office Communicator 2005 Client. See Configuring the Client in the Microsoft Office Communicator 2005 Telephony Planning and Deployment Guide.
9 Set up a static route. See Configuring a static route.
10 Specify the AE Services Server as an authorized host. See Specifying the AE Server as an authorized host for Microsoft Live Communications Server.
11 Set up Remote Call Control for each user in Active Directory Services. See Enabling Remote Call Control in Active Directory for Microsoft Live Communications Server. Based on information from Microsoft Office Communicator 2005 Telephony Planning and Deployment Guide.