Support

Table Of Contents

Preparing for System Upgrade

System Upgrade Approach

System Upgrade Dependencies

Cisco CallManager Upgrade and Compatibility Considerations

Cisco CallManager 4.1(3) and Cisco Unified CallManager 5.0(2) Compatibility Matrix

Cisco Intelligent Contact Management Considerations

Cisco IPCC Enterprise Considerations

Customer Response Solutions Considerations

Cisco IP Phones Considerations

Backward Compatibility Issues

Backward Compatibility Scenarios

Upgrade Release Versions

Software Releases for Contact Center Components

Software Releases for IP Telephony Components

Preparing for System Upgrade

---

This topic discusses information to be aware of prior to the actual upgrade process such as the general upgrade approach for the different components, upgrade release versions of components involved in the upgrade, and release version compatibility.

This topic contains the following sections:

•System Upgrade Approach

•System Upgrade Dependencies

•Upgrade Release Versions

System Upgrade Approach

The general approach is to upgrade one Cisco CallManager cluster and its associated components one at a time before upgrading the next cluster.

For each cluster, upgrade the components of the Cisco Unified Communications solution in the following order:

1. Infrastructure components, including Catalyst 6K switches, routers and domain controllers (including Active Directory). These components should be upgraded first to ensure that the infrastructure is able to support the services required by Cisco Unified Communications components.

2. Contact center components

3. Call processing components such as Cisco CallManager Express and Cisco CallManager clusters

4. PSTN Gateways

5. Cisco Gatekeepers (for multi-site distributed deployment models)

6. Application servers including Cisco Unity components (Security applications are not included)

7. Application clients including Cisco IPCC Enterprise Agent and Supervisor Desktop clients, Cisco Video Advantage, and others.

See Chapter 3, "Upgrading IPT Software Components" and "Upgrading Contact Center Software Components" for detailed information on the order in which the above components have to be upgraded.

The upgrade sequence of the components should also be dictated by the following considerations:

•The criticality of the service that these components provide. For example, basic phone service is considered to be of greater importance than supplementary services or voice-mail services.

•Backward compatibility of the software releases of these components.

See Table 2-1 which indicates which components need to be upgraded prior to or after upgrading Cisco CallManager, or if the upgrade order does not matter.

---

Note A majority of the IP telephony (IPT) and contact center components' names have changed as part of Cisco Unified Communications System Release 5.0. Consequently, in this document, we use the new names to reference Cisco Unified Communications Release 5.0 components and old names to reference the same components when part of the Cisco IP Communication (IPC) Systems Test Release 4.1.

---

System Upgrade Dependencies

It should be assumed that components within each release set are compatible with each other and will interoperate correctly. For example, components in the 4.1 release set are compatible with each other and will interoperate, as also the components in the Cisco Unified Communications release set.

The order of operations also needs to take into account the impact of backwards (in)compatibility as described later in this section, especially for Multi-Staged System and Multi-Site Migration upgrades, where each stage (or maintenance window) only upgrades some of the components in the Release Set.

However, as you upgrade individual components of the integrated system, the overall system may operate in a state of degraded service where one or more components have been upgraded to the next release level and may not interoperate with components that are still at the previous release level.

For the upgrade order listed previously for the various deployment models, the components that are upgraded first should interoperate with other components that are still at the previous release level.

For example, Cisco CallManager is upgraded before the gateways. Therefore, Cisco Unified CallManager (Unified CallManager), which is now at the next release level, must interoperate with the gateways that have not been upgraded and are still at the previous release level.

Cisco CallManager Upgrade and Compatibility Considerations

Since Cisco CallManager is upgraded from the 4.1 release set to the Cisco Unified Communications release set early in the upgrade sequence, it has to be compatible with other components running Cisco Unified Communications software release versions.

Be aware of the following constraints to upgrade with regards to Cisco CallManager:

•For Cisco CallManager, you must perform all software installations and upgrades using the Software Upgrade Menu Options. Only software approved by Cisco Systems can be uploaded and processed by the system installer. Third-party or Windows-based software applications that you may have been using with a previous version of Cisco CallManager cannot be installed or used with the current Unified CallManager 5.0 release version.

•While Cisco CallManager Release 4.1(3)SR1 is the version included in the IP Communications Systems Test 4.1 release set and can be used as the starting point for the Cisco CallManager upgrade, we recommend using Release 4.1(3)SR2 as the starting release version.

•If Cisco CallManager clusters are set up in a 1:1 redundancy model, downtime during upgrade can be kept to a minimum. You can do this by load-balancing device registrations across primary and backup subscribers. This way if either subscriber server fails or is taken down for maintenance, only half of the devices will have to failover to the remaining subscriber, but will ensure that all devices can remain in service.

