Cisco Unified Contact Center Enterprise Solution Reference ...

IPT: Clustering Over the WAN
2-32
Cisco Unified Contact Center Enterprise 7.x SRND
Chapter 2 Deployment Models
Best Practices
Distributed gateways require minimal additional remote maintenance and administration over
centralized gateways.
The media server for Unified CVP may be centrally located or located at the agent site. Media may
also be run from gateway flash. Locating the media server at the agent site reduces bandwidth
requirements but adds to the decentralized model.
Site-to-Site Unified ICM Private Communications Options
Unified ICM private communications must travel on a separate path from the public communications
between Unified ICM components. There are two options for achieving this path separation: dual and
single links.
Unified ICM Central Controller Private and Cisco Unified CallManager PG Private Across Dual Links
Dual links, shown in Figure 2-11, separate Unified ICM Central Controller Private traffic from VRU/CM
PG Private traffic.
Figure 2-11 Unified ICM Central Controller Private and Cisco Unified CallManager PG Private Across
Dual Links
Site 1 Site 2
ICM A
PG A
ICM B
PG B
126028
Advantages
Failure of one link does not cause both the Unified ICM Central Controller and PG to enter simplex
mode, thus reducing the possibility of an outage due to a double failure.
The QoS configuration is limited to two classifications across each link, therefore links are simpler
to configure and maintain.
Resizing or alterations of the deployment model and call flow might affect only one link, thus
reducing the QoS and sizing changes needed to ensure proper functionality.
Unanticipated changes to the call flow or configuration (including misconfiguration) are less likely
to cause issues across separate private links.
Best Practices
The links must be across separate dedicated circuits. The links, however, do not have to be redundant
and must not fail-over to each other.
Link sizing and configuration must be examined before any major change to call load, call flow, or
deployment configuration
OL-8669-05