Cisco Cisco IP Contact Center Release 4.6.1 Release Note

Upgrading an ICM / IPCC installation from Release 5.0 or 6.0 requires that you first upgrade the entire system to 7.0(0). You can 
then install 7.1(x) on your upgraded 7.0(0) system.  See also the Overview on page 1. 

This section describes the considerations for this process. 

Upgrading to ICM / IPCC Release 7.0(0) is explained in the Upgrade Guide for Cisco ICM/IPCC Enterprise & Hosted Editions.  
This section highlights some of the considerations to be aware of.  

 

There are two distinct approaches for upgrading an existing ICM/IPCC installation to the 7.0(0) release of the software: 

ƒ  Technology Refresh.  Install and configure the system and product software on newly acquired hardware, migrating 

historical and configuration data from the prior hardware environment.    

ƒ  Common Ground.  Upgrade software in-place on pre-existing hardware, migrating data in-place.   

In both the above cases, the ICM/IPCC database is migrated using a newly introduced migration utility known as the Enhanced 
Database Migration Tool (EDMT).  EDMT streamlines the upgrade process by migrating data and schema efficiently in bulk 
(usually over the course of a single maintenance window) and with an improved user interface. This replaces the prolonged “shadow 
copy” process of prior upgrades.  Both EDMT and detailed procedures for the overall upgrade and migration can be found in the 
Upgrade Guide for Cisco ICM/IPCC Enterprise & Hosted Editions. 

Deciding on the appropriate upgrade path depends in part on whether a customer’s existing hardware is suitable for the Release 
7.0(0) deployment.  Cisco recognizes the importance of protecting a customer’s investment in recent generation hardware, and for 
that reason ongoing qualification of the ICM/IPCC product is extended to address older hardware.  At the same time, given 
significant strides in processor speeds and an increasing computational demand from both the system and application software, a 
level of relative concurrency in supported hardware is maintained.  As a guideline, Cisco minimally certifies and supports the current 
release hardware that met the corresponding product Hardware and System Software Specification (Bill of Materials) when 
purchased new two major releases back.  Capacity and sizing numbers differ between those for “minimum recommended” and 
currently available hardware models – and capacity profiles presented in Section 7 

reflect that difference between capacities shown for new deployments (and technology refresh) versus common ground upgrades.  
The current generation (new deployment) hardware specified is strongly recommended for all upgrades, to fully exploit the call 
processing capacity designed into the ICM/IPCC product. 

ICM/IPCC Release 7.0(0) is optimized for the Windows Server 2003 operating system (both Standard and Enterprise Edition), and 
all new installs must be performed on that operating system. Ongoing support for Release 7.x (ICM and IPCC) running on Windows 
2000 Server effectively ended in October 2006 (one year following the General Availability date of the Windows Server 2003-
compatible 7.0 product)

 4

.   

Recognizing the significant impact of an operating system deployment in the upgrade scenario, Cisco continues to provide for 
updates to the current maintenance version of the product (7.1(x)) on the Windows 2000 Server platform, provided customers 
subsequently migrate to Windows Server 2003 within 30 days of the upgrade.  This policy will NOT continue with any subsequent 
version updates beyond 7.1(x), either major (e.g. 8.0(x)) or minor (7.2(x)) versions — which will require Windows Server 2003 as 
prerequisite to their installation. 

                                                           

4

 Windows 2000 mainstream support from Microsoft ended on June 30, 2005.  Microsoft offers Extended Support for five (5) years 

after the end of mainstream support, or for two (2) years after the second successor product (N+2) is released—whichever is longer.  
Refer to the Windows Product Family Lifecycle at http://www.microsoft.com/lifecycle for the latest information.