Guest

Cisco Unified Communications Manager (CallManager)

Field Notice: Upgrading to CallManager 3.2(1) Corrupts IP Phone Ring List


June 11, 2002



Products Affected

Cisco CallManager Version 3.2(1)

Problem Description

When upgrading from any version of Cisco CallManager 3.1 to Cisco CallManager 3.2(1) on the 7900 series phones, the only remaining rings under Settings >Ring types are chirp1 and chirp2, even if all of the ring files exist in the TFTP path.

Background

Development is unable to determine root cause of this defect at this time.

Problem Symptoms

Upon completion of upgrade to Cisco CallManager 3.2(1) from any version of Cisco CallManager 3.1, the available ring types are the default Chirp1 and Chirp2. This occurs even if the ringlist.xml file is populated with additional ring types. IP phones (CP-79xx) may also display Bad ring list file after initialization.

Workaround/Solution

Use the following steps to perform a workaround:

  1. Go to the CallManager CCMadmin web pages. Click Service \ Service Parameters and select Cisco TFTP.

  2. Select the TFTP server and click Advanced.

  3. Set the Enable Caching of Files at Startup parameter to False.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCdw93219 (registered customers only)

Ring list precieved as chirp 1 and 2 (partial file send)

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: