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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2 Deployment Models<br />

OL-8669-05<br />

IPT: Multi-Site with Distributed Call Processing<br />

Best Practices<br />

The <strong>Unified</strong> CCE Gateway PG, <strong>Cisco</strong> <strong>Unified</strong> CallManager cluster, <strong>Unified</strong> IP IVR, and System<br />

<strong>Unified</strong> CCE must be co-located at the contact center site.<br />

The communication link from the parent <strong>Unified</strong> ICM Central Controller to the <strong>Unified</strong> CCE<br />

Gateway PG must be sized properly and provisioned for bandwidth and QoS. (For details, refer to<br />

the chapter on Bandwidth Provisioning and QoS Considerations, page 11-1.)<br />

Gatekeeper-based call admission control could be used to reroute calls between sites over the PSTN<br />

when WAN bandwidth is not available. It is best to ensure that adequate WAN bandwidth exists<br />

between sites for the maximum amount of calling that can occur.<br />

If the communication link between the <strong>Unified</strong> CCE Gateway PG and the parent <strong>Unified</strong> ICM<br />

Central Controller is lost, then all contact center routing for calls at that site is put under control of<br />

the local System <strong>Unified</strong> CCE. <strong>Unified</strong> CVP-controlled ingress voice gateways would have<br />

survivability TCL scripts to redirect inbound calls to local <strong>Cisco</strong> <strong>Unified</strong> CallManager CTI route<br />

points, and the local <strong>Unified</strong> IP IVR would be used to handle local queue and treatment during the<br />

WAN outage. This is a major feature of the parent/child model to provide complete local<br />

survivability for the call center. For more information, see the chapter on Design Considerations for<br />

High Availability, page 3-1.<br />

While two intercluster call legs for the same call will not cause unnecessary RTP streams, two<br />

separate call signaling control paths will remain intact between the two clusters (producing logical<br />

hairpinning and reducing the number of intercluster trunks by two).<br />

Latency between parent <strong>Unified</strong> ICM Central Controllers and remote <strong>Unified</strong> CCE Gateway PGs<br />

cannot exceed 200 ms one way (400 ms round-trip).<br />

IVR: Distributed Voice Gateways with Treatment and Queuing Using<br />

<strong>Unified</strong> CVP<br />

This deployment model is the same as the previous model, except that <strong>Unified</strong> CVP is used instead of<br />

<strong>Unified</strong> IP IVR for call treatment and queuing. In this model, voice gateways with PSTN trunks<br />

terminate into each site. Just as in the centralized call processing model with distributed voice gateways,<br />

it might be desirable to limit the routing of calls to agents within the site where the call arrived (to reduce<br />

WAN bandwidth). Call treatment and queuing can also be achieved at the site where the call arrived,<br />

further reducing the WAN bandwidth needs. Figure 2-6 illustrates this model using traditional <strong>Unified</strong><br />

CCE deployment.<br />

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

2-23

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

Saved successfully!

Ooh no, something went wrong!