I have two 2801 with FXO ports, both of them registered with the CM and I can place calls throught them with no problem. They're MGCP gateways.
Now I've configured two Route Groups, one for each gateway and crated one Route List containing those two route groups, with different prefixes (because each gateways connects to different carriers).
So I place one call to the PSTN and it takes the first Route Group of the Route List, as expected. When I place the second call (simultaneously), it takes the second Route Group (also expected, because I have just one port per gateway). No problem here.
If I disconnect the phone line of the FXO of the primary Gateway , all outbound calls take the secondary route group (still fine), BUT when I re-connect the line of the primary gateway, the CallManager doesn't forward calls to it anymore ! All calls go through the secondary gateway, even if the primary FXO line is already connected and the voice port appear as Registered on the CallManager.
This condition is just reversed when I issue a "mgcp / no mgcp" command on the primary gateway. After this command it start to pass calls again as it is the first option according to the Route List configuration.
*Jul 18 19:10:23.940: MGCP Packet sent to 172.18.1.254:2427--->
NTFY 330883188 aaln/S0/SU0/0@Gateway_1 MGCP 0.1
I also noted something that may help: when I disconnect the fxo line from the primary gateway and try to make a call, I see (debug voice ccapi inout) that some messages come to the gateway and, as there's no line, it alerts the CCM, then the CCM redirects the call to the secondary gateway. After this redirecting, I see that the gateway downloads a new .xml configuration file. Somehow, this same gateway will accept new calls only after the "no mgcp/mgcp" when a new .xml comes from the CCM.
I removed the "ccm-manager config" command and it seems that the router didn't received/asked for a new xml file, but it didn't help it anyway; the problem is still happening...
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...