I have ran into a issue setting up redundancy on CallManager 3.2(3)ES8.2 cluster. We have a 2 server cluster, the Publisher being the secondary, and the Subscriber being the primary CallManager. All options but CMI are installed on each system to mirror configuations in the instance of a outage.
That being said, failover is working fine for all services. The only issue that we are having is that our pilot numbers (configured under WebAttendant) fail to work if the Subscriber (primary) goes or is taken down. I am using 2 pilot numbers right now to route to internal extensions (Voicemail and a a iPaq phone). When the Subscriber is down, I receive the "out of service" message from the LEC. When the subscriber comes back up, the numbers function without any issues. I have even went to the extent of restarting TCD when the subscriber was down to see if this would fix the issue.
Does anyone else have a idea on what is going on, or have I hit a bug? Please advise.
I find from the image name that you are running some Engineering Special image. So there are high chances that you are hitting a bug as these images are not thoroughly tested, i suppose. So I would suggest you to upgrade to the next available release image.
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...