Cisco Cisco TelePresence Video Communication Server Expressway

Introduction 

The versions of software (Cisco VCS X3 or X4, and OCS R1 or R2 / standard, enterprise) affect the 
capabilities of the deployed system. 

Cisco VCS works equally well with OCS Standard edition and OCS Enterprise edition. 

 

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) 

 

Presence is only supported Cisco VCS to OCS 
 

“Off-line” and “Available” and “In-call” are supported for “same domain” OCS Relay FindMe™ 
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. 

 

Same domain calls OCS to Cisco VCS can only be made to “same domain” OCS Relay FindMe™ 
users. 

 

OCS does not accept call hold request - this means that MOC devices cannot be joined into a 
Multiway conference. 

 

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 from endpoints in the Cisco VCS Video Network are not 
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. 

Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 

Page 9 of 92