Manual

Introduction
 the “OCS gateway” Cisco VCS(s) also need to have 1 or more neighbor zones that contain
the Peer addresses of all the OCS FEPs.
 the Hardware Load Balancer neighbor zone is pointed to by the Search rule(s) that route calls
to OCS.
 the neighbor zones to the other FEPs must also have their Zone profile set to Microsoft Office
Communications Server 2007 but must not be referenced by any Search rules.
4. If OCS is a single FEP then the “OCS gateway” Cisco VCS(s) should be configured to route calls
for OCS to the single FEP directly, and receive calls from the FEP:
 configure the single FEP as the Peer address in the neighbor zone
For more details about OCS Director, see “Appendix 14 – Cisco VCS and Microsoft OCS Director’.
Prerequisites prior to configuring Cisco VCS and OCS to
interoperate
Before configuring the Video Network and the OCS system to interwork, make sure that the following
is operational:
 OCS is configured and operational and access is available to Active Directory for managing users.
 The FQDN of OCS (enterprisepool.test-customer.com in this example) is resolvable via the DNS
server that Cisco VCS Control is configured to use (often the DNS server on OCS).
 The FQDNs of each of the “OCS gateway” Cisco VCSs and the FQDN of the “OCS gateway”
cluster must be resolvable via the DNS server.
 The video endpoints registered to the Video Network must support the H.263 video codec – this is
the only video codec which is common to MOC clients and standard video endpoints.
 Validation of the Front End Servers on all OCS Directors and OCS FEPs must show no errors.
(Log into each OCS Director and each OCS FEP, select the Director or FEP, then select
Validation, select Front End Server and follow the wizard instructions.)
 If TLS is to be used (recommended) ensure that the DNS server supports reverse DNS lookup
(often supported using PTR records).
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 16 of 92