Integrating Microsoft Lync Server 2010 and Avaya Communications Manager S8300
Microsoft Lync Server 2010
Published: April 2011
Authors: Rui Maximo with technical assistance from Nandita Sharma and Mark King Abstract: If you want to integrate an Avaya S8300 Communications Manager with the Microsoft? Lync? Server 2010 communications software, you need to establish a Direct SIP connection between the two. This document provides a step-by-step guide for configuring Avaya Communications Manager S8300 with Lync Server 2010.
This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice.
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.
? 2011 Microsoft. All rights reserved.
Contents
Integrating Microsoft Lync Server and Avaya Communications Manager (1)
Configure Avaya Communications Manager (2)
Configure Call Routing between Avaya Communications Manager and SES (3)
Create Signaling Group (3)
Create Trunk Group (4)
Define Route Pattern (5)
Configure Dial Plans (5)
Configure Avaya SIP Enablement Services (6)
Configure Static Route to Lync Server (6)
Configure static route to Avaya Communications Manager (9)
Configure Lync Server (10)
Adding Avaya SES as a gateway to the Lync Server Topology (11)
Define Dial Plan (12)
Create Voice Policy (13)
Define Trunk Configuration (17)
Additional Resources (17)
Appendix (18)
Configure Call Routing between Avaya Communications Manager and the Branch Site SES (18)
Create Signaling Group (18)
Create Trunk Group (18)
Configure Avaya SES at each Branch Site (19)
Configure Lync Server to use Branch Site SES (19)
Adding Branch Site SES as a Gateway to the Lync Topology (19)
Integrating Microsoft Lync Server and Avaya Communications Manager Microsoft? Lync Server? 2010 communications software can interoperate with Avaya Communications Manager 4.0.
In this article, Avaya Communications Manager is running on an Avaya S8300 Media Server with an Avaya G350 Media Gateway. The Avaya G350 Media Gateway provides the physical interfaces and resources for Communications Manager. This just happens to be the hardware in our lab, but if you have other versions that you are interested in configuring for Direct SIP with Lync Server 2010, please contact me. We would like to partner with you to author an article on the NextHop blog. For details about the NextHop blog, see https://www.doczj.com/doc/7f4399832.html,/fwlink/?LinkId=203149.
According to the Avaya support site at https://www.doczj.com/doc/7f4399832.html,/usa/product/servers#S8300 Server, the Avaya S8300 Media Server (shown in Figure 1) resides inside an Avaya G700, G450, G350, or G250 Media Gateway. You can use it as a stand-alone communication system or as a fully survivable remote gateway. The Avaya S8300 Media Server can be the primary controller for up to 50 remote Avaya G250, G350, G450, and G700 Media Gateways.
Figure 1 Avaya S8300
For Avaya Communications Manager to interoperate with Lync Server by using direct SIP, you need to use Avaya SIP Enablement Services (SES) as an interface between the Avaya infrastructure and the Lync Server infrastructure. In SES, SIP trunks are used to connect Communications Manager and Lync Server 2010. Avaya SIP Enablement Services provides core SIP routing and integration services that enable communications between Avaya Communications Manager and the Lync Server Mediation Server. The version of SIP Enablement Services used in our lab is 4.0.0.0-033.6. This Direct SIP topology is illustrated in Figure 2.
Integrating Microsoft Lync Server and Avaya Communications Manager
Avaya
Communication
Server Avaya SIP Enablement Services Figure 2 Direct SIP topology
This topology requires that you perform the following configuration steps:
1. Configure Avaya Communications Manager 4.0 on an Avaya S8300 Media Gateway.
2. Configure Avaya SIP Enablement Services 4.0.0.0-03
3.6.
3. Configure Lync Server 2010.
Before we jump in, a quick point: This configuration involves making changes to your IP-PBX, changes that we recommend be performed by someone with experience in your environment. Although we
don’t anticipate any of these changes having an impact on your production system, you should still take any necessary steps to back up your configuration before you begin and edit where appropriate for your environment. Microsoft makes no warranties, express or implied, on this content, and you proceed at your own risk.
Configure Avaya Communications Manager
The steps to configure Avaya Communications Manager are as follows:
1. Configure call routing between Avaya Communications Manager and SES.
2. Configure call routing between Lync Server and SES.
3. Configure dial plans to route calls between Avaya Communications Manager and Lync Server. The rest of this section describes these steps in detail. The Avaya Communications Manager commands described in this section were administered by using the System Access Terminal (SAT). To access the SAT command line interface, use Secure Shell (SSH) or Telnet to connect to the Communications Manager. Open a command prompt window. At the command prompt, type SAT , and then press Enter.