Cisco Cisco TelePresence Video Communication Server Expressway

Appendix 12 – Cisco TelePresence MCU configuration 

When using OCS R1, MCUs can be configured to register to Cisco VCS or can be configured to 
register directly with OCS R1. 

With the changes Microsoft introduced in OCS R2, which include the use of multi-part mime, MCUs 
can not accept OCS R2 calls directly. Cisco VCS however contains the smarts to convert OCS R2 
messaging into a format that the MCUs can handle. 

Therefore for OCS R2 and beyond, MCUs must be registered to Cisco VCS in order for MOC callers 
to be able to join conferences. 

When using Cisco VCS to route MOC calls to an MCU, the MCU should be configured to support SIP 
access to conferences. Cisco VCS should also be configured to keep MOC calls in native SIP where 
possible. Although Cisco VCS will handle media and signaling conversion for SIP to H.323 calls, Cisco 
VCS does not convert RFC 2833 DTMF to H.323 DTMF signaling. 

When OCS Relay is used, FindMe™ accounts can be set up for static conferences (for example if the 
In-Call presence status of the conference is wanted). For Ad hoc conferences (for example those 
created and used by Multiway™), a static route to the MCU’s domain must be set up in order that calls 
can be routed to non FindMe™ destinations. 

The configuration of both the Cisco VCS and the MCU documented in the ‘Cisco VCS Multiway™ 
deployment guide’ is the correct configuration for Cisco VCS and MCU when working with OCS. 
Please see that document for further details. 

Ensure that OCS has a static domain route to the MCU’s domain. 
 

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

Page 85 of 92