Cisco Unified Communications Manager (CallManager)

This notice is designed to clarify the sale and support status of Cisco® CallManager 3.1(X) and previous Cisco CallManager software releases.

Cisco CallManager is the software call-processing component of the enterprise IP telephony solution enabled by Cisco AVVID (Architecture for Voice, Video and Integrated Data). Cisco CallManager extends enterprise telephony features and capabilities to packet telephony network devices such as IP phones, media processing devices, voice-over-IP (VoIP) gateways, and multimedia applications. Additional data, voice, and video services such as unified messaging, multimedia conferencing, collaborative contact centers, and interactive multimedia response systems interact with the IP telephony solution through Cisco CallManager's open telephony applications programming interfaces (APIs). As such, the software content expands as it acquires improvements with each new release of Cisco CallManager. Each release does not constitute an end of Cisco Life; CallManager releases are replaced by a successor that provides enhancements to the former release. These subsequent releases, along with associated services and phone firmware loads, accumulate significantly more intensive component, system, and solutions testing than any previous version of Cisco CallManager.

Cisco CallManager 3.1(1) was released on Cisco.com on July 31, 2001, and was further enhanced and substituted by several maintenance and feature releases ending with Release 3.1(4). As each new release became available, it became a better alternative to a previous release, so that, over time, demand for the previous release versions decreased. With previous releases compatibility was ensured through extensive testing. This notice applies to all versions of Cisco CallManager 3.1(X). Sales of these releases ended on December 18, 2003, with the availability of Cisco CallManager 3.3(2).

Customers can choose to continue using Cisco on CallManager 3.1(X). Customers with the appropriate support contract will continue to receive support form the Cisco Technical Assistance Center (TAC). However, customers with 3.1(X) releases deployed who encounter stability or defect issues that have been corrected in releases 3.2(X), 3.3(X) or 4.0 will be directed to upgrade to these versions to resolve the defects. The last maintenance version for Cisco CallManager 3.1 was 3.1(4). Limiting the number of orderable Cisco CallManager releases improves customer satisfaction with Cisco IP Communications solutions by allowing Cisco Systems® to concentrate more engineering resources on improved quality and performance in current releases.

Cisco CallManager customers are encouraged to take advantage of new and updated features that address security and interoperability components. Customers with current Software Application Support plus Upgrades (SASU) contracts may upgrade to Cisco CallManager 3.3 or 4.0 with no software charge. Standard support allows for upgrades to the last release on the current trains and the last maintenance release on the two previous trains. For more information about supported upgrades and compatibility with other Cisco application releases, please visit:

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/ccmcomp.htm.

Customers currently running an environment with Cisco CallManager 3.1 must obtain Cisco CallManager 3.3 Upgrade (SW-CCM-3.3-UPG=). Customers who have a current SASU contract can order this stock-keeping unit (SKU) at no charge using the Product Upgrade Tool (PUT), which is located at: http://www.cisco.com/upgrade.

The customer must order one SW-CCM-3.3-UPG= for each Cisco CallManager server that is being upgraded.

Upgrades to Cisco CallManager 3.3 require a fresh install of the operating system. Customers must therefore install the upgrade from a newly ordered package of Cisco CallManager 3.3 CD-ROMs. Upgrades from downloadable CCO images are not possible with the upgrade to version 3.3. The set of CDs in the upgrade package allows for software upgrades to existing Cisco MCS platforms, the Cisco SPE 310 and all supported third party platforms.

Please note that the current system (with 3.1) MUST first be upgraded to CallManager 3.3 before an upgrade to CallManager 4.0 is attempted. In addition, a migration to a new server may also be required. The following servers are not supported with CallManager 4.0,

For more information on upgrading to Cisco CallManager 4.0, please go to, http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_installation_guide_book09186a008024ec49.html

As above customers with current SASU contracts may go to, http://www.cisco.com/upgrade

For customers that currently do not have a SASU contract the following table should be used to determine the SKU that needs to be ordered.

When upgrading to Cisco CallManager 4.0, an upgrade SKU must be purchased for every server being migrated to Cisco CallManager 4.0.

Customers intending to go to Cisco CallManager 4.0 who have upgraded to Cisco CallManager 3.3 and who have servers not supported by Cisco CallManager 4.0 can retain their investment in the Cisco CallManager software they have already purchased. The migration has two components that can provide credit to the customer. The first component is a credit for the existing Cisco CallManager software when trading up to a new Cisco CallManager software installation that supports the new server. The second component is a hardware credit for returning an existing Cisco MCS when a new Cisco MCS Server is being purchased.

Cisco CallManager uses a value price model where the price of Cisco CallManager is determined by the number of IP phones being supported on the server platform. Table 3 outlines the current pricing steps for Cisco CallManager.

To determine the cost of the software component of the upgrade, perform the following steps:

Repeat this process for each server being replaced.

To determine the credit to be obtained when trading in a Cisco MCS for a new Cisco MCS, use the Cisco Technology Migration Program (CTPM) located at http://www.cisco.com/offer/tic/TMP_PA.html. Repeat this process for each Cisco MCS platform being replaced by a Cisco MCS platform. Please note that no credit will be provided for customers migrating from a third-party platform to a Cisco MCS platform or for customers migrating from a Cisco MCS platform to a third-party platform.