Manual

Introduction
 The existing Video Network’s domain is vcs.domain, and can, if desired, also include devices
registering with the domain test-customer.com.
 Endpoints registered to the Video Network may be SIP or H.323 endpoints; they must register
with an ID in the format name@domain, where domain is a domain hosted on the Video Network
(for example vcs.domain, or if desired test-customer.com).
 MOC clients registered to OCS are identified by URIs, for example:
 Steve with a URI [e-mail]
 Mary with a URI [e-mail]
 Endpoints registered to the Video Network are identified by URIs, frequently including the location
of the endpoint, for example:
 Mary with an h.323 ID [e-mail]
 Mary with a SIP URI [e-mail]
 Steve with an H.323 ID [e-mail]
 Steve with a SIP URI [e-mail]
 When using OCS Relay functionality on Cisco VCS, together with OCS R2 or later:
 The “OCS gateway” Cisco VCS Control supports the test-customer.com domain for OCS
Relay FindMe™ users.
 OCS Relay FindMe™ user names are constructed in exactly the same way as OCS URIs, for
example:
 Steve with a URI [e-mail]
 Mary with a URI [e-mail]
 These OCS Relay FindMe™ users (with the same domain as OCS) register to OCS as
though they are MOC clients. If a corresponding MOC client also exists on a PC, the MOC
endpoint on the PC and the Video endpoints specified in the FindMe™ will ring
simultaneously when called, whether called from an endpoint communicating with Cisco
VCS, or whether called from an endpoint communicating with OCS.
 These OCS Relay FindMe™ users can specify single or multiple endpoints as primary
devices to call; the primary devices can be located anywhere in the Video network or be
accessible via the Video Network.
 “Available”, “off-line” and “in-call” presence may be observed by MOC clients for OCS Relay
FindMe™ users registered by the “OCS gateway” Cisco VCS (when OCS Relay is enabled).
“Available” and “off-line” presence may be observed by MOC clients for other devices or
FindMe™ users which provide presence information in the Video Network.
 It is assumed that the “OCS gateway” Cisco VCS Control is running X5 code (or later) and has at
least the following option keys applied:
 H323-SIP interworking
 Registrations
 Traversal calls
 Non-traversal calls
 User Policy (FindMe™) - optional but recommended; necessary to take advantage of the
OCS Relay functionality.
 Traversal call and non-traversal call option keys are both needed on the “OCS gateway” Cisco
VCS Control
 OCS to SIP calls that do not use encryption are non-traversal calls
 OCS to H.323 calls are traversal calls as they need to be interworked from SIP RTP to H.323
RTP
 The version of OCS must be Microsoft OCS 2007 version 3.0.6362.0 (OCS R1) or OCS R2.
 The version of operating system That OCS runs on must be Microsoft Server 2003, 2003 R2 or
2008. It must not be Microsoft Server 2008 R2.
 The version of MOC client must be the version distributed with OCS R1 or OCS R2.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 7 of 92