I have a 4224 configured as an MGCP device so it registers all its FXS ports with CallManager. It is also configured with some H323 for use during SRST failover. Before failover all devices can dial and recieve calls to both the pstn and locally. After a failover occurs and then the failover ends and is running normally again, the analog devices can no longer make outgoing calls. They get a fast busy as soon as I try to dial a number. Any thoughts?
Do the ports show registered in callmanager? There was a bug on the vg200 that once they drop a mgcp keep alive it would never try to register again. It sounds something like that, because it will drop keep alives while it can not connect to the CCM. Then when it comes back up it will not try again.
After trying it again, it does say the ports are "Registered to Cisco Call Manager" on the Gateway Configuration page. Any other thoughts? I do have debugs from the local gateway and the remote gateway, as well as a trace from CCM.
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...