Cisco Cisco IP Contact Center Release 4.6.2 Design Guide
10-2
Cisco Unified Contact Center Enterprise 7.0, 7.1, and 7.2 SRND
OL-8669-16
Chapter 10 Sizing Unified CCE Components and Servers
Sizing Considerations for Unified CCE
Sizing Considerations for Unified CCE
This section discusses the following Unified CCE sizing considerations:
•
•
•
•
Core Unified CCE Components
When sizing Unified CCE deployments, Cisco Unified Communications components are a critical factor
in capacity planning. Good design, including multiple Cisco Unified Communications Managers and
clusters, must be utilized to support significant call loads. For additional information on Cisco Unified
Communications Manager (Unified CM) capacity and sizing of Cisco Unified Communications
components, refer to
in capacity planning. Good design, including multiple Cisco Unified Communications Managers and
clusters, must be utilized to support significant call loads. For additional information on Cisco Unified
Communications Manager (Unified CM) capacity and sizing of Cisco Unified Communications
components, refer to
, and to the
latest version of the Cisco Unified Communications Solution Reference Network Design (SRND) guide
available at
available at
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guides
_list.html
_list.html
Additionally, because of varying agent and skill group capacities, proper sizing of the CTI OS and Cisco
Agent Desktop servers should be considered together with the Cisco Unified Communications
components.
Agent Desktop servers should be considered together with the Cisco Unified Communications
components.
Finally, the remaining Unified ICM components, while able to scale extremely well, are affected by
specific configuration element sizing variables that also have an impact on the system resources. These
factors, discussed in this section, must be considered and included in the planning of any deployment.
specific configuration element sizing variables that also have an impact on the system resources. These
factors, discussed in this section, must be considered and included in the planning of any deployment.
Note
Unless otherwise explicitly noted, the capacity information presented in
,
,
,
specifies capacity for inbound calls only.
The information presented in
,
,
, and
does not apply equally to all implementations of Unified CCE. The data is based on testing
in particular scenarios, and it represents the maximum allowed configuration. This data, along with the
sizing variables information in this chapter, serves only as a guide. As always, you should be
conservative when sizing and should plan for growth.
sizing variables information in this chapter, serves only as a guide. As always, you should be
conservative when sizing and should plan for growth.
Note
Sizing considerations are based upon capacity and scalability test data. Major Unified ICM software
processes were run on individual servers to measure their specific CPU and memory usage and other
internal system resources. Reasonable extrapolations were used to derive capacities for co-resident
software processes and multiple CPU servers. This information is meant as a guide for determining when
Unified ICM software processes can be co-resident within a single server and when certain processes
need their own dedicated server.
processes were run on individual servers to measure their specific CPU and memory usage and other
internal system resources. Reasonable extrapolations were used to derive capacities for co-resident
software processes and multiple CPU servers. This information is meant as a guide for determining when
Unified ICM software processes can be co-resident within a single server and when certain processes
need their own dedicated server.
assumes that the deployment scenario includes two fully
redundant servers that are deployed as a duplexed pair.