Release Note

Cisco Unified ICM/Contact Center Enterprise & Hosted Editions, Release 7.5,

Hardware and System Software Specification

For example, if the Cisco HDS is sized at 1GB for 8 weeks of storage and the customer wishes to retain data for 52 weeks,

the formula would then be:

4 * 1GB * 52/8 = 26GB

Network Recommendations

LAN – CCMP systems should be connected to ICM and other servers via gigabit (1000 Base-T) connections.

WAN – CCMP systems connecting to ICM or a distributed CCMP deployment across a WAN should be allocated a

dedicated link of at least 1.5 Mbps capacity.

Load Balancing – Distributed CCMP Systems may use a Load Balancer to distribute load across the sites. We recommend

that this is done using a dedicated Load Balancer, rather than using Windows built-in functionality.

6.5 Unified ICM Enterprise

This section assists you in selecting hardware servers for Unified ICM Enterprise, including new deployments and

technology refresh as well as common ground upgrade.

6.5.1 Note on Agent Capacity

Agent capacity numbers are based on the assumption that 'Enable agent reporting' is unchecked on the Agent

Distribution tab for the PG configuration (which is the default). When 'Enable agent reporting' is checked, agent

capacity numbers for central controller servers are virtually identical to Unified Contact Center Enterprise – the Progger

and Standalone Router/Logger capacity tables in Section 6.5.2,

New Deployments and Technology Refresh

and Section

6.5.3,

Common Ground Upgrade are applicable instead of those that follow.

6.5.2 New Deployments and Technology Refresh

Table 6-26: Rogger Servers, Unified ICME, New Deployments / Tech. Refresh

Server Class Capacity

(agents)

MCS-40-005-Class

MCS-40-011-Class

2,000

Note: The Rogger server has the Unified ICM Router and Unified ICM Logger collocated.