Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.0
Page 12 of 104
•
Latest versions of Cisco endpoints registering to a VCS recognize when they are connected
in a SIP call to a MOC and will send appropriate full frames to allow MOC to display video.
(The detection is for MOC, and does not work for Lync clients.)
in a SIP call to a MOC and will send appropriate full frames to allow MOC to display video.
(The detection is for MOC, and does not work for Lync clients.)
•
MCU code 3.1 and later recognizes when it is connected in a SIP call to a MOC and will send
appropriate full frames to allow MOC to display video.
(The detection is for MOC, and does not work for Lync clients.)
appropriate full frames to allow MOC to display video.
(The detection is for MOC, and does not work for Lync clients.)
•
H.323 to OCS SIP interworked calls periodically send full frames sent to ensure MOC gets
video.
(The detection is for MOC, and does not work for Lync clients.)
video.
(The detection is for MOC, and does not work for Lync clients.)
•
Third-party SIP endpoints are unlikely to allow video to be displayed on MOC or Lync clients.
Note: Although the Cisco TelePresence MCU could register directly to OCS R1, due to changes
made by Microsoft, the MCU cannot register directly to OCS R2 or Lync server.
To use an MCU with OCS R2 / Lync server, register the MCU to Cisco VCS; Cisco “OCS/Lync
gateway” VCS handles the protocol differences on behalf of the MCU.
made by Microsoft, the MCU cannot register directly to OCS R2 or Lync server.
To use an MCU with OCS R2 / Lync server, register the MCU to Cisco VCS; Cisco “OCS/Lync
gateway” VCS handles the protocol differences on behalf of the MCU.
VCS X7.0 or later with B2BUA enabled and OCS R2 / Lync 2010
As Cisco VCS X5.x, X6.x and X7.x (non B2BUA mode), plus:
Lync is supported
“OCS/Lync gateway” VCS can register FindMe users (in a single OCS/Lync domain) as
MOC/Lync clients onto the OCS/Lync Server (using B2BUA FindMe registration)
MOC/Lync clients onto the OCS/Lync Server (using B2BUA FindMe registration)
MOC/Lync clients can be the object of a transfer even when there is an AM gateway involved in
the call.
the call.
MOC/Lync clients can be joined into a Multiway conference even when there is an AM gateway
involved in the call.
involved in the call.
Presence updates are only supported from Cisco VCS to OCS/Lync Server:
•
•
“Off-line”, “Available” and “In-call” are supported for B2BUA registered FindMe users
•
Use of ‘Available’ for registered endpoints is optional via PUA configuration
•
“Off-line” and “Available” (not “In-call”) are reported for users which are not B2BUA
registered FindMe users
registered FindMe users
OCS/Lync server connecting to a cluster of Cisco VCSs is supported when using B2BUA FindMe
registration.
•
registration.
•
The B2BUA share the registrations across the Cisco VCS peers so that calls to video
endpoints will be distributed across the VCS peers. If any peer(s) go out of service, the
remaining active peers will take over the registrations of the unavailable peers.
endpoints will be distributed across the VCS peers. If any peer(s) go out of service, the
remaining active peers will take over the registrations of the unavailable peers.
•
For non-“B2BUA registered FindMe users” clustering provides resilience but not load sharing.
This is because OCS/Lync does not support the load balancing of calls to an attached cluster
of devices – it routes all calls to the destination of the domain static route, and if that is a
Round-Robin DNS it will send to the one VCS until it loses connection to that VCS; only then
will it change to using a different VCS in the cluster.
This is because OCS/Lync does not support the load balancing of calls to an attached cluster
of devices – it routes all calls to the destination of the domain static route, and if that is a
Round-Robin DNS it will send to the one VCS until it loses connection to that VCS; only then
will it change to using a different VCS in the cluster.
Calls through Microsoft Edge server are supported (requires Enhanced OCS Collaboration
option key and a VCS Expressway).
option key and a VCS Expressway).
When running in B2BUA mode, SIP signaling and RTP media is always routed via the B2BUA
application for calls involving MOC/Lync clients. Each B2BUA application (one application per
VCS) can handle 50 simultaneous calls between OCS/Lync and the VCS video environment.
application for calls involving MOC/Lync clients. Each B2BUA application (one application per
VCS) can handle 50 simultaneous calls between OCS/Lync and the VCS video environment.
The “lack of video on MOC/Lync client” problem due to it not requesting appropriate full frame
updates is removed as the B2BUA initiates the requests on behalf of the MOC/Lync client.
updates is removed as the B2BUA initiates the requests on behalf of the MOC/Lync client.
OCS Relay functionality is now incorporated into the B2BUA as the “Register FindMe users as clients
on OCS/Lync” which means that no OCS/Lync-specific user-supplied CPL is required.
on OCS/Lync” which means that no OCS/Lync-specific user-supplied CPL is required.