May 14, 2004
Products Affected
|
Product |
Comments |
|---|---|
|
Cisco CallManager |
3.3(4) -> 4.0(1) Feature loss |
|
Cisco Enterprise IP Telephony products (Cisco IVR, ICD, IPCC Enterprise and Express, etc) |
Version compatibility must be verified |
|
3rd party products |
Version compatibility must be verified |
Problem Description
Cisco CallManager 3.3(4) to 4.0(1) upgrade and feature loss considerations:
Some features that are available in Cisco CallManager 3.3(4) do not exist in Cisco CallManager 4.0(1) (see Background section below). If you are currently using any of the following features, Cisco recommends that you do not upgrade until the Cisco CallManager release that supports the feature becomes available. If you decide that these features are not important to you, you can upgrade from Cisco CallManager 3.3(4) to 4.0(1), but you lose the 3.3(4) feature-specific data when you upgrade to 4.0(1). After you upgrade to the Cisco CallManager release that provides the features, for example, Cisco CallManager 4.1, you must configure the features again if you want to use them with that release.
Likewise, architectural enhancements introduced in Cisco CallManager 4.0(1) have caused other upgrade/data migration considerations. To ensure system stability, review the Cisco CallManager release notes and upgrade document for specific details.
Cisco Enterprise IP Telephony application compatibility considerations:
Cisco CallManager 4.0(1) also required some changes to API/Interfaces. Therefore, some Cisco IP telephony applications required changes. To ensure that version compatibility and functionality exist after the upgrade, review the Cisco CallManager Compatibility Matrix.
3rd party/AVVID Partner application compatibility considerations:
The changes to the API/Interfaces may also interfere with the compatibly of Cisco-approved, third-party and Cisco AVVID Partner Program applications. Cisco's AVVID Partner Program and Technology Affiliate Program requires Interoperability Verification Testing against Cisco CallManager 4.0. To determine "verification" status of a 3rd party application, please go to IP Communications Applications Central, under "Application Partner Search" for AVVID Partners - Cisco AVVID Technology Affiliate Search
(Click Application Search or Application Partner Search. When the Application Search page displays, choose the criteria for the search from the drop-down list boxes. Then, click Search.)
Background
In March 2004, Cisco CallManager 3.3(4) released. Cisco CallManager 3.3(4), a maintenance release for the Cisco CallManager 3.3 branch, addresses caveats and introduces support for the following features in the table:
Forced Authorization Codes and Client Matter Codes
Cisco WebDialer
Cisco IP Telephony Backup and Restore System (BARS)
Extension Mobility Enhancements
Cisco Security Agent
Dialed Number Analyzer (DNA)
Image Authentication
NM-HDV2 and NM-HD Support for Cisco CallManager Conferencing Enhancements
Conferencing Enhancements
Block External To External Transfer Service Parameter
International Dial Plan
Calling Search Space Enhancements
Default Trace Level Changed for Cisco Database Layer Monitor Service
For a description of these features, refer to the Release Notes for Cisco CallManager Release 3.3(4).
Problem Symptoms
Cisco CallManager 3.3(4) to 4.0(1) upgrade and feature loss considerations:
Three of the features listed above are not supported in Cisco CallManager 4.0(1).
|
Feature |
Notes |
|---|---|
|
Forced Authorization Codes and Client Matter Codes |
Forced Authorization Codes and Client Matter Codes will not be addressed in Cisco CallManager 4.0, but will be introduced in Cisco CallManager 4.1 to be released in late 2004. |
|
Conferencing Enhancements Block External To External Transfer Service Parameter |
Conferencing Enhancements and Block External To External Transfer Service Parameter are addressed in 4.0(1)SR2 targeted to release in May 2004. |
If you are currently using any of the preceding features, Cisco recommends that you do not upgrade until the Cisco CallManager release that supports the feature becomes available. Otherwise, you will lose the desired functionality and data.
Other upgrade issues:
Cisco CallManager 4.0(1) upgrade also includes some new caveats that have not been resolved . Some of the known issues are listed in the table:
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
|
Issue |
Description |
|---|---|
|
CSCee30571 - Route/Hunt List Redundancy Lost After Upgrade to 4.0(1). |
After an upgrade to Cisco CallManager 4.0(1), route/hunt lists lose redundancy. This issue is slated to be resolved in 4.0(2), which is targeted for August 2004. Since this is a migration issue and not a defect in the core CallManager code, the system administrator can set up the proper redundancy after the upgrade. |
|
CSCed85385 - Default behavior for CF CSS = should be none. |
On forwarded calls, the calling party's Calling Search Space (CSS) will be used instead of the called party's CSS. This could cause some undesired results when forwarding calls. The resolution of this issue will be delivered in 4.0(2) targeted for August 2004. |
|
CSCee08148 - CP7935 fails to reboot after failed upgrade. |
When a firmware upgrade for a Cisco IP Phone 7935 fails due to timeout from a TFTP server or other network disruption, the device is left in an unrecoverable state. Cisco plans to generate a separate field notice to discuss this problem in detail. A workaround will be provided which includes downloading and installing the updated 7935 firmware load prior to the Cisco Call Manager 4.0 upgrade. |
|
CSCed55280 - 7935 un-mutes when second call is answered on same line. |
This issue will be resolved in a 7935 load that will be released later in May. |
For a complete list of upgrade issues, requirements and procedures, review the appropriate documentation by clicking the following URL: Cisco CallManager 4.0.
Cisco Enterprise IP Telephony application compatibility considerations:
As for all other Cisco CallManager upgrades, the compatibility matrix must be reviewed to ensure that all Cisco Enterprise IP Telephony applications that you are using are compatible with Cisco CallManager 4.0(1).
3rd party/AVVID Partner application compatibility considerations:
Cisco AVVID Partner Program and Technology Affiliate Program Interoperability Verification Testing have not completed interoperability vertification testing (IVT) for all applications that run with Cisco CallManager 4.0. All third-party applications in the Cisco AVVID Partner Program (APP) are subject to IVT for major feature releases, such as Cisco CallManager 4.0. Without IVT verification status, Cisco Technical Assistance Center (TAC) does not provide coordinated support for application integration with Cisco CallManager 4.0. To determine if the third-party product you have purchased has completed IVT, click Cisco AVVID Application Portal - Find a Partner.
Workaround/Solution
Cisco CallManager 3.3(4) to 4.0(1) upgrade and feature loss considerations:
Release Notes for Cisco CallManager Release 4.0(1)
Cisco Enterprise IP Telephony application compatibility considerations:
3rd party/AVVID Partner application compatibility considerations:
To determine if compatibility testing has been completed for a Cisco-approved, third-party application, refer to the following URLs:
IP Communications Applications Central
Cisco AVVID Technology Affiliate Search
(Click Application Search or Application Partner Search; when the Application Search page displays, choose the criteria for the search from the drop-down list boxes. Then, click Search.)
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
Receive Email Notification For New Field Notices
Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.