•IPCC Enterprise 6.0 does not support Unified CallManager 5.0. This means that you must perform the upgrade from IPCC Enterprise 6.0 to Unified CCE 7.0(0)SR3 at a stage (or in a maintenance window) preceding the upgrade from Cisco CallManager 4.1 to Unified CallManager 5.0(2).

•In a mixed Cisco CallManager and Unified CallManager environment (where clusters are running 4.x and 5.0 versions) along with Cisco Emergency Responder clustering, you must upgrade Cisco Emergency Responder to the next release (version 1.3). You may also have to upgrade the Cisco CallManager 4.x cluster to a later 4.x release that supports the new Cisco Emergency Responder release version.

•CRS 3.5(3) does not support Unified CallManager 5.0(2) and CRS 4.5(2) does not support Cisco CallManager 4.1(3). This means that you must upgrade the CRS and Cisco CallManager components in the same maintenance window to avoid a long service outage.

---

Note if you are using Unified CallManager 5.0 or later, you need to use CRS 4.5(2) and treat all CRS upgrades as fresh installations.

---

•Cisco Unified Communications Release 5.0 includes Cisco Unity Express Release 2.2 (not version 2.3) as part of its system testing. Cisco Unity Express 2.2 is compatible only with Unified CallManager Express and not with Unified CallManager Release 5.0(2) with SRST. Therefore, in tested Cisco Unified Communications Release 5.0 scenarios, Cisco Unity Express is implemented only in autonomous sites (using Unified CallManager Express) and not in an Enterprise Branch (using SRST with Unified CallManager Release 5.0(2)).

•When upgrading Cisco CallManager clusters (publisher and subscribers), make sure that you completely disable Cisco Security Agent for Cisco CallManager using the Admin Tools > Services page. Enable the Cisco Security Agent only after the upgrade installation finishes completely and the system reboots. If you simply suspend the Cisco Security Agent, instead of disabling it prior to the upgrade, the Cisco Security Agent is active upon restart and the upgrade is not successful across the cluster.

•Cisco Unified MobilityManager has to be upgraded to Release 1.2 to be compatible with Unified CallManager 5.0(2). You must backup the current version of Cisco Unified MobilityManager, install Release 1.2, and then restore data from the backup version.

•Cisco Unity TSP 1.2.0.25 interoperates with Unified CallManager 5.0(2) if SCCP is the connection method, and if either:

–All the phones are also SCCP

- or -

–Some of the phones are SIP, but MTP resources are used to terminate the RTP stream and handle DTMF.

Cisco CallManager 4.1(3) and Cisco Unified CallManager 5.0(2) Compatibility Matrix

Table 2-1 lists the release versions of the components that are compatible with the Cisco CallManager 4.1(3) and Unified CallManager 5.0(2) release versions. The table also specifies the upgrade order for the listed component in relation to Unified CallManager, where "Any" means that the component can be upgraded either before or after upgrading Cisco CallManager.

Table 2-1 Cisco CallManager 4.1(3) and Unified CallManager 5.0(2) Upgrade Compatibility 

Component	Version	Cisco CallManager 4.1(3)	Unified CallManager 5.0(2)	Upgrade Order
Cisco Unified CallManager Express	3.4(0)	Yes	Yes	Any
Cisco Unity Express	2.1	Yes	No	After Cisco CallManager (see above considerations)
	2.2.1	No	Yes1
Cisco Unity (Exchange/Domino)	4.0(5)	Yes with TSP 1.2.0.25	Yes with TSP 1.2.0.25	Any
	4.2(1)	Yes with TSP 1.2.0.25	Yes with TSP 1.2.0.25
Cisco Unity TSP	8.1(2)	Yes	Yes	Any (see above considerations)
Cisco Unity Connection	1.1(1)SR1 ES12	Yes	Yes	Any
Cisco Unified MeetingPlace	5.3	Yes	Yes	Any
Cisco Unified MeetingPlace Express	1.1.1.11	Yes	Yes	Any
Cisco Unified MobilityManager	1.1	Yes	No	Before Cisco CallManager (see above considerations)
	1.2.0.1-5	Yes	Yes
CRS (Unified IP IVR & Unified Contact Center Express)	3.5(3)	Yes	No	Same stage as Cisco CallManager (see above considerations)
	4.5(2)	No	Yes
Unified CCE/Unified ICM and CTI OS Server	6.0(0)	Yes	No	Before Cisco CallManager (see above considerations)
	7.0(0)SR3 ES1	Yes	Yes
Cisco Unified Customer Voice Portal	3.1(0)ES2	Yes	No	Any
Cisco Agent Desktop/Cisco Supervisor Desktop	6.0(0)	Yes	No	Before Cisco CallManager (see above considerations)
	7.0.1.17	Yes	Yes
