Cisco Cisco IPCC Web Option Leaflet

The link should preferably be a dedicated circuit and not be tunneled across the highly available 
(HA) WAN. See 

, at the beginning of the section on 

, for more information on path diversity.

A single link, shown in 

, carries both Unified ICM Central Controller Private traffic and 

VRU/CM PG Private traffic. Single-link implementations are more common and less costly than 
dual-link implementations.

Less costly than separate-link model.

Fewer links to maintain, but more complex.

The link does not have to be redundant. If a redundant link is used, however, latency on failover 
must not exceed 500 ms.

Separate QoS classifications and reserved bandwidth are required for Central Controller 
high-priority and PG high-priority communications. For details, see 

Link sizing and configuration must be examined before any major change to call load, call flow, or 
deployment configuration. This is especially important in the single-link model.

The link should preferably be a dedicated circuit fully isolated from, and not tunneled across, the 
highly available (HA) WAN. See 

, at the beginning of the section on 

, for more information on path diversity.

This section describes the behavior of clustering over the WAN for Unified CCE during certain failure 
situations. The stability of the highly available (HA) WAN is extremely critical in this deployment 
model, and failure of the highly available WAN is considered outside the bounds of what would normally 
happen.

For illustrations of the deployment models described in this section, refer to the figures shown 
previously for 

126029

ICM A

ICM B