Manual
Introduction
OCS should be configured so that:
1. If the OCS system is fronted by a Hardware Load Balancer in front of OCS Directors then calls to
and from the video network will go via the Directors; they will not be routed directly to or from the
FEPs:
OCS Directors should trust the “OCS gateway” Cisco VCS(s)
OCS Directors should route Video network SIP domain(s) (and the OCS SIP domain) to the
“OCS gateway” Cisco VCS cluster FQDN (or if only a single Cisco VCS, the FQDN of that
Cisco VCS)
FEPs will route traffic that they don’t know how to route to Director, and Director will route the
calls to the Cisco VCS.
2. If the OCS system is fronted by a single OCS Director then calls to and from the video network
will go via that Director; they will not be routed directly to or from the FEPs:
OCS Director should trust the “OCS gateway” Cisco VCS(s)
OCS Director should route Video network SIP domain(s) (and the OCS SIP domain) to the
“OCS gateway” Cisco VCS cluster FQDN (or if only a single Cisco VCS, the FQDN of that
Cisco VCS)
FEPs will route traffic that they don’t know how to route to Director, and Director will route the
calls to the Cisco VCS.
3. If the OCS system has no OCS Director but a Hardware Load Balancer in front of Front End
Processor pool(s) then configure the pool(s) (not each FEP) to route calls for the video network
directly to The “OCS gateway” Cisco VCS(s) – configuring the pool ensures that the same
configuration is applied to every FEP in the pool:
The FEP pools should trust the “OCS gateway” Cisco VCS(s)
All FEP pools should route calls to the “OCS gateway” Cisco VCS cluster FQDN (or if only a
single Cisco VCS, the FQDN of that Cisco VCS)
4. If OCS is a single FEP then that FEP should be configured to route calls for the Video Network
directly to the “OCS gateway” Cisco VCS(s):
the single FEP should trust the “OCS gateway” Cisco VCS(s)
the single FEP should route calls to the “OCS gateway” Cisco VCS cluster FQDN (or if only a
single Cisco VCS, the FQDN of that Cisco VCS)
Cisco VCS should be configured such that:
1. If the OCS system is fronted by a Hardware Load Balancer in front of OCS Directors then the
“OCS gateway” Cisco VCS(s) should be configured to route calls for OCS through the Hardware
Load Balancer in front of the OCS Directors, and receive calls from either of the OCS Directors:
the “OCS gateway” Cisco VCS(s) need to neighbor to the Hardware Load Balancer.
the “OCS gateway” Cisco VCS(s) also need to have another neighbor zones that contain the
Peer addresses of both OCS Directors.
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.
2. If the OCS system is fronted by an OCS Director then the “OCS gateway” Cisco VCS(s) should be
configured to route calls for OCS through the OCS Director, and receive calls from the OCS
Director:
configure the OCS Director as the Peer address in the neighbor zone
3. If the OCS system has no OCS Director but a Hardware Load Balancer in front of Front End
Processors then the “OCS gateway” Cisco VCS(s) should be configured to route calls for the
Video Network directly to the Hardware Load Balancer, and receive calls from any of the FEPs:
the “OCS gateway” Cisco VCS(s) need to neighbor to the Hardware Load Balancer.
Cisco VCS Deployment Guide: Microsoft OCS 2007 R1 and R2 and Cisco VCS X5.2 Page 15 of 92