Lync Server And Cucm
Authors: Danny Cheung, Taimoor Husain
Publication date: July 2011
Abstract: This article provides a step-by-step guide for configuring Cisco Unified Communications Manager with Microsoft® Lync™ Server 2010 by using Direct SIP.
This document is provided “as-is”. Information and views expressedin 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 thisdocument for your internal, reference purposes.
© 2011 Microsoft. All rights reserved.
Microsoft, Active Directory, Hyper-V, Lync, Windows, and Windows PowerShell are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
Contents
Integrating Microsoft Lync Server and Cisco Unified Communications Manager 1
Configure CiscoUnified Communications Manager 2
Configure SIP Trunk 2
Configure Translation Pattern 7
Configure Route Pattern 9
Configure ISR Gateway 14
Configure Mobility (Optional) 14
Configure Lync Server 17
Add CUCM to the Lync Topology 17
Configure Dial Plan 18
Add Voice Policy and Route 19
Add Trunk Configuration 22
Configure Media Bypass 23
Summary 25
Additional Resources 26
Appendix A –Call Scenarios 27
Integrating Microsoft Lync Server and Cisco Unified Communications Manager
Microsoft® Lync™ Server 2010 communications software can send and receive calls with Cisco Unified Communications Manager (CUCM) by using Direct SIP. This capability has been tested by Microsoft with multiple versions of CUCM. For details, see “Unified Communications Open InteroperabilityProgram—Lync Server” at http://go.microsoft.com/fwlink/?LinkId=223942.
This white paper will show step-by-step configuration tasks to set up the Direct SIP connectivity between CUCM and Lync Server 2010. These steps include configuration of the media bypass feature that optimizes media flow by allowing Lync endpoints to directly establish a media connection with gateway or private branch exchange(PBX) without going through Lync Server Mediation Server.
In order to test the interoperability cases, we picked a topology that we believe most customers would have when migrating or integrating their existing Cisco IP telephony infrastructure with Lync Server 2010 and Microsoft® Lync™ 2010.In most cases, customers would have their public switched telephone network (PSTN) lines terminated atthe Cisco ISR router and use the CUCM as a peer IP-PBX for communicating with Lync 2010.
In our environment, the topology looks like this:
[pic]
Figure 1. Lab topology
In our lab, the Cisco ISR is 2811 running IOS version 12.4(20)T1. Cisco Unified Communications Manager is running on a MCS-7816-H3 hardware platform and the CUCM version is 8.5.1.11900-21.
Lync Server is running on aHyper-V® virtualized environment and it has the Mediation Server collocated with the Front End Server.
The hardware platform should not have any impact to the configuration and interoperability we illustrate in this article.
We assume that you have already configured Lync and CUCM properly such that they can do call routing at their own domain, for example, calls can be made among Ciscophones, calls can be made between PSTN and Cisco phones, and calls can be made among Lync clients. If you don’t have these working and need guidance, see the Lync Server TechCenter at http://go.microsoft.com/fwlink/?LinkId=201187. This document will detail the necessary steps to connect the elements together by using Direct SIP to exchange calls between systems.
The dial-plan looks like this:...
Regístrate para leer el documento completo.