[cisco-voip] Intercluster-trunk calls not working in one direction

[Ryan Ratliff]

ICT calls are just H.323 with an extra IE added for CM stuff so  
troubleshoot it just like an H.323 gateway.   Point your favorite  
Q931 translator at the CCM traces and see what's there (alternatively  
get a sniffer capture from the originating CM of the failed call).   
Does the CM send the H.225 Setup message?  What happens from there?

If the CSS on the branch office's Trunk going to the central site was  
removed then you'll get unallocated/unassigned number in the H.225  
Release Complete.

-Ryan

On Apr 16, 2007, at 1:31 PM, Ruben Montes ((Europe)) wrote:

Hello,

I have one central site CCM cluster that connects with two branch  
offices (1 and 2), each one with each own CCM cluster (pub+sub).
We have configured intercluster trunks between all of them.

We are having a problem stablishing calls in one direction between  
the central site and one of the branch offices. From the central site  
point of view, configuration is the same for both branch offices  
(device pool, partition, CSS, etc...).
One intercluster trunk is working fine in both directions (with  
branch office 2), but in the other one, calls are only working in one  
direction (from branch office to central site). From the other  
direction calls are not being established.

I have tried to change the CCM preference in the trunk configuratioin  
in both endpoints with always the same result: calls only working  
from Branch Office 1 to Central Site.

I'm really stuck with this, any help would be greatly appreciated...

Thanks in advance,

Ruben
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip