Also please verify if you have checked the option 'Run On All Active Nodes'. If so, please uncheck it and see if it helps.
As George said, If the call from cluster A is made with originating IP address x.x.x.x and if this address x.x.x.x is not defined as the destination in cluster B to A, then the calls will not be accepted.
if the CUCM version is 8.x and above, you can login into RTMT tool and check the session trace for the failed call. It will display the SIP message flow for the call. with the cause code, we can further troubleshoot it.
If the configurations looks good, please attach the CCM traces for the call failure with calling number, called number & time of call.
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...