Preparing for System Upgrade

Table Of Contents

Preparing for System Upgrade

System Upgrade Approach

System Upgrade Dependencies

Cisco Unified CallManager Upgrade and Compatibility Considerations

Cisco Unified CallManager 5.0(2) and Cisco Unified CallManager 5.0(4) Compatibility Matrix

Customer Response Solutions Considerations

Cisco Unified 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 Unified CallManager (Unified 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 System solution in the following order:

1. Infrastructure components, including Catalyst 6000 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 System components.

2. Contact center components

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

4. PSTN Gateways

5. Cisco Gatekeepers (for multisite distributed deployment models)

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

7. Application clients including Cisco Unified Contact Center Enterprise (Unified CCE) Agent and Supervisor Desktop clients, Cisco Unified Video Advantage, and others.

See Chapter 3, "Upgrading IPT Software Components" and Chapter 4, "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 Unified CallManager, or if the upgrade order does not matter.

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 Cisco Unified Communications System
Release 5.0 release set are compatible with each other and will interoperate, as also the components in the Release 5.0(2) 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 Multistage System and Multisite 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, Unified CallManager is upgraded before the gateways. Therefore, 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 Unified CallManager Upgrade and Compatibility Considerations

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

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

•For Unified 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.x release versions.

•Before you perform an upgrade, Cisco recommends that you back up the Unified CallManager and Call Detail Record (CDR) database to an external network directory using the Disaster Recovery Framework. This practice will prevent any loss of data if the upgrade fails.

•If Unified 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.

•When upgrading Unified CallManager clusters set up in a 1:1 redundancy model, the first node should always be upgraded first. Before rebooting the first node after its upgrade, upgrade all the subsequent nodes simultaneously, again without rebooting them.

After all nodes in the cluster are upgraded, make sure you do the following:

–Reboot and switch versions to Unified CallManager 5.0(4) on the first node and wait until the first node is initialized and fully operational.

–Reboot and switch versions to Unified CallManager 5.0(4) on the TFTP and Music-On-Hold (MOH) servers first.

–Wait until the TFTP servers fully build their configuration files.

–Then reboot and switch versions to Unified CallManager 5.0(4) on the backup and call processing subsequent nodes and wait until these servers are fully initialized.

–Complete the upgrade by rebooting and switching versions to Unified CallManager 5.0(4) on the remaining active call processing subsequent nodes in the cluster.

---

Note For further details on recommended upgrade procedures, see Chapter 8 of the Cisco Unified Communications SRND based on Cisco Unified CallManager 5.0: http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_book09186a00806492bb.html

---

•In a mixed Cisco CallManager and Unified CallManager environment (where clusters are running 4.x and 5.x 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(4) 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(2) includes Cisco Unity Express Release 2.2.2 (not version 2.3) as part of its system testing. Cisco Unity Express 2.2.2 is compatible only with Unified CallManager Express and not with Unified CallManager Release 5.0(4) with SRST. Therefore, in tested Cisco Unified Communications Release 5.0(2) 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(4)).

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

•If your voicemail system is running Cisco Unity Release 4.2 and TSP 8.1(2), the following phones or combinations of phones are supported:

–With SIP trunk integration—Cisco Unity supports only SIP Phones with the Unified CallManager phone system.

–With SCCP integration—Cisco Unity supports:

•Only SCCP Phones for the Unified CallManager phone extensions.

•Both SCCP and SIP Phones for the Unified CallManager extensions with or without a media termination point (MTP) on the Cisco Unified CallManager server.

Cisco Unified CallManager 5.0(2) and Cisco Unified CallManager 5.0(4) Compatibility Matrix

Table 2-1 lists the release versions of the components that are compatible with the Unified CallManager 5.0(2) and Unified CallManager 5.0(4) 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 Unified CallManager.

Table 2-1 Unified CallManager Release 5.0(2) and Release 5.0(4) Upgrade Compatibility 

Component	Version	Unified CallManager 5.0(2)	Unified CallManager 5.0(4)	Upgrade Order
Cisco Unified CallManager Express	3.4(0)	Yes	Yes	Any
Cisco Unity Express	2.2.2	Yes	Yes1	After Unified CallManager (see above considerations)
Cisco Unity (Exchange/Domino)	4.2(1) ES9	Yes with TSP 8.1(2)	Yes with TSP 8.1(2)	Any (see above considerations)
Cisco Unity TSP	8.1(2)	Yes	Yes	Any
Cisco Unity Connection	1.1.(1) SR1 ES12	Yes	Yes	Any
	1.1(2) SR1 ES30	Yes	Yes
Cisco Unified MeetingPlace	5.3	Yes	Yes	Any
Cisco Unified MeetingPlace Express	1.1.1.11	Yes	No	Any
	1.1(2)	Yes	Yes
Cisco Unified MobilityManager	1.2.0.1-5	Yes	Yes	Before Unified CallManager (see above considerations)
CRS (Unified IP IVR & Unified Contact Center Express)	3.5(3)	Yes	No	Same stage as Unified CallManager (see above considerations)
	4.5(2)	No	Yes
Unified CCE/Unified ICM and CTI OS Server	7.0(0) SR3	Yes	Yes	Any
	7.0(0) SR4	Yes	Yes
Cisco Unified Customer Voice Portal	3.1(0)ES2	Yes	Yes	Any
	3.1(0) SR1 ES2	Yes	Yes
Cisco Agent Desktop/Cisco Supervisor Desktop	6.0(0)	Yes	No	Any
	7.0.1.17	Yes	Yes
CTI OS Agent/Supervisor	6.0(0)	Yes	No	Any
	7.0SR2	Yes	Yes
Cisco Unified ICM Support Tools	2.0	Yes	Yes	Any (upgrade with Unified ICM)
Cisco Emergency Responder	1.3.1	Yes	Yes	Any (see above considerations)
Cisco IP Communicator	2.0(1a)	Yes	Yes	Any
Cisco Unified Operations Manager	1.1	Yes	Yes	Any
IOS Gateway and Gatekeeper	12.4(6)T	Yes	Yes	Any
	12.4(6)T1	Yes	Yes
Cisco Unified Survivable Remote Site Telephony (SRST)	3.4(0)	Yes	Yes	Any
Cisco Unified VT Advantage	1.0(2)	Yes	Yes	Any
	2.0(1a)	Yes	Yes
Cisco VG224 (analog voice gateway)	12.4(6)T	Yes	No	Any
	12.4(6)T1	No	Yes
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
Cisco Secure PIX Firewall 535	7.0(4)5	Yes	Yes	Before Unified CallManager and Unified Communications products
	7.2	Yes	Yes
Cisco Unified Personal Communicator	1.1(1)	No	Yes	After Unified CallManager upgrade and Presence Server installation
Cisco Unified Presence Server	1.0(1)	No	Yes	After Unified CallManager

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

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 CRS 4.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, or 4.0. 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 Unified 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

•Chapter "IP Telephony Endpoints" in the Cisco Unified Communications SRND based on Cisco Unified CallManager 5.0:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_implementation_design_guide_book09186a00806492bb.html

Backward Compatibility Issues

In Multistage 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 Multistage System or Multisite 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 Chapter 4, "Related Documentation" (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.

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 Multistage System and Multisite 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.

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.

You should perform the upgrade for these components across two separate maintenance windows. This type of upgrade is described in the Multistage System and Multisite 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(4) 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 the Cisco Unified Communications System Release 5.0 and Release 5.0(2) release sets:

Table 2-2 Contact Center Components in Cisco Unified Communications System Release 5.0 and Release 5.0(2) Release Sets 

Cisco Unified Communications System Release 5.0 Component Name	Cisco Unified Communications System Release 5.0 Release Set	Cisco Unified Communications System Release 5.0(2) Release Set
Cisco Unified CallManager	5.0(2)	5.0(4)
Cisco Unified CallManager Operating System	Included with Unified CallManager	Included with Unified CallManager
Cisco Customer Response Solutions (Unified IP IVR)	4.5(2)	4.5(2)
Cisco Customer Response Solutions (Unified IP IVR) Operating System	2000.4.2SR3	2000.4.2SR8
Cisco Unified Intelligent Contact Management	7.0(0)SR2 ES1	7.0(0)SR4
Cisco Unified Intelligent Contact Management Operating System	Win2003 SP1	Win2003 SP1
Cisco Unified Customer Voice Portal	3.1(0)ES2	3.1(0)SR1 ES2
Cisco Unified Customer Voice Portal Operating System	Win2000 SP4	Win2000 SP4
Computer Telephony Integration Object Server (CTI OS)	7.0SR1	7.00SR2
Cisco Agent Desktop (CAD)	7.0.1.17	7.0.1.17
Cisco Agent Desktop (CAD) Operating System	WinXP SP2	WinXP SP2
Cisco Unified IP Phone Agent	7.0.1.17	7.0.1.17
ScanSoft Open Speech Recognizer (OSR)	2.0.9	2.0.9
ScanSoft Open Speech Media Server (OSMS)	2.0.4	2.0.4
ScanSoft Speechify	3.0.1	3.0.1
Cisco CSS 11501 Content Services Switch	WebNs 7.40.2.02	WebNs 7.40.2.02
Cisco Unity Connection	1.1(1)SR1 ES12	1.1(1)SR1 ES30 (for SIP only) 1.1(1)SR1 (for SCCP only)
Cisco IP Communicator	2.0(1a)	2.0(1a)
Cisco 3725, 3745 (Unified CVP VXML voice gateways)	12.4(6)T	12.4(6)T1
Cisco 3825, 3845 (Unified CVP VXML voice gateways)	12.4(6)T	12.4(6)T1
Cisco AS5400HPX (Unified CVP VXML voice and PSTN gateways)	12.4(6)T	12.4(6)T1
Cisco AS5850 (PSTN gateway)	12.4(6)T	12.4(6)T1
Cisco 3660 (Cluster gatekeeper)	12.4(6)T	12.4(6)T1
Cisco 3745 (HSRP gatekeeper)	12.4(6)T	12.4(6)T1
Cisco 3725, 3745 (voice/data gateway)	12.4(6)T	12.4(6)T1
Cisco 3825, 3845 (voice/data gateway)	12.4(6)T	12.4(6)T1
RSVP Agent (on 37xx and 38xx platforms)	12.4(6)T	12.4(6)T1
Cisco 7206 (core/WAN router)	12.4(6)T	12.4(6)T1
Cisco 831 router	12.4(5a)	12.4(5a)
Cisco Catalyst 3550 (access switch)	12.2(25)SEC	12.2(25)SEC
Cisco Catalyst 6506, 6509 (core switch, supervisor 2)	CatOS 8.4(4)	CatOS 8.5(2)
Cisco Catalyst 6506, 6509 (MSFC, supervisor 2)	12.1(26)E3	12.1(26)E3
Cisco Catalyst Communications Media Module (CMM)	12.4(4)T1	12.4(6)T1
Cisco Security Agent Management Center for Cisco Security Agents	4.5.1.639	4.5.1.639
Cisco Security Agent for Unified CallManager—Engine/Policy	4.5.1.639 /2.0.3	4.5.0.573 /2.0.3
Cisco Security Agent for Customer Response Solutions—Engine/Policy	4.5.1.639 /2.0.3	4.5.1.639 /2.0.4
Cisco Security Agent for Unified Intelligent Contact Management—Engine/Policy	4.5.1.639 /2.0.1	4.5.0.573 /2.0.2
Cisco Security Agent for Unified Customer Voice Portal—Engine/Policy	4.5.1.639 /2.0.0	4.5.0.573 /2.0.0
Cisco Unified Operations Manager	1.1	1.1
LAN Management Solution (LMS)	2.5	2.5
Resource Management Essentials (RME)	4.0	4.0
Cisco Remote Monitoring Suite (RMS)	2.0	2.0
Cisco Unified ICM Support Tools (Server and Agent)	2.0	2.0
McAfee Antivirus	Enterprise 8.0.0	Enterprise 8.0i
Cisco Unified IP Phones (Both SCCP and SIP Phones are included)	Bundled with Unified CallManager	Bundled with Unified CallManager

Software Releases for IP Telephony Components

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

Table 2-3 IPT Components in Cisco Unified Communications System Release 5.0 and Release 5.0(2) Release Sets 

Cisco Unified Communications System Release 5.0 Component Name	Cisco Unified Communications System Release 5.0 Release Set	Cisco Unified Communications System Release 5.0(2) Release Set
Cisco Unified CallManager	5.0(2)	5.0(4)
Cisco Unified CallManager—Cisco IP Telephony Operating System	Included with Unified CallManager	Included with Unified CallManager
Cisco Customer Response Solutions (Cisco Unified Contact Center Express)	4.5(2)	4.5(2)
Cisco Customer Response Solutions—Cisco IP Telephony Operating System	2000.4.2SR3	2000.4.2SR8
Cisco Emergency Responder	1.3.1	1.3(1a)
Cisco Emergency Responder—Cisco IP Telephony Operating System	2000.4.2SR3	2000.4.2SR8
Cisco Unified Presence Server	not used	1.0(1)
Cisco Unity, TSP	4.2(1), 8.1(2)	4.2(1) ES9, 8.1(2)
Cisco Unity—Microsoft Exchange	Microsoft Exchange 2000/2003	Microsoft Exchange 2000/2003
Cisco Unity—IBM/Lotus Domino1	6.5 with DUC 1.2.3	6.5 with DUC 1.2.3
Cisco Unified MeetingPlace	5.3	5.3
Cisco Unified CallManager Express	3.4(0) / IOS 12.4(6)T	3.4(0) / IOS 12.4(6)T1
Cisco Unity Express2	2.2.1	2.2.2
Cisco Unity Connection	1.1(1)SR1 ES12 (for SIP interworking), 1.1(1)SR1 (for SCCP only, no SIP)	1.1(1)SR1 ES30 (for SIP integration), 1.1(1)SR1 (for SCCP only integration)
Cisco Unified MeetingPlace Express	1.1.1.11	1.1(2)
Cisco Unified Survivable Remote Site Telephony (SRST)	3.4(0)	3.4(0)
Cisco Unified Videoconferencing Multipoint Control Unit (MCU) 35111	4.1.9	5.0
Cisco Unified Videoconferencing MCU 3540	4.2.10	5.0
Cisco Unified Videoconferencing Enhanced Media Processor (EMP) Module	4.2.8 and 4.2.8.1	4.2.8 and 4.2.8.1
Cisco Unified Videoconferencing Gateway 3521 (ISDN BRI)1	4.0.0.40	4.0.0.40
Cisco Unified Videoconferencing Gateway 3526 (ISDN PRI)1	4.0.0.40	4.0.0.40
Cisco 1760 (voice/data gateway)1	not used	12.4(6)T1
Cisco 2610XM, 2611XM, 2620XM, 2621XM, 2650XM, 2651XM, 2691 (router)	12.4(6)T	12.4(6)T1
Cisco 2801, 2821, 2851, 3825, 3845 (router, voice/data gateway)	12.4(6)T	12.4(6)T1
Cisco 3745 (gatekeeper)	12.4(6)T	12.4(6)T1
Cisco 3725, 3745 (voice/data gateway)	12.4(6)T	12.4(6)T1
Cisco 3725, 3745, 3825 (SRTP3 and Secure SRST gateways)	12.4(6)T	12.4(6)T1
Cisco 7206 (voice/data gateway)	12.4(6)T	12.4(6)T1
Cisco Catalyst 3550 (access switch)	12.2(25)SEC2	12.2(25)SEC2
Cisco Catalyst 3560 (access switch)	12.2(25r)SE1 -3560	12.2(25r)SE1 -3560
Cisco Catalyst 3750 (data center switch)	12.2(25)SEC2	12.2(25)SEC2
Cisco Catalyst 4506 (access switch)	12.2(20)EWA (3.86)	12.2(20)EWA (3.86)
Cisco Catalyst 6506, 6509 (voice access switch, supervisor 2 / MSFC2)	CatOS 8.4(3) / 12.2(17d)SXB9	CatOS 8.5(2) / 12.2(18)SXF3
Cisco Catalyst 6506, 6509 (core switch, supervisor 720)	IOS 12.2(18)SXE4 (native-mode)	IOS 12.2(18)SXF3 (native-mode)
Cisco Catalyst Communications Media Module (CMM)	12.4(4)T1	12.4(6)T1
Cisco Catalyst Firewall Service Module (FWSM)	3.1(1)	3.1(3)
Cisco Catalyst 6608, 6624 (voice gateway)	Bundled with Unified CallManager	Bundled with Unified CallManager
Cisco VG224 (analog voice gateway)	12.4(6)T	12.4(6)T1
Cisco VG248 (analog voice gateway)	1.3(1)ES8.2	1.3(1)ES8.2
Cisco ATA 186, 188 (analog telephony adaptor)	Bundled with Unified CallManager	Bundled with Unified CallManager
Cisco Security Agent for Unified CallManager—Engine/Policy	4.5.1.(652.1)	4.5.1.(652.1)
Cisco Security Agent for Cisco Emergency Responder	4.5.1-639-2.0.3	4.5.1-639-2.0.4
Cisco Security Agent for Cisco Customer Response Solutions	4.5.1-639-2.0.3	4.5.1-639-2.0.4
Cisco Security Agent for Cisco Unity	4.5.1-639-2.0.2	4.5.1-639-2.0.3
Cisco Fax Server	9.0	9.0
Cisco Secure PIX Firewall 535	7.0(4)5	7.2
Cisco SIP Proxy Server	2.2.1.11	2.2.1.11
Cisco Unified MobilityManager	1.2.0.1-5	1.2.1
Cisco Unified Operations Manager	1.1	1.1
Cisco Resource Management Essentials (RME)	4.0.3	4.0.3
Cisco Unified IP Phones models 7905G, 7911G, 7912G, 7920, 7935, 7940G, 7941G 7960G, 7961G, 7970G, 7971G	Bundled with Unified CallManager	Bundled with Unified CallManager
Cisco Aironet Access Point (AP) 1200G	12.3(8)JA	12.3(8)JA
Cisco IP Communicator	2.0(1a)	2.0(1a)
Cisco Unified Personal Communicator	not used	1.1(1)
Cisco Unified VT Advantage	1.0(2)	2.0(1a)
McAfee Antivirus	Enterprise 8.0.0 Patch Version: 11	Enterprise 8.0.0 Patch Version: 11
Polycom VSX7000	8.0.3 (H.323)	8.0.3 (H.323)
Tandberg 7985 (SCCP video endpoint)	4.0(2)	4.0(2)
Tandberg 990 MXP (H.323 video endpoint)	F4.0 (H.323)	F4.1 (H.323)
Tandberg T1000 (SCCP video endpoint)	I2.1	I2.1
Tandberg T1000 MXP (H.323 and SCCP video endpoint)	F4.0 (H.323), M2.1 (SCCP)	F4.0 (H.323), M2.1 (SCCP)

1 Applies to EUEM (European & Emerging Markets) deployments only. 2 See additional compatibility information in the Cisco Unified CallManager Upgrade and Compatibility Considerations section. 3 SRTP supported for MGCP gateways only (not H.323 gateways or SIP servers).