[cisco-voip] Intercluster Trunk what am I missing?

[Burton, Jason]

Now that I re-read my email this is a single CM to a single CM not a
cluster.  Sorry about that.

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Monday, October 24, 2005 11:18 AM
To: Burton, Jason
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?

CM won't accept an H.225 Setup message from any device not in its  
database.   This goes for ICTs as well as regular voice gateways.    
This is why your ICTs always need to be fully meshed (ie all servers  
defined in the trunk on both sides).

-Ryan

On Oct 24, 2005, at 12:09 PM, Burton, Jason wrote:

Okay, I've setup an intercluster trunk on one CM cluster that points  
to the foreign CM.  I've setup a route pattern that includes this  
trunk, however when I dial I get a busy tone.  What am I missing?  Do  
I need to configure a trunk on the other end to make one way calling  
function?  Both are CM 3.3(4).  After I get the test calls working  
I'll worry about CAC and AAR



Thanks!





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