Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS Deployment Guide: Microsoft OCS 2007 R2, Lync 2010 and Cisco VCS X7.0
Page 8 of 104
network.
If a corresponding MOC/Lync client also exists from a PC, the MOC/Lync client on the PC and the
video endpoints specified in the FindMe will ring simultaneously when called, whether called from
an endpoint communicating with Cisco VCS, or whether called from an endpoint communicating
with OCS/Lync.
If a corresponding MOC/Lync client also exists from a PC, the MOC/Lync client on the PC and the
video endpoints specified in the FindMe will ring simultaneously when called, whether called from
an endpoint communicating with Cisco VCS, or whether called from an endpoint communicating
with OCS/Lync.
“Available”, “off-line” and “in-call” presence may be observed by MOC/Lync clients for users and
MCU conferences associated with a FindMe account on the Cisco “OCS/Lync gateway” VCS
(B2BUA is enabled). Note: this requires that the primary video devices within the FindMe account
have a URI-based alias, for example firstname.lastname@domain.
MCU conferences associated with a FindMe account on the Cisco “OCS/Lync gateway” VCS
(B2BUA is enabled). Note: this requires that the primary video devices within the FindMe account
have a URI-based alias, for example firstname.lastname@domain.
MCUs that will receive calls from OCS/Lync can register conferences to the video network with a
dedicated MCU domain (mcu.ciscotp.com) and make these available to OCS/Lync users via a
FindMe account (suitable for static conference aliases), or by using a static SIP domain route from
the OCS/Lync environment (suitable for ad-hoc conference aliases). The reason for using a
separate domain for MCU registrations is to more easily prevent SIP traffic coming from
OCS/Lync via a static route from propagating further into the video network than needed (by using
search rules).
dedicated MCU domain (mcu.ciscotp.com) and make these available to OCS/Lync users via a
FindMe account (suitable for static conference aliases), or by using a static SIP domain route from
the OCS/Lync environment (suitable for ad-hoc conference aliases). The reason for using a
separate domain for MCU registrations is to more easily prevent SIP traffic coming from
OCS/Lync via a static route from propagating further into the video network than needed (by using
search rules).
“Available” and “off-line” presence may be observed by MOC/Lync clients for MCU conferences
where the conferences do not have associated FindMe user entries on the “OCS/Lync gateway”
VCS.
where the conferences do not have associated FindMe user entries on the “OCS/Lync gateway”
VCS.
Prerequisites
The “OCS/Lync gateway” VCS Control (cluster peers) must be running X7.0 code (or later)
The “OCS/Lync gateway” VCS Control (cluster peers) must have at least the following option keys
applied:
•
applied:
•
Non-traversal calls
•
User Policy (FindMe)
For OCS
•
•
The version of OCS must be Microsoft OCS 2007 R2
•
The operating system that OCS runs on must be Microsoft Server 2003, 2003 R2 or 2008. If
Microsoft Server 2008 R2 is to be used, the appropriate Microsoft patches must be applied to
allow OCS to run properly.
Microsoft Server 2008 R2 is to be used, the appropriate Microsoft patches must be applied to
allow OCS to run properly.
For Lync
•
•
The version of Lync must be Lync 2010.
•
The operating system that Lync runs on must be Microsoft Server 2008 SP2 64 bit or
Microsoft Server 2008 R2 64 bit.
Microsoft Server 2008 R2 64 bit.
The version of MOC client must be the version distributed with OCS R2.
The version of Lync client must be the version distributed with Lync 2010.
The version of Communicator for Mac client must be Communicator for Mac 2011.
Clustered “OCS/Lync Gateway” VCS Control
When this document refers to an “OCS/Lync gateway” VCS, a cluster of VCSs can also be used. The
operation is functionally the same, but there is more capacity available.
operation is functionally the same, but there is more capacity available.
To provide load balancing, the “OCS/Lync gateway” VCS peers will distribute the shared domain
FindMe users between themselves, and register their set with OCS/Lync server. When OCS/Lync
Server makes a call to one of these user IDs, the call will be presented to the VCS that made the
registration.
FindMe users between themselves, and register their set with OCS/Lync server. When OCS/Lync
Server makes a call to one of these user IDs, the call will be presented to the VCS that made the
registration.
Calls from OCS/Lync Server to VCS where there is no registration from VCS (e.g. for MCU calls) will
typically arrive at a single VCS in the cluster, as OCS/Lync Server will use the static domain route (set
typically arrive at a single VCS in the cluster, as OCS/Lync Server will use the static domain route (set