CUCM 7.1.3 and CUCN 7.0.2 best practices for graceful shutdown f
Assuming you are simply moving the server (i.e. not changing the IP addresses) you can simply shut each down from the CLI (utils system shutdown) or OS Administration web interface (under system/version or something similarly obscure).
They should all boot fine and recover in any order, but you might boot the publisher first, veryify network connectivity etc before bringing up the other servers.
If you want to maintain service during the move and don't have SRST you might consider moving one CUCM at a time.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
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...
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 discusses the bas...