Cisco Cisco IP Contact Center Release 4.6.1 Release Note

Page of 33
Cisco ICM Software Release 6.0(0) Bill of Materials 
 
Overview 
This document is the recommended Bill of Materials for Cisco ICM Enterprise Edition and IPCC Enterprise Edition version 6.0(0) 
(referenced herein as “ICM/IPCC”).  It provides platform hardware specifications and compatible 3
rd
 party software version 
requirements across the major components of the Cisco ICM/IPCC platform. 
Requirements for the ICM/IPCC systems are listed by major component, both basic ICM/IPCC nodes and corresponding options, 
including multi-media servers.  Hardware specifications are supplied for these components across three broadly-defined categories of 
small, medium and large enterprise systems. Each category is loosely defined by system configuration and workload levels (see the 
Sizing Guidelines” section below). 
The Cisco ICM/IPCC product is, by design, highly scalable and is configured across multiple deployment and call routing scenarios.  
Optimal sizing and component configuration for a given deployment will vary based on a number of factors, including agent capacity, 
call rate and call flow model(s), call context size, historical data volume and retention requirements, and other factors.  Given the 
deployment variables of the overall product, sizing categories contained herein are intended for use as guidelines only.  Cisco strongly 
recommends consultation with your Cisco Certified Partner or with Cisco World Wide Voice Practice / Advanced Services prior to 
specific deployment selection. 
Note that specific ICM/IPCC component nodes (e.g. ICM/IPCC Router or Logger) are described herein as being deployed on 
dedicated hardware servers.  While typically deployed as such, the descriptions are not meant to imply that all components mandate a 
standalone server configuration.  In most circumstances, however, components deployed in a co-resident fashion (e.g. a combined 
Router and Logger, or “Rogger” configuration) should target the next higher level of the deployment sizing guidelines.  Consult your 
Cisco Certified Partner or Cisco World Wide Voice Practice / Advanced Services for additional information. 
The hardware specifications supplied herein for CPU processor power, memory and disk storage requirements, and related parameters 
represent systems minimally configured for adequate performance in the given size category.  As specified, such systems will afford a 
margin for reasonable incremental growth within the bounds of that category.  While it is likely that lower capacity hardware would 
provide adequate performance in many scenarios, the specifications as stated are those on which the ICM/IPCC product is qualified 
by Cisco prior to release.  Cisco thus stipulates that new system deployments meet these minimum requirements to ensure safe and 
adequate performance results.  Customers upgrading to the ICM/IPCC 6.0(0) release from prior versions should carefully evaluate 
their hardware platforms and ascertain whether replacement is necessary; where processor family and speeds are significantly below 
those outlined here, consult your Cisco Certified Partner or Cisco World Wide Voice Practice / Advanced Services to determine 
whether a hardware upgrade is required. 
Updated Information in this Document 
This document updates the February, 2007 version with the following changes: 
Topic Notes 
ICM/IPCC E-Mail Manager Option page 25 
This section now makes clear that only in very small agent configurations (less 
than 10 concurrent agents) can the UI Server and WebView components be co-
resident with the Application Server. 
Qualificaton with McAfee VirusScan Enterprise 8.5i 
Cisco E-Mail Manager
Qualification with Cisco E-Mail Manager 50.SR7  
Cisco Media Convergence Servers 
Supplied hardware options include the Cisco Media Convergence Servers (MCS) platform, a Cisco supplied and qualified server 
platform built using components from several leading server hardware vendors.  The BOM provides a mapping of ICM/IPCC 
component server requirements to the appropriate MCS model(s) across the configuration range.  Where specific ICM/IPCC 
 1