19.07.2013 Views

Cisco Unified Contact Center Enterprise Solution Reference ...

Cisco Unified Contact Center Enterprise Solution Reference ...

Cisco Unified Contact Center Enterprise Solution Reference ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 2 Deployment Models<br />

OL-8669-05<br />

IPT: Clustering Over the WAN<br />

The link must be a dedicated circuit and not be tunneled across the highly available (HA) WAN. See<br />

Best Practices, page 2-27, at the beginning of the section on IPT: Clustering Over the WAN, page<br />

2-27, for more information on path diversity.<br />

<strong>Unified</strong> ICM Central Controller Private and <strong>Cisco</strong> <strong>Unified</strong> CallManager PG Private Across Single<br />

Link<br />

A single link, shown in Figure 2-12, carries both <strong>Unified</strong> ICM Central Controller Private traffic and<br />

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

dual-link implementations.<br />

Figure 2-12 <strong>Unified</strong> ICM Central Controller Private and <strong>Cisco</strong> <strong>Unified</strong> CallManager PG Private Across<br />

Single Link<br />

Site 1 Site 2<br />

PG A<br />

ICM A<br />

ICM B<br />

PG B<br />

Advantages<br />

Less costly than separate-link model.<br />

Fewer links to maintain, but more complex.<br />

Best Practices<br />

The link does not have to be redundant. If a redundant link is used, however, latency on failover must<br />

not exceed 500 ms.<br />

Separate QoS classifications and reserved bandwidth are required for Central Controller<br />

high-priority and PG high-priority communications. For details, see Bandwidth Provisioning and<br />

QoS Considerations, page 11-1.<br />

Link sizing and configuration must be examined before any major change to call load, call flow, or<br />

deployment configuration. This is especially important in the single-link model.<br />

The link must be a dedicated circuit fully isolated from, and not tunneled across, the highly available<br />

(HA) WAN. See Best Practices, page 2-27, at the beginning of the section on IPT: Clustering Over<br />

the WAN, page 2-27, for more information on path diversity.<br />

Clustering Over the WAN with <strong>Unified</strong> CCE System PG<br />

126029<br />

Clustering over the WAN using the <strong>Unified</strong> CCE System PG looks similar to clustering over the WAN<br />

with <strong>Unified</strong> IP IVR, but it has an additional set of challenges. Instead of using separate peripherals for<br />

each of the <strong>Unified</strong> IP IVRs, the single <strong>Unified</strong> CCE System peripheral is controlling all of the<br />

<strong>Unified</strong> IP IVRs and the <strong>Cisco</strong> <strong>Unified</strong> CallManager.<br />

<strong>Cisco</strong> <strong>Unified</strong> <strong>Contact</strong> <strong>Center</strong> <strong>Enterprise</strong> 7.x SRND<br />

2-33

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!