CTI OS Agent/Supervisor	6.0(0)	Yes	No	Before Cisco CallManager (see above considerations)
	7.0SR1	Yes	Yes
Cisco Unified ICM Support Tools	2.0	Yes	Yes	Before Cisco CallManager (with Unified ICM)
Cisco Emergency Responder	1.2(3)SR2a	Yes	No	Any (see above considerations)
	1.3.1	Yes	Yes
Cisco IP Communicator	1.1(3)	Yes	Yes	Any
	2.0(1a)	Yes	Yes
(formerly CiscoWorks ITEM) Cisco Unified Operations Manager	2.0(5)	Yes	No	Any
	1.1	No	Yes
IOS Gateway and Gatekeeper	12.3(11)T2	Yes	Yes	Any
	12.4(6)T	Yes	Yes
Cisco Unified Survivable Remote Site Telephony (SRST)	3.2/12.3(11)T2	Yes	Yes	Any
	3.4(0)	Yes	Yes
Cisco Unified VT Advantage	1.0(2)	Yes	Yes	Any
Cisco VG224 (analog voice gateway)	12.4(6)T	Yes	Yes	Any
Cisco VG248 (analog voice gateway)	1.3(1)ES8.2	Yes	Yes	Any
Cisco Aironet Access Point AP 1200G	12.3(8)JA	Yes	Yes	Any

1 See additional compatibility information in the Cisco CallManager Upgrade and Compatibility Considerations section.

Cisco Intelligent Contact Management Considerations

Beginning with Unified CCE/Unified ICM Release 7.0(0)SR3, there are two ways to install and upgrade contact center components:

•Traditional ICM Setup (available previously)

•Unified System Contact Center (Unified SCC) (new with Release 7.0(0)SR3), which due to its simplicity is the recommended installation if you are newly installing Unified Communications System for Contact Center

When upgrading to Unified CCE/Unified ICM Release 7.0(0)SR3, be aware of the following:

•To implement regular Unified CallManager Post-Routed call flows, use the traditional ICM Setup and follow normal procedures to upgrade generic PGs, Cisco CallManager PGs, and VRU PGs.

•To implement Parent/Child call flows (and the Unified CCGE feature):

–You require the Cisco Unified System Contact Center Gateway (Unified SCCG) and Cisco Unified Contact Center Enterprise Gateway (Unified CCGE) components.

–There is no upgrade path for the above components; you have to perform a fresh installation.

–Unified CCGE can only be installed and supported on Unified ICM Release 7.0(0) or later.

–Unified SCCG can only be installed and supported on Unified CCE Release 7.0(0) or later.

–Unified SCCG functionality only supports CRS (IP IVR), not Unified CVP.

–Cisco Unified System Contact Center (Unified SCC) is a new peripheral type that combines the United CallManager and Unified IP IVR peripherals into one logical Unified CCE peripheral.

–Unified SCC's streamlined installation is only supported with Unified CCE Release 7.0(0) or later. It has a web-based administration that only supports Unified SCCGs.

–Unified SCC can only connect to one Unified CallManager cluster.

For additional information, see Upgrading a Specific Contact Center Test Bed.

Cisco IPCC Enterprise Considerations

When upgrading to Unified CCE Release 7.0(0)SR3, be aware of the following:

•If you do not backup the Active Directory and the upgrade fails, you will have to rebuild the entire Unified ICM server.

Customer Response Solutions Considerations

For CRS 4.5(2), be aware of the following:

•CRS is implemented as a standalone server with no support for high availability.

•CRS 4.5(2) in the Cisco Unified Communications contact center environment can only be handled as a "fresh" installation; upgrading from the previous CRS system is not supported. You cannot upgrade to CRS 4.5(2) from CRS Releases 3.1, 3.5 or 4.0; only a fresh install of CRS 4.5(2) is supported.

---

Note However, you can upgrade from CRS 4.5(1)SR1 to CRS4.5(2).

---

•CRS 4.5(2) also does not support data migration of configuration, scripts and agent information from CRS Releases 3.1, 3.5, 4.0 or 4.5(2). You must manually rebuild existing configurations and CRS scripts on the freshly installed CRS 4.5(2) server.

•Configuration data and CRS scripts (both custom and standard) are stored in the CRS database; not in the LDAP directory on the Unified CallManager.

•You should migrate all CRS applications that were previously co-resident with the Unified CallManager to a different Cisco Media Convergence Server (MCS).

•You must use the new "Backup and Restore System for CRS4.5" utility to back up CRS data.

•Ensure the following:

–A valid DNS server is available to provide name resolution services for all cluster machines, including CRS machines.

