I have a customer, they have two clusters, two CCM servers (Version3.1) on one site, and three CCM servers (version 3.3) on the other site. All intra culster IP calls and PSTN calls are good. They configured intercluster trunk on CCM 3.3 and intercluster H.323 gateway on the CCM3.1. It was working, they could make intercuster calls via the WAN from both sites.
But about 3-4 monthes ago, they upgrade the CCM 3.33 to 3.34 and after several days, they can not call from CCM3.1 to CCM3.3 via the WAN, the only way is via PSTN. The intercluster call from CCM 3.34 to CCM 3.1 is still working.
I tried from CCM 3.1 to dial 7078 which is a DN within CCM 3.3 cluter, when I press 707, I get the busy tone from the callmanager. It seem the intercluster gateway does not work.
I checked the CCM3.1 configuration, they have route pattern 7XXX point to the intercluster gateway.
Verify that the Trunk configuration contains the IP address/hostname of all Callmanager nodes contained in the device pool of the remote trunk. Please see the Remote Cisco CallManager Information section under Trunk Configuration Settings in the following link for further explanation.
Thanks for your reply. The trunk on CCM3.3 is working, we can make a call from CCM3.3 to CCM3.1 via the trunk.
The issue is on the CCM3.1, we can not make a call from CCM3.1 to CCM 3.3 via the WAN. We could not configure intercluster trunk on CCM3.1, a H323 intercluster gateway is being configured and it was working, and suddenly it stopped.
Did you try resetting the gateway on the CCM3.1 cluster?
The fact that you get a reorder tone after the 3rd digit sounds like a Calling Search Space problem. The problem also appeared out of no where which either means there was a bug with intercluster trunk, or something was changed on the CCM 3.1 cluster. If it is a bug, a reboot of the cluster should clear the problem until it happens again.
I'd suggest that you turn on detailed traces for the 3.1 cluster and collect traces for a failed call before you reboot the cluster.
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...