Guest

Preview Tool

Cisco Bug: CSCsy80531 - CUCM-BE upgrade can result in lost ringtone/tftpdata files

Last Modified

Feb 10, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

7.0(1)

Description (partial)

Symptom:

After CUCM-BE switch, ringtones are missing.

Conditions:

This only applies to CUCM-BE and does not apply to stand-alone CM or stand-alone Unity Connection.  There are three situations where this can occur.  All three situations involve having the following version either on the active or inactive partition:
7.0(1), 7.0(1) ES1 through 7.0(1) ES12 inclusive, 7.0(1)SU1 or 7.0(1)SU1a

Case 1.)
If upgrading from
7.0(1), 7.0(1) ES1 through 7.0(1) ES12 inclusive, 7.0(1)SU1 or 7.0(1)SU1a
to a newer version
and the upgrade was completed on a different day than the switch was done, the ringtones and other critical files on the system will get incorrectly removed by the Unity Connection Log File Aging Task.  The Log File Aging Task bug was corrected via CSCsv83436.  More specifically, if the upgrade was completed prior to 3:45 am and the switch was done after 3:45 am, the Log File Aging Task incorrectly deletes critical files including all of the ringtones from the inactive newer version.

Case 2.)
Upgrade from
7.0(1), 7.0(1) ES1 through 7.0(1) ES12 inclusive, 7.0(1)SU1 or 7.0(1)SU1a
to a newer version and switched over to the newer version prior to 3:45 am, avoiding case 1.
Then reverted to the older version and stayed on that older version past 3:45 am.
Once 3:45 am has passed, the bug in the older version corrupts the newer inactive version by incorrectly deleting critical files including all of the ringtones.

Case 3.)
Upgrade from an older version to
7.0(1), 7.0(1) ES1 through 7.0(1) ES12 inclusive, 7.0(1)SU1 or 7.0(1)SU1a
The Unity Connection Task Log File Aging will delete critical files (including ringtones) from the
older version.  Should not switch back to the old version unless the intention is to redo the upgrade.  Otherwise, the ringtones and other critical files will be missing on the older version.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.