Avaya Solution & Interoperability Test Lab Application Notes for Microsoft Office Communicator Clients with Avaya Communication Manager Phones - Issue 1.1 Abstract These Application Notes describe the configuration procedures for enabling Microsoft Office Communicator (MOC) clients to operate Avaya Communication Manager phones. The MOC client and Microsoft Office Communications Server (OCS) provide the user with multiple modes of communications, such as Instant Messaging (IM), voice, and video.
1. Introduction These Application Notes describe the procedures for configuring TR/87 integration between Avaya Communication Manager and Microsoft Office Communications Server (OCS). The TR/87 integration allows a Microsoft Office Communicator (MOC) client running on a Microsoft Windows computer to operate an Avaya Communication Manager phone using CSTA CTI call control constructs.
Both RCC and EV clients are registered with Microsoft OCS, which is comprised of one or more of each of the following: Front-End Servers, IM Conferencing Servers, Telephony Conferencing Servers, A/V Conferencing Servers, Web Conferencing servers, and IIS Servers. In the sample configuration of Figure 1, the aforementioned component servers reside on a single physical server in an Microsoft OCS Enterprise Edition (EE) Consolidated configuration.
3. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment & Software Avaya S8300 Server Avaya G350 Media Gateway Media Gateway Processor Avaya Application Enablement Services Server Avaya SIP Enablement Services Server Avaya 4600 Series H.
4. Avaya Communication Manager and Avaya Application Enablement Services Integration These Application Notes assume that basic Avaya Communication Manager and Avaya Application Enablement (AE) Services administration has already been performed. These Application Notes further assume that an AE Services connection and TSAPI CTI link has already been configured and established between Avaya Communication Manager and Avaya AE Services. 4.1.
4.3. TR/87 Port Launch a web browser, enter the URL https://:8443/MVAP, and log into the Avaya AE Services OAM Web Interface. In the left pane, select CTI OAM Admin. In the left pane of the CTI OAM Home Web Interface, select Administration Æ Network Configuration Æ Ports. In the right pane, enable TR/87 Port and click on “Apply Changes” (not shown below). RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc.
5. Certificates The Avaya AE Services and Microsoft OCS servers must exchange signed server certificates each time a Transport Layer Security (TLS) enabled TCP connection is initiated between the two servers. The certificates must be obtained from the same Certificate Authority (CA) or from CAs in the same certificate chain. In the sample configuration, a Microsoft Enterprise CA (running on Microsoft Windows Server 2003) serves as the CA for both. 5.1.
Step Description 3. In the Microsoft Certificate Services Download a CA Certificate, Certificate Chain, or CRL page, select the “Current” CA certificate of the Microsoft Enterprise CA, set Encoding method to “Base 64”, and click on “Download CA certificate chain”. 4. When prompted, save the CA certificate chain file to a local directory on the Microsoft OCS server. After saving, navigate to that directory in Windows Explorer, right-click on the CA certificate chain file, and select “Install Certificate”.
Step Description 5. In the Certificate Import Wizard dialog box, click on “Next”. 6. In the Certificate Import Wizard dialog box, select “Place all certificates in the following store” and click on “Browse”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 7. In the Select Certificate Store dialog box, select “Trusted Root Certification Authorities” and click on “OK”. 8. In the Certificate Import Wizard dialog box, click on “Next”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 9. In the Certificate Import Wizard dialog box, click on “Finish”. 10. Repeat Steps 1 – 9 on each Microsoft OCS server in the enterprise pool. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
5.2. Create Certificate Template for Server Certificates The server certificates exchanged between Avaya AE Services and Microsoft OCS must support both Server Authentication and Client Authentication. This section describes the steps for creating a certificate template for such server certificates on the Microsoft Enterprise CA. Step Description 1. On the Microsoft Enterprise CA server, launch the Certification Authority Microsoft Management Console (MMC) snap-in. 2.
Step Description 4. In the Properties of New Template dialog box, select the General tab, and enter a descriptive Template display name and Template name. 5. In the Properties of New Template dialog box, select the Request Handling tab, and ensure that Purpose is set to “Signature and encryption”. Click on “CSPs”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 6. In the CSP Selection dialog box, select “Requests must use one of the following CSPs:” and check the “Microsoft Enhanced Cryptographic Provider v1.0” checkbox. Click on “OK”. 7. In the Properties of New Template dialog box, select the Subject Name tab and ensure that “Supply in the request” is selected. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 8. In the Properties of New Template dialog box, select the Extensions tab. In the Extensions included in this template section, select “Application Policies” and click on “Edit”. 9. In the Edit Application Policies Extension dialog box, click on “Add”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 10. In the Add Application Policy dialog box, select “Client Authentication” and click on “OK”. 11. In the Edit Application Policies Extension dialog box, ensure that both Server Authentication and Client Authentication are included in the Application Policies list. Click on “OK”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 12. In the Properties of New Template dialog box, click on “OK”. 13. In the Certification Authority MMC snap-in, expand the Certification Authority node, rightclick on Certificate Templates, and select “New Æ Certificate Template to Issue”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 14. In the Enable Certificate Templates dialog box, select the Certificate Template created in Steps 3 -12 and click on “OK”. 5.3. Request and Install Server Certificate on Microsoft OCS Server This section describes the steps for requesting the server certificate (based on the certificate template created in Section 5.2) from the Microsoft Enterprise CA and installing the server certificate on a Microsoft OCS server. Step Description 1.
Step Description 3. In the Microsoft Certificate Services Request a Certificate page, click on “advanced certificate request”. 4. In the Microsoft Certificate Services Advanced Certificate Request page, click on “Create and submit a request to this CA”. 5. In the Microsoft Certificate Services Advanced Certificate Request page, select the Certificate Template created in Section 5.2, and configure the fields in the Identifying Information For Offline Template section.
Step Description 6. Scroll down in the Microsoft Certificate Services Advanced Certificate Request page. In the Key Options section, select “Microsoft Enhanced Cryptographic Provider v1.0” for CSP, and check the Store certificate in the local computer certificate store checkbox.
Step Description 8. Repeat Steps 1 – 7 on each Microsoft OCS server in the enterprise pool. 5.4. Assign Server Certificate to Microsoft OCS Enterprise Pool Server Connections This section describes the steps for assigning the server certificate installed in Section 5.3 to inbound and outbound connections on a Microsoft OCS enterprise pool server. Step Description 1. On a Microsoft OCS server, launch the Microsoft Office Communications Server 2007 MMC snap-in.
Step Description 2. In the Properties dialog box, click on “Select Certificate”. 3. In the Select Certificate dialog box, select the certificate installed in Section 5.3 and click on “OK”. Note: This new certificate replaces the certificate assigned during Microsoft OCS installation. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 4. In the Properties dialog box, click on “OK”. 5. Repeat Steps 1 – 4 on each Microsoft OCS server in the enterprise pool. 5.5. Install Certificate Chain (Trusted Certificate) on Avaya Application Enablement Services Server This section describes the steps for installing the Microsoft Enterprise CA certificate chain (trusted certificate) on an Avaya AE Services server. Step Description 1. On a Microsoft OCS server, make a copy of the CA certificate chain file downloaded in Section 5.
Step Description 2. On the Microsoft OCS server, launch a web browser and log into the Avaya AE Services OAM Web Interface. In the left pane, select CTI OAM Admin Æ Administration Æ Certificate Management Æ Trusted Certificate. In the Trusted Certificates page, click on “Import”. 3. In the Trusted Certificate Import page, enter a descriptive name for Certificate Alias, and paste the copied contents from Step 1 into the Certificate PEM textbox. Click on “Apply”.
5.6. Request and Install Server Certificate on Avaya Application Enablement Services Server This section describes the steps for requesting the server certificate (based on the certificate template created in Section 5.2) from the Microsoft Enterprise CA and installing the server certificate on an Avaya AE Services server Step Description 1. On the Microsoft OCS server, launch a web browser and log into the Avaya AE Services OAM Web Interface.
Step Description 2. In the Add Server Certificate page, configure the following and click on “Apply”. • Certificate Alias – enter a descriptive name. • Password and Re-enter Password – enter an arbitrary password. • Distinguished Name – enter “CN=,OU=,O=,L=,S=,C=” . Use the same Department, Company, City, State, and Country/Region values entered in Section 5.3 Step 5. In the example below, “CN=msavaes1.sitlms.
Step Description 3. In the Server Certificate Manual Enrollment Request page , copy the entire contents of the Certificate Request PEM textbox into the Windows clipboard. 4. Repeat Section 5.3 Steps 1 - 3. 5. In the Microsoft Certificate Services Advanced Certificate Request page, click on “Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file”.
Step Description 6. In the Submit a Certificate Request or Renewal Request page, paste the copied contents from Step 3 into the Saved Request textbox, select the Certificate Template created in Section 5.2, and click on “Submit”. 7. In the Certificate Issued page, select “Base 64 encoded” and click on “Download certificate”. 8. When prompted, save the certificate file to a local directory on the Microsoft OCS server.
Step Description 9. In the left pane of the Avaya AE Services OAM Web Interface, select CTI OAM Admin Æ Administration Æ Certificate Management Æ Server Certificate Æ Pending Requests. In the Pending Requests Certificate Requests page, select the alias for the certificate request created in Steps 1 - 3 and click on “Manual Enroll”. 10. In the Server Certificate Manual Enrollment Request page, click on “Import”.
Step Description 11. In the Server Certificate Import page, enter the same Certificate Alias, ensure that the Establish Chain of Trust checkbox is checked, paste the copied contents from Step 8 into the Certificate PEM textbox, and click on “Apply”. If the import is successful, the message “Certificate imported successfully” is displayed on the Server Certificate Import page. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
6. Avaya Application Enablement Services TR/87 Configuration This section describes the Active Directory and Dial Plan configuration on Avaya AE Services for TR/87 integration with Microsoft OCS. Step Description 1. Launch a web browser and log into the Avaya AE Services OAM Web Interface. In the left pane, select CTI OAM Admin Æ Administration Æ TR87 Configuration Æ Active Directory. In the Active Directory Configuration page, configure the following and click on “Apply Changes”.
Step Description 2. In the left pane, select Dial Plan Æ Switch Administration. In the Switch Dial Plan Administration page, select the switch connection corresponding to the appropriate Avaya Communication Manager, and click on “Detail”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 3. In the Dial Plan Settings – Conversion Rules page, click on “Add” in the From TelURI section. Avaya AE Services uses the From TelURI table to convert E.164-formatted numbers in TR/87 requests received from Microsoft OCS into extensions and number strings that Avaya Communication Manager can handle and route. For example, when an RCC client places a call on behalf of an Avaya Communication Manager phone, Microsoft OCS sends a call initiation request to Avaya AE Services.
Step Description 4. In the Add Dial Plan From TelURI page, configure an entry that converts the E.164-formatted numbers assigned to the RCC clients (see Section 7 Step 3) to the corresponding Avaya Communication Manager phone extensions (see Section 4.1), and click on “Apply Changes”. This entry applies to the calling number when a RCC client sends a call initiation request to Avaya AE Services, and allows Avaya Communication Manager to identify the phone for which the RCC client is placing the call.
Step Description 7. Repeat Steps 3 – 5 to configure an entry that extracts the “extensions” from the E.164-formatted numbers assigned to the EV clients (refer to [1] and Section 4.1). This entry applies to the called number when a RCC client sends a call initiation request to Avaya AE Services, where the called number is the E.164-formatted number assigned to an EV client.
Step Description 8. Repeat Steps 3 – 5 to configure an entry that extracts the extensions from E.164-formatted numbers corresponding to Avaya Communication Manager phones that are not associated with RCC clients. This entry applies to the called number when a RCC client sends a call initiation request to Avaya AE Services, where the called number is an E.164-formatted number containing the extension of an Avaya Communication Manager phone that is not associated with an RCC client.
Step Description 9. Repeat Steps 3 – 5 to configure an entry that adds a leading digit to E.164-formatted external numbers, and click on “Apply Changes”. The leading digit must be the ARS Access Code configured on Avaya Communication Manager for ARS routing (refer to [1]). This entry applies to the called number when a RCC client sends a call initiation request to Avaya AE Services, where the called number is the E.164-formatted number of an external phone. In the example below, the entry matches E.
Step Description 10. In the Dial Plan Settings – Conversion Rules page, click on “Add” in the To TelURI section. Avaya AE Services uses the To TelURI table to convert extensions and number strings received from Avaya Communication Manager into formatted numbers that Microsoft OCS recognizes.
Step Description 11. In the Add Dial Plan To TelURI page, configure an entry that adds a leading “+” to non-E.164formatted numbers, and click on “Apply Changes”. This entry applies to the calling or called number when Avaya AE Services sends a call notification to a RCC client, where the number lacks a leading “+”. This can occur when an external phone or EV client3 calls a RCC client, or when the Avaya Communication Manager phone associated with the RCC client dials an external phone.
7. Configure Microsoft Office Communications Server This section highlights the Microsoft Office Communications Server (OCS) configuration for TR/87 integration with Avaya AE Services. These Application Notes assume that basic Microsoft OCS server installation and configuration have already been performed according to the guidelines provided in [6], [7], and [8]. These Application Notes further assume that user accounts have been created in Microsoft Active Directory and enabled for Microsoft OCS.
Step Description 2. In the selected user’s Properties dialog box, click on “Configure”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 3. In the User Options dialog box, in the Telephony section, select “Enable Remote call control”, enter “sip:aes@” for Server URI, and enter an E.164 Tel URI for Line URI. The trailing five digits of the E.164 Tel URI should contain the user’s Avaya Communication Manager phone extension (see Section 4.1).
Step Description 6. In the left pane of the Microsoft Office Communications Server 2007 MMC snap-in, expand the Forest node down to the Enterprise Pool level (Forest Æ Enterprise pools Æ ), right-click on Front Ends, and select “Properties”. 7. In the Front Ends Properties dialog box, select the Routing tab and click on “Add”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
Step Description 8. In the Add Static Route dialog box, in the Matching URI section, enter the FQDN of the Avaya AE Services server for Domain. In the Next hop section, enter the FQDN of the Avaya AE Services server for FQDN, select “TLS” for Transport, and enter the Avaya AE Services TR/87 Port (see Section 4.3) for Port. Click on “OK”. 9. In the Front Ends Properties dialog box, select the Host Authorization tab and click on “Add”.
Step Description 10. In the Add Authorized Host dialog box, in the Server section, select “FQDN” and enter the FQDN of the Avaya AE Services server. In the Settings section, ensure that the Outbound Only checkbox is unchecked, and check the Throttle As Server and Treat As Authenticated checkboxes. Click on “OK”. 11. In the Front Ends Properties dialog box, click on “OK”. RL; Reviewed: SPOC 11/5/2007 Solution & Interoperability Test Lab Application Notes ©2007 Avaya Inc. All Rights Reserved.
8. Verification Steps The following steps may be used to verify the configuration: • Place outbound calls from a RCC client to Avaya phones (associated and not associated with RCC clients), EV clients, and Microsoft Exchange voicemail access and Auto Attendant using extension dialing. Verify that the calls are established successfully on the associated RCC Avaya phones.
9. Conclusion These Application Notes described the configuration procedures for enabling Microsoft Office Communicator (MOC) clients to place, answer, hold/retrieve, transfer, and disconnect calls on Avaya Communication Manager phones. The integration between MOC clients and Avaya Communication Manager phones was achieved through TR/87 integration between Avaya Application Enablement Services and Microsoft OCS.
© 2007 Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™ are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice.
