Backup in newer versions of callmanager, dont use the .sti file format. It simply archives all files and database info into a tar file. (Using BARS tool)
If you are trying to restore the info into a new server that is installed with CM 4.1, you should configure the new server with same name and ip. So the conclusion is that you cannot change the name on the new server and restore the old server's database which has the old servers name.
But, you can change the ip after the backup tar file has been restored.
If you are so keen on changing the name, you should do a manual transfer of config info from old server to new server (with name changed). You can BAT out existing phone config into CSV format and restore them in the new server.
If you are can have both the old server and new server available and on the network at the same time then build out the new server to the name that you want with a different IP address and do an inter-cluster trunk between the 2 Call Managers. If you have your call routing done properly you can move phones in small groups from the old server to the new one with minimal downtime.
This will also give you an on-line, immediate fallback if there are problems with the new server
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...