Cisco Cisco IP Contact Center Release 4.6.2 Release Note

 
This Hardware and System Software Specification was formerly known as the ICM/IPCC Bill of Materials (BOM).  It has been 
renamed to better reflect its content and purpose. That purpose is to specify the hardware and system software compatible with, and 
required for, the Cisco Unified Intelligent Contact Management (ICM) and Cisco Unified Contact Center (IPCC) product

 for major 

Release 7.0(0) and the minor and maintenance releases that can be applied to Release 7.0(0). 

This document is applicable to both the Enterprise and Hosted Editions of the Unified ICM and Unified Contact Center solutions.  

The information contained herein is intended for use by Certified Partners and Cisco sales and system engineers, for pre-sales 
hardware planning and third-party software selection, as well as for incremental system updates.  In all cases, the reader is assumed 
to be familiar with the ICM/IPCC product at an overview level, and to understand high level deployment models and essential 
application server types such as Logger and PG.  

Document content will be updated periodically for technical clarification and to align with subsequently qualified hardware and 
third- party software.  Document updates are typically synchronized with minor and maintenance releases and include updated 
support policy details for Microsoft Service Pack support qualified for the release.  Note that while newly available hardware may be 
added to this document following initial publication, existing hardware server specifications originally published for a specific 
configuration will not be rendered obsolete by any subsequent release 7.0(0) specification update.  

Release 7.0(0) is a major software release for the Enterprise and Hosted Editions of Unified ICM and Unified CC. Its predecessor 
was major Release 6.0.  

A minor release includes incremental new functionality in addition to software defect fixes, delivered in an automated patch installer 
that includes full rollback capability. Release 7.1(1) was the first minor release update to major Release 7.0.   

Defect repair updates subsequent to 7.0 SR4 are delivered as maintenance releases (designated by the rightmost digit of the version 
number, starting with two (2). Maintenance Releases replace Service Releases (SRs), the name change made to establish consistency 
across Cisco’s Voice product line.  Release 7.1(2) is the first maintenance release for minor Release 7.1(1) and can be installed over 
base Release 7.0(0), SRs 1—4 or Release 7.1(1). Release 7.1(2) replaces the ongoing 7.0 SR stream. Releases 7.1(2), 7.1(3), and 
7.1(4) are the second, third, and fourth maintenance releases, respectively, for minor Release 7.1(1) 

Note that minor Release 7.1(1) and subsequent  maintenance Releases 7.1(2)  - 7.1(4) are referenced generically in this document as 
Release 7.1(x)—except where a distinction is necessary, such as in the explanation of the upgrade path or in tables where agent-
capacity differs among them.  

Although 7.0(0) SR4 was the last Service Release,  both the ‘Service Release’ and ‘Maintenance Release’ terminology appear 
throughout the document.   

Because ICM/IPCC 7.0(0) installation is a prerequisite to 7.1(x) and later minor and maintenance releases to 7.0, statements in this 
document referring to ICM/IPCC 7.0(0) system requirements apply equally to follow-on 7.0 update releases, unless otherwise noted. 

To simplify mapping of the hardware server configurations across various deployments, a new approach of “server class” is 
introduced for both MCS and vendor-sourced (“generic”) servers.   A server class contains one or more hardware types, based on 
category of processor family, memory, and hard drive configuration appropriate for the specified application.  Server classes are 
detailed in 

Hardware and associated system software are specified by ICM/IPCC system server configuration with consideration for both the 
overall deployment model and the specific server software component configuration.  Capacity sizing is an integral factor in proper 
requirement specification. Where requirements are tiered by system sizing, defined operating conditions and representative sizing 

                                                           

1

 See the Note on Cisco Product Names on page 3. 

2

 System software consists of the operating system, database server, and other 3

rd

 party applications.