–A backup server is available for exclusively backing up the CRS database and is not used to back up other applications.

–The BARS server is bundled and installed on the same CRS server or on a separate MCS server acting as the backup server.

Cisco IP Phones Considerations

When enabling or upgrading phones to SIP, certain features and functionality that were previously available may no longer be supported. be aware of the following:

•Only enhanced SIP phones and existing/enhanced SCCP phones are supported as Cisco Unified IP Phone Agents.

•Cisco IP Communicator is supported as the Media Termination for the CAD/CSD desktops.

For more detailed information on this and the differences between features on the SCCP and SIP phones, see the documentation at:

•Cisco 7900 Series IP Phones Maintain and Operate Guides:
http://www.cisco.com/en/US/products/hw/phones/ps379/prod_maintenance_guides_list.html

•Cisco 7900 Series IP Phones End-User Guides:
http://www.cisco.com/en/US/products/hw/phones/ps379/products_user_guide_list.html

Backward Compatibility Issues

In Multi-Staged System upgrade scenarios, you may have to consider additional issues such as backward compatibility across components.

A version of one component is backward compatible with a previous version of another component when service functionality and behavior are maintained between the two component versions. Backward compatibility between two components or applications may limit the order of upgrade of the components and cause service outage during upgrades.

If two components are upgraded during separate maintenance windows, as in the Multi-Staged System or Multi-Site Migration upgrade scenarios, the whole system exists in a partially upgraded state in the interval between the two maintenance windows (MW).

The service capability during the period between maintenance windows depends on backwards compatibility between the two components as discussed in this section. If the two components are not backward compatible, then service outages occur in the interval between the two maintenance windows.

You may need to consider the following backward compatibility situations that may occur during the upgrade process. For more information, see the component compatibility matrices listed in Chapter 3, "Related Documentation" (for IP telephony) and "Upgrading Contact Center Software Components" (for Contact Center).

Backward Compatibility Scenarios

Both New Versions Are Backward Compatible

Both new versions of the two components are backward compatible with the previous version of the other component, as with Unified CallManager and Cisco Unity.

In this case, there is no restriction in the order of upgrades relating to backward compatibility. Either component may be upgraded first and be able to interoperate with the other component as shown in Figure 2-1.

You can perform the upgrade for these components across multiple maintenance windows. This type of upgrade is described in the Multi-Staged System and Multi-Site Migration upgrade approaches in "Planning Your System Upgrade" (for IP telephony) or "Planning Your System Upgrade" (for Contact Center).

Figure 2-1 Both New Release Versions are Backward Compatible

Only One New Version is Backward Compatible

Only one of the new versions is backward compatible with the previous version of the other component, as with Unified CCE and Cisco CallManager.

In this case, the component that is backward compatible should be upgraded first in order to avoid a service outage during the upgrade as shown in Figure 2-2.

For example, since IPCC Enterprise 6.0 does not support Unified CallManager 5.0(2), the upgrade from IPCC Enterprise 6.0 to Unified CCE 7.0(0)SR3 must be done prior to upgrading Cisco CallManager 4.1 to Unified CallManager 5.0(2).

You should perform the upgrade for these components across two separate maintenance windows. This type of upgrade is described in the Multi-Staged System and Multi-Site Migration upgrade approaches in "Planning Your System Upgrade" (for IP telephony) or "Planning Your System Upgrade" (for Contact Center).

Figure 2-2 One New Release Version is Backward Compatible

Neither New Version is Backward Compatible

Neither of the new versions is backward compatible with the previous version of the other component, as with CRS and Unified CallManager.

There will be a service outage which exists from the time the first product is upgraded until the second component has completed its upgrade as shown in Figure 2-3.

For example, CRS 3.5(3) does not support Unified CallManager 5.0(2) and CRS 4.5(2) does not support Cisco CallManager 4.1(3). Since neither component is backward compatible with the other, both components have to be upgraded in the same maintenance window to avoid service outage. This upgrade is described in the Single-Stage upgrade approach in "Planning Your System Upgrade" (for IP telephony) or "Planning Your System Upgrade" (for Contact Center).

Essentially, all CRS upgrades should be treated as fresh installations.

Figure 2-3 Neither New Release Version is Backward Compatible

Upgrade Release Versions

Software Releases for Contact Center Components

Table 2-2 lists the software versions for the contact center components in both the IPC Systems Test Release 4.1 and Cisco Unified Communications Release 5.0 release sets:

Table 2-2 Contact Center Components in Release 4.1 and Cisco Unified Communications Release 5.0 Release Sets 

