First of all, check that the dns configuration is correct on the TMS and the VCS. Do an nslookup of the TMS servers FQDN in the commandline and see if it resolves to the correct ip. Do the same on the VCS (login via SSH as root).
If it resolves correctly, go to the admin tools, config, network settings and check that the IPv4 address and TMS FQDN matches the TMS servers actual settings.
If they match, reboot the TMS server and the VCS and try to re-enable it again. A couple of questions:
Is the TMS server added to a domain?
Is the TMS and the VCS on the same subnet?
Have you enabled replication on this VCS before or has it been working before at all?
Make sure the VCS is tracked by hostname.
If none of this helps you, please raise a TAC case on this.
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...