Cisco Cisco TelePresence Video Communication Server Expressway
Introduction
Cisco VCS X5 or later and OCS R1
As in X4:
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):
OCS (using OCS Relay):
domain static route(s) are set up on OCS to route calls to Cisco VCS’s separate domain(s)
Presence is only supported Cisco VCS to OCS:
“Off-line” and “Available” and “In-call” are supported for “same domain” OCS Relay FindMe™
users
users
“Off-line” and “Available” (not “In-call”) are reported for “separate domain” users
Passing MOC presence to devices registered to Cisco VCS is not supported.
OCS does not accept call hold request - this means that MOC devices cannot be joined into a
Multiway conference.
Multiway conference.
MOC devices registering through a Microsoft Edge Server and then calling Cisco VCS registered
endpoints is not supported:
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
registering through an Edge server get no video if they call a Cisco VCS registered endpoint
Calls to Microsoft Mediation Servers from endpoints in the Cisco VCS video network is not
supported.
supported.
In H.323 / SIP interworking, Cisco VCS X4.2 and later code requests full picture updates to work
around a “lack of video on MOC” problem.
around a “lack of video on MOC” problem.
Plus:
OCS can be connected to a cluster of Cisco VCS peers.
Cisco VCS forces SIP encryption off on the OCS zone so that video endpoints do not need to
have encryption turned off.
have encryption turned off.
Subzones are no longer needed on the Cisco VCS control for locally registered endpoints.
Cisco VCS X5 or later and OCS R2
As in X4:
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):
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)
(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
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
OCS Relay FindMe™ users
Passing MOC presence to devices registered to Cisco VCS is not supported.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2
Page 11 of 92