IPC Systems Test Release 4.1 Component Name	IPC Systems Test Release 4.1 Release Set	Cisco Unified Communications Release 5.0 Release Set	Cisco Unified Communications Release 5.0 Component Name
Cisco CallManager	4.1(3)SR1	5.0(2)	Cisco Unified CallManager
Cisco CallManager—Cisco IP Telephony Operating System	2000.2.7SR4	Included with Unified CallManager	Cisco Unified CallManager Operating System
Cisco Customer Response Solutions (IP IVR)	3.5(3)SR1	4.5(2)	Cisco Customer Response Solutions (Unified IP IVR)
Cisco Customer Response Solutions—Cisco IP Telephony Operating System	2000.2.7SR4	2000.4.2SR3	Cisco Customer Response Solutions (Unified IP IVR) Operating System
Cisco Intelligent Contact Management (ICM)	6.0(0)SR2	7.0(0)SR2 ES1	Cisco Unified Intelligent Contact Management
Cisco Intelligent Contact Management (ICM)—Cisco IP Telephony Operating System	Win2000 SP4	Win2003 SP1	Cisco Unified Intelligent Contact Management Operating System
Cisco Customer Voice Portal (CVP) (formerly ISN)	3.0	3.1(0)ES2	Cisco Unified Customer Voice Portal
Cisco Customer Voice Portal (CVP)—Cisco IP Telephony Operating System	Win2000 SP4 or 2000.2.7	Win2000 SP4	Cisco Unified Customer Voice Portal Operating System
Cisco Telephony Integration Object Server (CTI OS)	6.0(0)SR2	7.0SR1	Computer Telephony Integration Object Server (CTI OS)
Cisco Agent Desktop (CAD)	6.0(2)SR1	7.0.1.17	Cisco Agent Desktop (CAD)
Cisco Agent Desktop (CAD) Operating System	Win2000 SP4	WinXP SP2	Cisco Agent Desktop (CAD) Operating System
Cisco Unified IP Phone Agent	not used1	7.0.1.17	Cisco Unified IP Phone Agent
ScanSoft Open Speech Recognizer (OSR)	2.0.9	2.0.9	ScanSoft Open Speech Recognizer (OSR)
ScanSoft Open Speech MRCP Server (OSMS)	2.0.4	2.0.4	ScanSoft Open Speech Media Server (OSMS)
ScanSoft Speechify	3.0.1	3.0.1	ScanSoft Speechify
Cisco CSS 11500 Content Services Switch	WebNs 7.30.2.03	WebNs 7.40.2.02	Cisco CSS 11501 Content Services Switch
Cisco Unity Connection	not used	1.1(1)SR1 ES12	Cisco Unity Connection
Cisco IP Communicator	not used	2.0(1a)	Cisco IP Communicator
Cisco 3660 (CVP VXML voice gateway)	12.3(11)T4	not used	Cisco 3660 (CVP VXML voice gateway)
Cisco 3725, 3745 (CVP VXML voice gateways)	12.3(11)T4	12.4(6)T	Cisco 3725, 3745 (Unified CVP VXML voice gateways)
Cisco 3825, 3845 (CVP VXML voice gateways)	not used	12.4(6)T	Cisco 3825, 3845 (Unified CVP VXML voice gateways)
Cisco AS5400HPX (CVP VXML voice gateway)	12.3(11)T4	12.4(6)T	Cisco AS5400HPX (Unified CVP VXML voice and PSTN gateways)
Cisco AS5850 (PSTN gateway)	12.4(1a)	12.4(6)T	Cisco AS5850 (PSTN gateway)
Cisco 3660 (Cluster gatekeeper)	not used	12.4(6)T	Cisco 3660 (Cluster gatekeeper)
Cisco 3745 (HSRP gatekeeper)	12.4(1a)	12.4(6)T	Cisco 3745 (HSRP gatekeeper)
Cisco 26xx, 37xx (core/access routers)	12.4(1a)	not used	Cisco 26xx, 37xx (core/access routers)
Cisco 3660 (voice/data gateway)	12.4(1a)	not used	Cisco 3660 (voice/data gateway)
Cisco 3725, 3745 (voice/data gateway)	12.4(1a)	12.4(6)T	Cisco 3725, 3745 (voice/data gateway)
Cisco 3825, 3845 (voice/data gateway)	not used	12.4(6)T	Cisco 3825, 3845 (voice/data gateway)
RSVP Agent (on 37xx and 38xx platforms)	not used	12.4(6)T	RSVP Agent (on 37xx and 38xx platforms)
Cisco 2691 (core/WAN router)	12.4(1a)	not used	Cisco 2691 (core/WAN router)
Cisco 7206 (core/WAN router)	12.4(1a)	12.4(6)T	Cisco 7206 (core/WAN router)
Cisco 831 router	12.4(1a)	12.4(5a)	Cisco 831 router
Cisco Catalyst 3550 (access switch)	12.1(22)EA4	12.2(25)SEC	Cisco Catalyst 3550 (access switch)
Cisco Catalyst 6506, 6509 (core switch, supervisor 2)	CatOS 8.4(3)	CatOS 8.4(4)	Cisco Catalyst 6506, 6509 (core switch, supervisor 2)
Cisco Catalyst 6506, 6509 (MSFC, supervisor 2)	12.1(26)E2	12.1(26)E3	Cisco Catalyst 6506, 6509 (MSFC, supervisor 2)
Cisco Catalyst Communications Media Module (CMM)	CatOS 8.4(3) / 12.4(1a)	12.4-4.T1	Cisco Catalyst Communications Media Module (CMM)
Cisco Security Agent (CSA) Management Center	4.0.3.728	4.5.1.639	Cisco Security Agent Management Center for Cisco Security Agents
Cisco Security Agent Engine/Policy—Cisco CallManager	1.1(10)	4.5.1.639 /2.0.3	Cisco Security Agent for Unified CallManager—Engine/Policy
Cisco Security Agent Engine/Policy—Cisco Customer Response Solutions	1.1(10)	4.5.1.639 /2.0.3	Cisco Security Agent for Customer Response Solutions—Engine/Policy
Cisco Security Agent Engine/Policy—Cisco Intelligent Contact Management (ICM)	1.0(6)	4.5.1.639 /2.0.1	Cisco Security Agent for Unified Intelligent Contact Management—Engine/Policy
Cisco Security Agent Engine/Policy—Cisco Customer Voice Portal (CVP)	1.1(3)	4.5.1.639 /2.0.0	Cisco Security Agent for Unified Customer Voice Portal—Engine/Policy
CiscoWorks ITEM	2.0(6)	1.1	Cisco Unified Operations Manager
LAN Management Solution (LMS)	not used	2.5	LAN Management Solution (LMS)
Resource Management Essentials (RME)	not used	4.0	Resource Management Essentials (RME)
Cisco Remote Monitoring Suite	2.0(6)	2.0	Cisco Remote Monitoring Suite (RMS)
Cisco ICM Support Tools (Server and Agent)	not used	2.0	Cisco Unified ICM Support Tools (Server and Agent)
McAfee Antivirus	Enterprise 7.1.0	Enterprise 8.0.0	McAfee Antivirus
Cisco SCCP Phones models 7940G, 7960G, 7970G (SIP Phones not used)	Bundled with Cisco CallManager	Bundled with Unified CallManager	Cisco Unified IP Phones (Both SCCP and SIP Phones are included)

