Hi all. I am having an issue getting my publisher and subscriber syncing up. I have had them up at one point, because I saw some route patterns I put in on both of them. But I came in today to work on them, I rebooted the publisher and now I cant seem to get them both to sync up. The Cisco Dirsync is running on the publisher, just not sure what else to look for. Any ideas?
Ok, sorry for the delay on this all. My goal here is if the Publisher dies (CUCM 6.1), then the Subscriber takes over without any issue. Well, when I took down the Publisher today (because I changed the default gateway on it), then the Subscriber didnt have the config I had initially put in for route patterns, etc. I had added two phones in on the Pub, but one wouldnt register because it was pointed to the Subscriber as the primary. To troubleshoot, I looked at the Subscriber to see why, and neither phone was there in the phones listing. The first one registered to the Publisher without issue. So, after the Publisher had rebooted and the gateway was correct, I had rebooted the Subscriber and then all was good. But, if the Publisher fails, I want the Sub to take over without issue, and not have to reboot it after the Publisher comes back up. Is there a way that this happens automatically?
All, I think I got this figured out. I put the sub as the first server, the pub second. I pull the network cable for the sub out, and phones register to pub. Put sub network cable back in and it re-registers to sub. I think this is how it should work. Thanks all.
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...