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.

Bandwidth Provisioning<br />

11-18<br />

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

Chapter 11 Bandwidth Provisioning and QoS Considerations<br />

<strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP PG to <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP<br />

At this time, no tool exists that specifically addresses communication between the <strong>Unified</strong> IP IVR or<br />

<strong>Unified</strong> CVP PG and the <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP. However, the tool mentioned in the previous<br />

section produces a fairly accurate measurement of bandwidth needed for this communication.<br />

Bandwidth consumed between the <strong>Unified</strong> ICM Central Controller and <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP<br />

PG is very similar to the bandwidth consumed between the <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP PG and the<br />

<strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP.<br />

The tool is available to <strong>Cisco</strong> partners and <strong>Cisco</strong> employees at<br />

http://www.cisco.com/partner/WWChannels/technologies/resources/IPCC_resources.html<br />

If the <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP PGs are split across the WAN, total bandwidth required would be<br />

double what the tool reports: once for <strong>Unified</strong> ICM Central Controller to <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP<br />

PG and once for <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP PG to <strong>Unified</strong> IP IVR or <strong>Unified</strong> CVP.<br />

CTI Server to CTI OS<br />

The worst case for bandwidth utilization across the WAN link between the CTI OS and CTI Server<br />

occurs when the CTI OS is remote from the CTI Server. A bandwidth queue should be used to guarantee<br />

availability for this worst case.<br />

For this model, the following simple formula can be used to compute worst-case bandwidth<br />

requirements:<br />

With no Extended Call Context (ECC) or Call Variables:<br />

BHCA ∗ 20 = bps<br />

With ECC and/or Call Variables<br />

BHCA ∗ (20 + ((Number of Variables ∗ Average Variable Length) / 40) = bps<br />

Example: With 10,000 BHCA and 20 ECC variables with average length of 40 bits:<br />

10,000 ∗ (20 + ((20 ∗ 40) / 40) = 10,000 ∗ 40 = 400,000 bps = 400 kbps<br />

<strong>Cisco</strong> <strong>Unified</strong> CallManager Intra-Cluster Communications (ICC)<br />

The <strong>Cisco</strong> <strong>Unified</strong> Communications <strong>Solution</strong> <strong>Reference</strong> Network Design (SRND) guide states that<br />

900 kbps must be reserved for every 10,000 BHCA. This amount is significantly higher with <strong>Unified</strong><br />

CCE due to the number of call redirects and additional CTI/JTAPI communications encompassed in the<br />

intra-cluster communications.<br />

The bandwidth that must be reserved is approximately 2,000 kbps (2 Mbps) per 10,000 BHCA. This<br />

requirement assumes proper design and deployment based on the recommendations in this <strong>Unified</strong> CCE<br />

design guide. Inefficient design (such as “ingress calls to Site 1 are treated in Site 2”) will cause<br />

additional intra-cluster communications, possibly exceeding the defined requirements.<br />

More specifically, you can use the following formula to calculate the required bandwidth:<br />

Link Size BHCA ∗ 200 = bps<br />

OL-8669-05

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

Saved successfully!

Ooh no, something went wrong!