I have been trying to move a CUCM 7.1(5) cluster on MCS to 10.5(1) on UCS without much success.
Initially I tried to go from 7.1(5) to 10.5(1) by following the Jump upgrade process.
I successfully built a replica of the CUCM 7.1(5) cluster on the UCS servers and did a DRS restore.
When I tried doing an upgrade to CUCM 10.5(1) it failed on the database installation stage.
I raised a TAC case and was asked for logs which I provided but the Cisco Database Installation Service Log did not have any information for the failure.
The TAC engineer said that he had seen this before and it was a problem with dial plans installed on the server.
I had the UK dial plan installed so I rebuilt the cluster on UCS without installing dial plan, locales and phone firmware as I had previously. The only cop file I installed was the refresh upgrade file.
When I tried to upgrade I got the same error.
I was not getting much response from the TAC engineer so I thought I would try upgrading to CUCM 9.1(2) as an interim step. This worked fine and I took a backup then re-installed CUCM 9.1(2) to align the partitions then did a restore. Again this worked ok.
I then tried to install to 10.5(1). I installed the ciscocm.version3-keys.cop file and started the upgrade. It failed in exactly the same place and once again there was no database log.
The failure message I get in the install log is shown below:
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...