Cisco Cisco TelePresence Video Communication Server Expressway

다운로드
페이지 92
Introduction 
Introduction 
Objectives and intended audience 
This deployment guide provides instructions on how to configure a Cisco TelePresence Video 
Communication Server (Cisco VCS) Control version X5.2 and OCS (Microsoft OCS 2007 R1 or R2) to 
interwork. 
This guide also highlights the capabilities and limitations of interoperation of Cisco VCS Control and 
OCS. 
Note: For information about connecting Cisco VCS X3 or X4 to Microsoft OCS, see ‘Cisco VCS 
deployment guide - Microsoft OCS 2007 (R1 and R2) and Cisco VCS Control (X3 and X4) - 
D14269.01’. 
Deployment scenario 
A company is introducing an OCS system into their network to provide Microsoft Office Communicator 
(MOC) clients on everyone’s desk to supply messaging and presence capabilities for all staff. 
Integrating this with their existing Video Network, which handles their video conferencing, provides the 
ability for video endpoints to make calls to and receive calls from MOC clients, and for MOC clients to 
see the presence of the video endpoints. 
 
In this scenario, dialing will typically be carried out by users clicking on one of their buddies in MOC, or 
selecting a destination from an electronic address book on the video endpoint. 
This deployment guide describes how to connect OCS and a Cisco VCS Control using a SIP trunk 
across an IP network. The example presented uses the following setup: 
 
A new Cisco VCS Control (or cluster of Cisco VCS control peers) – the “OCS gateway” – to act as 
the link between the existing Video Network and OCS. 
 
The OCS’s SIP domain is test-customer.com
Note: the SIP domain for OCS need not be the same as the AD domain of MOC users (the MOC 
user’s login domain – used in the login user name - may be different from the SIP domain – used in 
the sign-in address.) 
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 
Page 6 of 92