Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.1
Page 12 of 104
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 (for up to 100 subscribers)
FindMe users (for up to 100 subscribers)
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.
Configuring VCS versions prior to X7.0
To configure VCS versions prior to VCS X7.0, use the appropriate deployment guide:
Cisco TelePresence Video Communication Server Microsoft Lync 2010 Deployment Guide (X6.1)
Cisco TelePresence Video Communication Server Microsoft OCS 2007 R1 and R2 Deployment
Guide (X5.2)
Guide (X5.2)
Summary of configuration process
This document describes how to configure the OCS R2, Lync 2010 and the Cisco VCS Control version
X7.x in B2BUA mode so that calls can be made from:
X7.x in B2BUA mode so that calls can be made from:
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.
endpoints registered in that same video network.
Microsoft Office Communicator (MOC) clients / Lync clients registered on OCS/Lync server to
other MOC/Lync clients registered on that OCS/Lync server.
other MOC/Lync clients registered on that OCS/Lync server.
SIP and H.323 video endpoints registered in the video network to MOC/Lync clients registered on
OCS/Lync.
OCS/Lync.
MOC/Lync clients registered on OCS/Lync server to SIP and H.323 video endpoints registered in
the video network.
the video network.
It also describes how to enable presence so that MOC/Lync clients can see the presence status of
endpoints registered in the video network.
endpoints registered in the video network.
The configuration process describes each of these stages separately, so that individual stages can be
implemented and tested before moving on to the next.
implemented and tested before moving on to the next.