Cisco Cisco TelePresence Video Communication Server Expressway
The B2BUA can use the Cisco AM GW to transcode between standard codecs (such as H.264) and
Microsoft RT Video and RT Audio to allow high definition calls between Microsoft Lync 2010 clients and
Cisco endpoints.
Microsoft RT Video and RT Audio to allow high definition calls between Microsoft Lync 2010 clients and
Cisco endpoints.
Microsoft Lync 2013
The B2BUA provides interworking between standard H.264 AVC and Lync 2013's H.264UC SVC codec.
You can still configure the B2BUA to use Cisco AM GW transcoders with Lync 2013, but it is not necessary
and we recommend that they are not deployed with Lync 2013.
You can still configure the B2BUA to use Cisco AM GW transcoders with Lync 2013, but it is not necessary
and we recommend that they are not deployed with Lync 2013.
Lync 2013 no longer supports H.263, so X8.1 or later software is required to interoperate successfully with
Lync 2013. X7.2 or earlier software will work with Lync 2013 only if calls are routed through a Cisco AM GW
transcoder.
Lync 2013. X7.2 or earlier software will work with Lync 2013 only if calls are routed through a Cisco AM GW
transcoder.
The Microsoft Interoperability option key is required for all types of communication with Lync 2013.
Microsoft Lync B2BUA interoperating capabilities
When using the Microsoft Lync B2BUA:
n
Domain static routes are set up on Lync Server to route calls to domains in the video network.
n
Search rules are set up on VCS to route calls to Lync domains.
n
Lync Server accepts and handles call hold (and resume) requests.
n
Lync clients can be the object of a transfer (even if there is an AM gateway involved in the call).
n
Lync clients can be joined into a Multiway conference (even if there is an AM gateway involved in the call).
n
Presence updates are only supported from VCS to Lync Server:
l
Use of ‘Available’ for registered endpoints is optional via PUA configuration
l
“Off-line” and “Available” (not “In-call”, which requires FindMe-based configuration) are reported for users
(for up to 100 subscribers)
(for up to 100 subscribers)
n
Passing Lync presence to devices registered to VCS is not supported.
n
Calls to Microsoft Mediation Servers work from endpoints in the VCS video network for SIP initiated calls,
but do not work for calls interworked from H.323 (unless the workaround specified in
but do not work for calls interworked from H.323 (unless the workaround specified in
n
Lync systems may use hardware load balancers for resilience and capacity.
n
A “Lync gateway” VCS (or VCS cluster) can communicate to Lync via Lync Director.
n
Media encryption (SRTP) is supported when TLS is used between VCS and Lync and the Microsoft
Interoperability option key is added to the “Lync gateway” VCS.
Interoperability option key is added to the “Lync gateway” VCS.
n
SIP signaling and RTP media is always routed via the B2BUA application for calls involving Lync clients.
Each B2BUA application (one application per VCS) can handle 100 simultaneous calls between Lync and
the VCS video environment. However, a call involving Cisco AM GW will consume two B2BUA call
resources.
Each B2BUA application (one application per VCS) can handle 100 simultaneous calls between Lync and
the VCS video environment. However, a call involving Cisco AM GW will consume two B2BUA call
resources.
Summary of configuration objectives
This document describes how to configure Lync and the VCS in B2BUA mode to enable calls from:
n
SIP and H.323 video endpoints registered in the video network to other SIP and H.323 video endpoints
registered in that same video network.
registered in that same video network.
n
Microsoft Lync clients registered on Lync Server to other Lync clients registered on that Lync Server.
n
SIP and H.323 video endpoints registered in the video network to Lync clients registered on Lync.
n
Lync clients registered on Lync Server to SIP and H.323 video endpoints registered in the video network.
Microsoft Lync and Cisco VCS Deployment Guide (X8.1)
Page 9 of 76
Introduction