When a user updates to Cisco CallManager version 3.2(3), all the entries in the corporate directory are lost

[TCC_2]

Core Issue

Normally, an upgrade Cisco CallManager has no effect on the corporate directory, so and unknown issue has occurred.

Resolution

In this case, the users listed in the corporate directory were not in the default Organizational Unit (OU). The Cisco CallManager administrator had created a custom OU for the users. During upgrades only the default OU is transferred over to the new version, and that container is OU=USER. The resolution of the issue is to transfer the list of users manually, rather than relying on the Cisco CallManager installation scripts to handle the action.

For more information, refer to these documents:

• Troubleshooting Guide for Cisco CallManager, Release 4.0(1): CallManager Installation, Backup and Restore Issues (For other versions of CallManager, refer to the CallManager Troubleshooting Guides index, select the appropriate troubleshooting guide and navigate to the Installation, Backup and Restore Issues chapter.)
• Fixing Problems with DC Directory
• Troubleshooting Guide for Cisco CallManager, Release 4.0(1): Directory Issues (For directory issues in other Callmanager versions, refer to the CallManager Troubleshooting Guides index, select the appropriate troubleshooting guide and navigate to the Directory Issues chapter.)
• Understanding the LDAP Directory for CallManager

Problem Type

Call control software  (CallManager, CallManager Express, ICS7750, SRST, SS7 call agents)

Call Control

CallManager

CallManager Features

Directory access

Common Software and Product Issues

Problems after an upgrade

Failure Type

Missing information: feature, item, file, field, number, parameter, data, settings, configuration, option, etc.

User Features

Corporate/global directory

CallManager Versions

CallManager 3.2