Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
This deployment guide describes how to configure a Cisco Collaboration video network to interwork with a Microsoft
Lync environment, using the back to back user agent (B2BUA) on the Cisco TelePresence Video Communication
Server (VCS).
Lync environment, using the back to back user agent (B2BUA) on the Cisco TelePresence Video Communication
Server (VCS).
It also highlights the capabilities and limitations of interoperation of VCS and Lync.
To enable video calling, desktop sharing, and presence between VCS-registered video endpoints and Lync clients,
you need to configure:
you need to configure:
■
A neighbor zone between the Gateway VCS and the VCS Control
■
The Lync B2BUA on the Gateway VCS to route calls to Lync
■
Static routes from Lync to the Gateway VCS
■
The Presence Server and Presence User Agent on the VCS Control
Note:
Previous versions of this guide recommended an extended deployment, using FindMe to enhance presence and
provide what we term Single Number Reach (SNR). We consider that to be a legacy deployment, prefering Cisco
Unified Communications Manager products for SNR and presence, but we included the details in
Unified Communications Manager products for SNR and presence, but we included the details in
Deployment Scope
The following major VCS-based deployments are mutually exclusive. They cannot be implemented together on the
same VCS (or traversal pair):
same VCS (or traversal pair):
■
Mobile and Remote Access
■
Microsoft Lync Interoperability
■
Jabber Guest
What is the Gateway VCS and Why Should I Use It?
A Gateway VCS is a VCS Control (or cluster of VCS Controls) that provides interoperability between a Cisco
Collaboration network and the Microsoft Lync environment.
Collaboration network and the Microsoft Lync environment.
We require that you dedicate a VCS Control to this role so that you:
■
Minimize the impact of adding Lync interoperability to your existing Cisco Collaboration network.
■
Limit the number of VCSs that need the Microsoft Interoperability option key.
■
Reduce the number of static routes that you need to define from the Lync environment.
Each static route matches a single SIP domain to a single FQDN, or IP address, but you can create appropriate
DNS records to map this destination to a cluster of VCSs.
DNS records to map this destination to a cluster of VCSs.
■
Reduce the number of third-party applications that you configure Lync to trust.
Lync Server will only accept SIP messages from peers that it trusts. By dedicating a Gateway VCS (or cluster),
you reduce the number of trusted devices that you need to configure in Lync.
you reduce the number of trusted devices that you need to configure in Lync.
Recommendations
■
We recommend that you use TLS connectivity throughout the deployment. We do not recommend
TCP because:
TCP because:
4
Cisco VCS and Microsoft Lync Deployment Guide
Introduction