Manual

Introduction
Cisco VCS X4.2 or X4.3 and OCS R2
 Cisco VCS can be in:
 the same domain as OCS
 a separate domain from OCS
 the same and separate domains from OCS
 Same domain is used by FindMe™ entries on Cisco VCS, which register as MOC devices on
OCS (using OCS Relay):
 domain static route(s) are set up on OCS to route calls to Cisco VCS’s separate domain(s)
 a domain static route is set up on OCS to route calls to Cisco VCS’s same domain devices
(that are not OCS Relay FindMe™ entries)
 Presence is only supported Cisco VCS to OCS:
 “Off-line” and “Available” are “In-call” are supported for “same domain” OCS Relay FindMe™
users
 “Off-line” and “Available” (not “In-call”) are reported for “separate domain” users
 “Off-line” and “Available” (not “In-call”) are reported for “same domain” users which are not
OCS Relay FindMe™ users
 Passing MOC presence to devices registered to Cisco VCS is not supported.
 Same domain calls OCS to Cisco VCS can be made to “same domain” OCS Relay FindMe™
users and also to other devices with that domain which are routable from the “OCS gateway”
Cisco VCS.
 OCS accepts and handles call hold (and resume) requests.
 OCS MOC clients can be joined into a Multiway™ conference.
 OCS connecting to a cluster of Cisco VCSs is not supported when using OCS Relay; without OCS
Relay use of Cisco VCS clusters with OCS is only for resilience, not for capacity, as OCS does
not support the load balancing of calls to an attached cluster of devices.
 MOC devices registering through a Microsoft Edge Server and then calling Cisco VCS registered
endpoints is not supported:
 Cisco VCS registered devices calling OCS registered devices will work, but MOC devices
registering through an Edge server get no video if they call a Cisco VCS registered endpoint
 Calls to Microsoft Mediation Servers work from endpoints in the Cisco VCS Video Network for SIP
initiated calls, but do not work for interworked H.323 initiated calls.
 A single Cisco VCS can communicate to a pool of OCS FEPs via a hardware load balancer. OCS
systems may use hardware load balancers for resilience and capacity.
 A “lack of video on MOC” problem occurs due to MOC R2 clients not displaying video until a full
video frame has been received. A full frame is sent either when requested by a fast picture
update request, or when the video stream is paused and then re-started. MOC R2 does not
request fast picture updates.
 latest versions of endpoints recognize when they are connected in a SIP call to an OCS and
will send appropriate full frames to allow MOC to display video
 with Cisco VCS X4.2 and later, H.323 to OCS SIP interworked calls will also have periodic full
frames sent to ensure MOC gets video
 MCU code 3.1 and later recognizes when it is connected in a SIP call to an OCS and will
send appropriate full frames to allow MOC to display video
 third party SIP endpoints are unlikely to allow video to be displayed on MOC
Note: Although the Cisco TelePresence MCU can register directly to OCS R1, due to changes made
by Microsoft, the MCU cannot register directly to OCS R2.
To use an MCU with OCS R2, register the MCU to Cisco VCS; Cisco VCS handles the protocol
differences on behalf of the MCU.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 10 of 92