Cisco Cisco IPCC Web Option Design Guide
2-30
Cisco Unified Contact Center Enterprise 7.0, 7.1, and 7.2 SRND
OL-8669-16
Chapter 2 Deployment Models
IPT: Clustering Over the WAN
Figure 2-12
Network Architecture Based on a SONET Ring Under Normal Operations
•
The highly available (HA) WAN between the central sites must be fully redundant with no single
point of failure. (For information regarding site-to-site redundancy options, refer to the WAN
infrastructure and QoS design guides available at
point of failure. (For information regarding site-to-site redundancy options, refer to the WAN
infrastructure and QoS design guides available at
) In case of
partial failure of the highly available WAN, the redundant link must be capable of handling the full
central-site load with all QoS parameters. For more information, see the section on
central-site load with all QoS parameters. For more information, see the section on
•
A highly available (HA) WAN using point-to-point technology is best implemented across two
separate carriers, but this is not necessary when using a ring technology.
separate carriers, but this is not necessary when using a ring technology.
•
Latency requirements across the highly available (HA) WAN must meet the current Cisco Unified
Communications requirements for clustering over the WAN. Currently, a maximum latency of 40 ms
one way (80 ms round-trip) is allowed with Unified CM 6.1 or later releases. With prior versions of
Unified CM, the maximum latency is 20 ms one way. For full specifications, refer to the Cisco
Unified Communications Solution Reference Network Design (SRND) guide, available at
Communications requirements for clustering over the WAN. Currently, a maximum latency of 40 ms
one way (80 ms round-trip) is allowed with Unified CM 6.1 or later releases. With prior versions of
Unified CM, the maximum latency is 20 ms one way. For full specifications, refer to the Cisco
Unified Communications Solution Reference Network Design (SRND) guide, available at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_g
uides_list.html
uides_list.html
•
Unified CCE latency requirements can be met by conforming to Cisco Unified Communications
requirements. However, the bandwidth requirements for Unified CM intra-cluster communications
differ between Unified CCE and Cisco Unified Communications. For more information, see the
section on
requirements. However, the bandwidth requirements for Unified CM intra-cluster communications
differ between Unified CCE and Cisco Unified Communications. For more information, see the
section on
•
Bandwidth requirements across the highly available (HA) WAN include bandwidth and QoS
provisioning for (see
provisioning for (see
–
Unified CM intra-cluster communication signaling (ICCS)
–
Communications between Unified ICM Central Controllers
–
Communications between Unified ICM Central Controller and PG
–
Communications between CTI Object Server (CTI OS) and CTI Server, if using CTI OS
•
Separate dedicated link(s) for Unified ICM private communications are recommended between
Unified ICM Central Controllers Side A and Side B and between PGs Side A and Side B to ensure
path diversity. Path diversity is required due to the architecture of Unified ICM. Without path
diversity, the possibility of a dual (public communication and private communication) failure exists.
If a dual failure occurs even for a moment, Unified ICM instability and data loss can occur, including
the corruption of one Logger database.
Unified ICM Central Controllers Side A and Side B and between PGs Side A and Side B to ensure
path diversity. Path diversity is required due to the architecture of Unified ICM. Without path
diversity, the possibility of a dual (public communication and private communication) failure exists.
If a dual failure occurs even for a moment, Unified ICM instability and data loss can occur, including
the corruption of one Logger database.
•
The separate private link(s) may be either two links (one for Central Controller private traffic and
one for Unified CM PG private traffic) or one converged link containing both Central Controller and
PG private traffic. See
one for Unified CM PG private traffic) or one converged link containing both Central Controller and
PG private traffic. See
, for
more information.
ICM public +
Unified CM traffic
ICM public +
Unified CM traffic
188808
Sonet
Ring
ICM private
ICM private