[cisco-voip] Intercluster Trunk what am I missing?
Wes Sisk
wsisk at cisco.com
Mon Oct 24 17:24:43 EDT 2005
CM also attempts a reverse DNS resolution and looks for that device name, so
you don't have to remember all those digits, so long as you include dns as
part of your IPT infrastructure.
/Wes
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Lelio Fulgenzi
Sent: Monday, October 24, 2005 4:27 PM
To: Burton, Jason
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Intercluster Trunk what am I missing?
wait until IPv6 comes out and we have to remember stuf like
3ffe:1900:4545:3:200:f8ff:fe21:67cf
*shiver*
----------------------------------------------------------------------------
----
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter than
an
IP phone on a long haul 10base2 connection"
LFJ
----- Original Message -----
From: Burton, Jason
To: Burton, Jason
Cc: cisco-voip at puck.nether.net
Sent: Monday, October 24, 2005 4:23 PM
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?
Man talk about a dumb butt attack. So I was banging my head against the
wall to find out I had a typo in the ip address for one of the CM's.
Geez go figure it works after you type in the right one.
Thanks!
-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Burton, Jason
Sent: Monday, October 24, 2005 11:40 AM
To: Ryan Ratliff
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] Intercluster Trunk what am I missing?
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
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20051024/a0e06f7e/attachment.html
More information about the cisco-voip
mailing list