1 Not Used: This denotes components that were not tested in the specific test environment due to a number of reasons including, but not limited to, lack of availability, end-of-life, or not being a test requirement for that release set.

Software Releases for IP Telephony Components

Table 2-3 lists the software versions for IPT components in the 4.1 release set and Cisco Unified Communications Release 5.0 release sets:

Table 2-3 IPT Components in Release 4.1 and Cisco Unified Communications Release 5.0 Release Sets 

IPC Systems Test Release 4.1 Component Name	IPC Systems Test Release 4.1 Release Set	Cisco Unified Communications Release 5.0 Release Set	Cisco Unified Communications Release 5.0 Component Name
Cisco CallManager	4.1(3)SR1/SR2	5.0(2)	Cisco Unified CallManager
Cisco CallManager—Cisco IP Telephony Operating System	2000.2.7SR4	Included with Unified CallManager	Cisco Unified CallManager—Cisco IP Telephony Operating System
Cisco Customer Response Solutions (IPCC Express)	3.5(3)SR1	4.5(2)	Cisco Customer Response Solutions (Cisco Unified Contact Center Express)
Cisco Customer Response Solutions—Cisco IP Telephony Operating System	2000.2.7SR4	2000.4.2SR3	Cisco Customer Response Solutions—Cisco IP Telephony Operating System
Cisco Emergency Responder	1.2(3)SR2	1.3.1	Cisco Emergency Responder
Cisco Emergency Responder—Cisco IP Telephony Operating System	2000.2.7SR4	2000.4.2SR3	Cisco Emergency Responder—Cisco IP Telephony Operating System
Cisco Unity, TSP	4.0(5), 8.0(1)	4.2(1), 8.1(2)	Cisco Unity, TSP
Cisco Unity—Microsoft Exchange	Exchange 2000	Microsoft Exchange 2000/2003	Cisco Unity—Microsoft Exchange
Cisco Unity—IBM/Lotus Domino	5.11 and 6.0.2 DUCS 1.2.2	6.5 with DUC 1.2.3	Cisco Unity—IBM/Lotus Domino1
Cisco MeetingPlace	5.3	5.3	Cisco Unified MeetingPlace
Cisco CallManager Express	3.3 / 12.4(1a)	3.4(0) / IOS 12.4(6)T	Cisco Unified CallManager Express
Cisco Unity Express	2.1	2.2.1	Cisco Unity Express2
Cisco Unity Connection	not used3	1.1(1)SR1 ES12 (for SIP interworking), 1.1(1)SR1 (for SCCP only, no SIP)	Cisco Unity Connection
Cisco MeetingPlace Express	not used	1.1.1.11	Cisco Unified MeetingPlace Express
Cisco Personal Assistant	1.4(5)	not used	Cisco Personal Assistant
Survivable Remote Site Telephony (SRST)	3.3 / 12.4(1a)	3.4(0)	Cisco Unified Survivable Remote Site Telephony (SRST)
Cisco Videoconferencing Multipoint Control Unit (MCU) 3511	4.0	4.1.9	Cisco Unified Videoconferencing Multipoint Control Unit (MCU) 35111
Cisco Videoconferencing System 3540	4.0.31	4.2.10	Cisco Unified Videoconferencing MCU 3540
Cisco Videoconferencing Enhanced Media Processor (EMP) Module	MCU 4.0, EMP 3.0.5	4.2.8 and 4.2.8.1	Cisco Unified Videoconferencing Enhanced Media Processor (EMP) Module
Cisco Videoconferencing Gateway 3521 (ISDN BRI)	1.2.0.9.4BRI	4.0.0.40	Cisco Unified Videoconferencing Gateway 3521 (ISDN BRI)1
Cisco Videoconferencing Gateway 3526 (ISDN PRI)	3.0.0.12	4.0.0.40	Cisco Unified Videoconferencing Gateway 3526 (ISDN PRI)1
Cisco 2610XM, 2611XM, 2620XM, 2621XM, 2650XM, 2651XM, 2691 (router)	12.4(1a)	12.4(6)T	Cisco 2610XM, 2611XM, 2620XM, 2621XM, 2650XM, 2651XM, 2691 (router)
Cisco 2801, 2821, 2851, 3825, 3845 (router, voice/data gateway)	12.4(1a)	12.4(6)T	Cisco 2801, 2821, 2851, 3825, 3845 (router, voice/data gateway)
Cisco 1751 (voice/data gateway)	12.4(1a)	not used	Cisco 1751 (voice/data gateway)
Cisco 1760 (voice/data gateway)	12.4(1a)	12.4(6)T	Cisco 1760 (voice/data gateway)
Cisco 3660 (voice/data gateway)	12.4(1a)	not used	Cisco 3660 (voice/data gateway)
Cisco 3745 (gatekeeper)	12.4(1a)	12.4(6)T	Cisco 3745 (gatekeeper)
Cisco 3725, 3745 (voice/data gateway)	12.4(1a)	12.4(6)T	Cisco 3725, 3745 (voice/data gateway)
Cisco 3725, 3745, 3825 (SRTP and Secure SRST gateways)	12.4(1a) / Advanced Enterprise Services	12.4(6)T	Cisco 3725, 3745, 3825 (SRTP4 and Secure SRST gateways)
Cisco 7206 (voice/data gateway)	12.4(1a)	12.4(6)T	Cisco 7206 (voice/data gateway)
Cisco Catalyst 3500XL (access switch)	12.0(5)WC11	not used	Cisco Catalyst 3500XL (access switch)
Cisco Catalyst 3550 (access switch)	12.1(22)EA4	12.2(25)SEC2	Cisco Catalyst 3550 (access switch)
Cisco Catalyst 3560 (access switch)	not used	12.2(25r)SE1 -3560	Cisco Catalyst 3560 (access switch)
Cisco Catalyst 3750 (data center switch)	not used	12.2(25)SEC2	Cisco Catalyst 3750 (data center switch)
Cisco Catalyst 4506 (access switch)	12.2(25)EWA1	12.2(20)EWA (3.86)	Cisco Catalyst 4506 (access switch)
Cisco Catalyst 6506, 6509 (voice access switch, supervisor 2 / MSFC2)	CatOS 8.4(3) / 12.1(20)E3	CatOS 8.4(3) / 12.2(17d)SXB9	Cisco Catalyst 6506, 6509 (voice access switch, supervisor 2 / MSFC2)
Cisco Catalyst 6506, 6509 (core switch, supervisor 720)	IOS 12.2(18)SXE1 (native-mode)	IOS 12.2(18)SXE4 (native-mode)	Cisco Catalyst 6506, 6509 (core switch, supervisor 720)
Cisco Catalyst Communications Media Module (CMM)	12.4(1a)	12.4(4)T1	Cisco Catalyst Communications Media Module (CMM)
Cisco Catalyst Firewall Service Module (FWSM)	not used	3.1(1)	Cisco Catalyst Firewall Service Module (FWSM)
Cisco Catalyst 6608, 6624 (voice gateway)	Bundled with Cisco CallManager	Bundled with Unified CallManager	Cisco Catalyst 6608, 6624 (voice gateway)
Cisco VG224 (analog voice gateway)	12.4(1a)	12.4(6)T	Cisco VG224 (analog voice gateway)
Cisco VG248 (analog voice gateway)	1.3(1)	1.3(1)ES8.2	Cisco VG248 (analog voice gateway)
Cisco ATA 186, 188 (analog telephony adaptor)	3.2(1)	Bundled with Unified CallManager	Cisco ATA 186, 188 (analog telephony adaptor)
Cisco Security Agent Engine/Policy —Cisco CallManager	4.5.0.565 / 2.0 Beta 6	4.5.1.(652.1)	Cisco Security Agent for Unified CallManager—Engine/Policy
Cisco Security Agent for Cisco Emergency Responder	4.5.1.639/ 2.0(3)	4.5.1-639-2.0.3	Cisco Security Agent for Cisco Emergency Responder
Cisco Security Agent Engine/Policy—Cisco Personal Assistant	4.0.1.539 / 1.1(3)	not used	Cisco Security Agent Engine/Policy—Cisco Personal Assistant
Cisco Security Agent Engine/Policy—Cisco Customer Response Solutions	4.5.0.565 / 2.0 Beta 6	4.5.1-639-2.0.3	Cisco Security Agent for Cisco Customer Response Solutions
Cisco Security Agent Engine/Policy—Cisco Unity	4.0.3.720 / 1.1(4)	4.5.1-639-2.0.2	Cisco Security Agent for Cisco Unity
Cisco Fax Server	not used	9.0	Cisco Fax Server
Cisco Secure PIX Firewall 535	not used	7.0(4)5	Cisco Secure PIX Firewall 535
Cisco SIP Proxy Server	not used	2.2.1.11	Cisco SIP Proxy Server
CiscoWorks ITEM	2.0(6)	1.1	Cisco Unified Operations Manager
Cisco Resource Management Essentials (RME)	not used	4.0.3	Cisco Resource Management Essentials (RME)
Cisco IP Phones models 7902G, 7905G, 7910G, 7912G, 7920, 7935, 7940G, 7960G, 7970G	Bundled with Cisco CallManager	Bundled with Unified CallManager	Cisco Unified IP Phones models 7905G, 7911G, 7912G, 7920, 7935, 7940G, 7941G 7960G, 7961G, 7970G, 7971G
IP Softphone	1.3(3)	not used	IP Softphone
Cisco VT Advantage	1.0(2)	1.0(2)	Cisco Unified VT Advantage
Cisco IP Communicator	1.1(2)	2.0(1a)	Cisco IP Communicator
Cisco Aironet Access Point (AP) 1100/1200	12.3(4)JA	12.3(8)JA	Cisco Aironet Access Point (AP) 1200G
Cisco Unified MobilityManager	not used	1.2.0.1-5	Cisco Unified MobilityManager
McAfee Antivirus	Enterprise 7.1.0	Enterprise 8.0.0 Patch Version: 11	McAfee Antivirus
Polycom VSX7000	7.5(2) (H.323)	8.0.3 (H.323), 8.5Beta (SIP)	Polycom VSX7000
Tandberg 7985 (SCCP video endpoint)	not used	4.0(2)	Tandberg 7985 (SCCP video endpoint)
Tandberg 990 MXP (H.323 and SIP video endpoint)	not used	F4.0 (H.323), F4.1Beta1 (SIP)	Tandberg 990 MXP (H.323 and SIP video endpoint)
Tandberg T1000 (H.323)	E4.2	not used	Tandberg T1000 (H.323 video endpoint)
Tandberg T1000 (SCCP)	I2.0	I2.1	Tandberg T1000 (SCCP video endpoint)
Tandberg T1000 MXP (H.323, SCCP and SIP video endpoint)	not used	F4.0 (H.323), M2.1 (SCCP), F4.1Beta1 (SIP)	Tandberg T1000 MXP (H.323, SCCP and SIP video endpoint)

1 Applies to EUEM (European & Emerging Markets) deployments only. 2 See additional compatibility information in the Cisco CallManager Upgrade and Compatibility Considerations section. 3 Not Used: This denotes components that were not tested in the specific test environment due to a number of reasons including, but not limited to, lack of availability, end-of-life, or not being a test requirement for that release set. 4 SRTP supported for MGCP gateways only (not H.323 gateways or SIP servers).