Manual

Enabling endpoints registered on the video network to call MOC clients registered on OCS
OCS configuration
The configuration will vary depending upon the architecture of the OCS installation.
 If an OCS Director is in use then configure the OCS Director (pool) to trust the “OCS Gateway”
Cisco VCS and to route traffic to Cisco VCS. (Other FEPs receiving calls for the Video domain
will not know how to route them, so will pass the calls to the Director for routing.)
 If there is just a hardware load balancer in front of a set of FEP pools, configure each FEP
pool.
 If there is just a single FEP, configure it.
To allow the “OCS gateway” Cisco VCS to communicate with OCS:
1. For a TLS (encrypted signaling) connection between the “OCS gateway” Cisco VCS and OCS
(recommended):
 TLS must be allowed on OCS
For a TCP connection (not recommended):
 TCP must be allowed on OCS
2. Configure OCS to trust the “OCS gateway” Cisco VCS(s).
3. Configure Static Route(s) to route calls to the “OCS gateway” Cisco VCS(s).
4. Configure OCS to make media encryption optional.
Allow (M)TLS or TCP connection to OCS
MTLS or TCP is configured on each OCS Director, or Each FEP – whichever the Cisco VCS
communicates directly with.
On OCS, for all OCS Directors, or FEPs:
1. Select Start > Administrative Tools > Office Communications Server 2007.
2. Select the specific OCS.
 If an OCS Director is available, then select the OCS Director (pool)
 otherwise, if a Hardware Load Balancer front ends multiple FEPs select and configure each
FEP in turn
 otherwise, if there is just one FEP, right-click on that one
For example if using Standard Edition Servers:
a. Expand Standard Edition Servers.
b. Expand OCS Pool for example, codian-hah1mccs or director.
c. If FEPs are being configured, right click on the FEP, e.g. codian-
hah1mccs.ocs2007.lcs.codian.com and choose Properties > Front End Properties.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 35 of 92