PDF(91.6 KB) View with Adobe Reader on a variety of devices
ePub(69.1 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(67.3 KB) View on Kindle device or Kindle app on multiple devices
Updated:February 26, 2015
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes solutions to common issues that occur when you upgrade or migrate Cisco Unified Communications Manager (CUCM) with Prime Collaboration Deployment (PCD).
There are no specific requirements for this document.
The information in this document is based on CUCM Releases 8.X, 9.X, and 10.X.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Problem 1. CUCM Release 8.6 to Release 10.x Upgrade Fails with Error "The selected file is not valid"
If you upgrade to CUCM Release 10.5(1) from a release earlier than CUCM 10.0(1), you must download and install ciscocm.version3-keys.cop.sgn on every node in the cluster. This Cisco Options Package (COP) file has the Rivest-Shamir-Addleman (RSA) keys required in order to validate the upgrade.
In order to improve software integrity protection, new public keys are used to sign CUCM Release 10.5.1. Prior to an upgrade from a release earlier than 10.0.1 to Release 10.5.1, the new keys must be installed on the previous server in order to validate the previous version server.
Problem 2. Migration from CUCM Release 6.x to CUCM Release 10.x Fails with PCD with Error "Invalid time zone" on CUCM
There are a few timezones that are not supported in CUCM Release 10.X, but are supported in CUCM Release 6.1.5. Change the timezone which is supported by CUCM 10.X. This issue is documented in Cisco bug ID CSCup50058.
Problem 3. Migration to CUCM 10.x with PCD Errors Out with "Login Timeout" during Export Task
The user selected for cluster discovery was an admin user added after CUCM installation. This issue is documented in Cisco bug ID CSCup43027.
Problem 4. Error "Failed to mount Cisco Prime Collaboration Deployments export as NFS store to the ESXi Host"
PCD is not compatible with all license types of VMware vSphere ESXi, because some of these licenses do not enable required VMware APIs. The PCD Admin Guide incorporates compatible licenses.
Problem 5. Phones Cannot Download Ringtone, Ringlist.xml, and Custom Background Image Files from the CUCM TFTP Server
After migration with PCD, the permission for the TFTP file/folder has changed. Contact the Cisco Technical Assistance Center (TAC) in order to apply the workaround. This issue is documented in Cisco bug IDs CSCus01744 and CSCui42799.