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 http://go.microsoft.com/fwlink/?LinkId=203149.
According to the Avaya support site at http://www.avaya.com/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.
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 188.8.131.52-033.6. This Direct SIP topology is illustrated in Figure 2.
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 184.108.40.206-033.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.