Re: Changing CCM server name when migrating from 4.13 to 5.03
The TAC has told me that you have to use the same exact hostname and IP address when upgrading from 4.X to 5.X because CM is very dependent on DNS. You would think that someone could have writen a script in the installation that would go through and change all the references in the old database to what the user wanted in the new database. I was trying to bring up my 4.X database on a test 5.X server before attempting the upgrade on my production server. There is no way I'm going to do the upgrade on a production server without testing everything. Unfortunately, Cisco makes this extremely difficult to do. I have two option. Either bring down my current publisher so I can steal the IP address and hostname or set up a seperate network that has the same IP range. Seems a little ridiculous.
You could always upgrade to a new server with a different IP address in the past with CM 4.X and earlier as long as the hostname matched. I don't understand why they chose to change this in 5.X.
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...