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.

Cluster Sizing Concepts<br />

10-2<br />

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

Chapter 10 Sizing <strong>Cisco</strong> <strong>Unified</strong> CallManager 4.x and 5.x Servers<br />

Once you have completed these tasks, you can begin to accurately size the necessary <strong>Cisco</strong> <strong>Unified</strong><br />

CallManager cluster(s). Many factors impact the sizing of a <strong>Cisco</strong> <strong>Unified</strong> CallManager cluster, and the<br />

following list mentions some of those factors:<br />

Number of office phones and the busy hour call attempt (BHCA) rate per phone<br />

Number of inbound agent phones and the BHCA rate per phone<br />

Number of CTI ports and the BHCA rate on those VoIP endpoints (can be zero if CVP is used for<br />

call treatment, self service, and queueing)<br />

Number of voice gateway ports and the BHCA rate on those VoIP endpoints<br />

Number of outbound agent phones, outbound dialing mode, and BHCA rate per phone<br />

The number of outbound dialer ports, number of IVR ports for outbound campaigns, and the BHCA<br />

rate per port for both<br />

The number of mobile agents and the BHCA rate per mobile agent<br />

Number of voicemail ports and the BHCA rate to those VoIP endpoints<br />

Signaling protocol(s) used by the VoIP endpoints<br />

Percent of agent call transfers and conferences<br />

Dial plan size and complexity, including the number of dialed numbers, lines, partitions, calling<br />

search spaces, locations, regions, route patterns, translations, route groups, hunt groups, pickup<br />

groups, route lists, and so forth<br />

Amount of media resources needed for functions such as transcoding, conferences, encryption, and<br />

so forth<br />

Co-resident applications and services such Auto Attendant, CTI Manager, E-911, and Music On<br />

Hold<br />

<strong>Cisco</strong> <strong>Unified</strong> CallManager release (sizing will vary per release)<br />

Desired hardware server model (sizing will vary per hardware server model)<br />

Other factors can affect cluster sizing, but the above list shows the most significant factors in terms of<br />

resource consumption.<br />

The general process to sizing a <strong>Cisco</strong> <strong>Unified</strong> CallManager cluster is to estimate the resource<br />

consumption (CPU, memory, and I/O) for each of these factors and then to choose hardware that will<br />

satisfy the resource requirements.<br />

It is important to gather information with regards to the factors listed above before attempting to size a<br />

cluster with any accuracy. To assist in calculating these numbers that relate to <strong>Unified</strong> CCE, <strong>Cisco</strong><br />

recommends using the <strong>Unified</strong> CCE Resource Calculators, discussed in the chapter on Sizing Call<br />

<strong>Center</strong> Resources, page 8-1.<br />

In prior releases of the <strong>Cisco</strong> <strong>Unified</strong> CallManager software, <strong>Cisco</strong> utilized various schemes to calculate<br />

the capacity of a cluster using device weights, BHCA multipliers, and dial-plan weights. With <strong>Cisco</strong><br />

<strong>Unified</strong> CallManager Releases 4.x, 5.x, and later, these approaches have been replaced by the <strong>Cisco</strong><br />

<strong>Unified</strong> CallManager Capacity Tool to allow for more accurate planning of the system. The next section<br />

describes the <strong>Cisco</strong> <strong>Unified</strong> CallManager Capacity Tool.<br />

OL-8669-05

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

Saved successfully!

Ooh no, something went wrong!