Cisco Cisco TelePresence Video Communication Server Expressway
MCUs for ad hoc conferences from Lync
The configuration of VCS and Cisco MCU described in Cisco TelePresence Multiway Deployment Guide is
the correct configuration for VCS and Cisco MCU when working with Lync Server. The MCU should be
configured to support SIP access to conferences to avoid the need to interwork the Lync client calls.
the correct configuration for VCS and Cisco MCU when working with Lync Server. The MCU should be
configured to support SIP access to conferences to avoid the need to interwork the Lync client calls.
MCUs must register to a VCS to allow Lync users to join conferences (MCUs cannot register to Lync Server;
the “Lync gateway” VCS handles the protocol differences on behalf of the MCU). We recommend that MCUs
that are used for conferences that Lync clients can dial, are registered using their own domain (different from
any other video or Lync domain) to the video network VCSs.
the “Lync gateway” VCS handles the protocol differences on behalf of the MCU). We recommend that MCUs
that are used for conferences that Lync clients can dial, are registered using their own domain (different from
any other video or Lync domain) to the video network VCSs.
When configured in their own domain, the MCU conferences can be accessible via a static route configured
on Lync for this MCU domain. If regional MCUs exist, the MCUs should have regional domains. For ad hoc
conferences routed via the Lync static domain route:
on Lync for this MCU domain. If regional MCUs exist, the MCUs should have regional domains. For ad hoc
conferences routed via the Lync static domain route:
n
If the conference is not underway presence status will be “Offline”.
n
If the conference has any participants, presence status will be “Available”.
Calling an MCU conference from a Lync device requires the MCU’s domain to be entered.
Note that:
n
If the PUA is configured so that registered devices do not report ‘Available’, presence will always show
“Off-line”.
“Off-line”.
n
VCS supports a maximum of 100 presence subscriptions per presentity.
Small test/demo networks
For small test and demo networks, video endpoints may be registered to the “Lync gateway” VCS, the small
video network being controlled by the same VCS that is the interface to Lync Server. (In this case, you need
to configure the SIP domains and enable the Presence Server on the “Lync gateway” VCS.)
video network being controlled by the same VCS that is the interface to Lync Server. (In this case, you need
to configure the SIP domains and enable the Presence Server on the “Lync gateway” VCS.)
Scaling up from a small test/demo network
As extra capacity, regional management and reduced license usage is required, you can scale away from the
‘small test and demo network’ system to the “Lync gateway” VCS connected to video network approach.
This is achieved by adding video network VCSs and neighboring them (directly, or indirectly through other
VCSs) to the “Lync gateway” VCS.
‘small test and demo network’ system to the “Lync gateway” VCS connected to video network approach.
This is achieved by adding video network VCSs and neighboring them (directly, or indirectly through other
VCSs) to the “Lync gateway” VCS.
Endpoints can be added to the video network VCSs and endpoints and other devices then gradually migrated
off the “Lync gateway” VCS onto the video network VCSs.
off the “Lync gateway” VCS onto the video network VCSs.
Features and capabilities
The interoperating capabilities of VCS and Microsoft Lync 2010 are broadly the same as between VCS and
Lync 2013 except where specified in this document. X8.1 or later is compatible with both Lync 2010 and Lync
2013 clients registered to either Lync 2010 or Lync 2013 front end servers. The main differences in features
and capabilities are summarized below.
Lync 2013 except where specified in this document. X8.1 or later is compatible with both Lync 2010 and Lync
2013 clients registered to either Lync 2010 or Lync 2013 front end servers. The main differences in features
and capabilities are summarized below.
Microsoft Lync 2010
The Microsoft Interoperability option key must be installed to enable encrypted calls to and from Microsoft
Lync 2010 Server (for both native SIP calls and calls interworked from H.323). It is also required by the
B2BUA when establishing ICE calls to Lync 2010 clients.
Lync 2010 Server (for both native SIP calls and calls interworked from H.323). It is also required by the
B2BUA when establishing ICE calls to Lync 2010 clients.
Cisco TelePresence Microsoft Lync and Cisco VCS Deployment Guide (X8.2)
Page 8 of 80
Introduction