<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2900.2769" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=359523221-07102005><FONT face=Arial color=#0000ff size=2>I was
always taught that DNS Reliance in CCM was a Bad Thing?!?</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B>
cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net]
<B>On Behalf Of </B>Wes Sisk<BR><B>Sent:</B> Monday, October 24, 2005 4:25
PM<BR><B>To:</B> Lelio Fulgenzi; Burton, Jason<BR><B>Cc:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> RE: [cisco-voip] Intercluster
Trunk what am I missing?<BR><BR></FONT></DIV>
<DIV><SPAN class=224062421-24102005><FONT face=Arial color=#0000ff size=2>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.</FONT></SPAN></DIV>
<DIV><SPAN class=224062421-24102005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=224062421-24102005><FONT face=Arial color=#0000ff
size=2>/Wes</FONT></SPAN></DIV>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net]<B>On Behalf Of </B>Lelio
Fulgenzi<BR><B>Sent:</B> Monday, October 24, 2005 4:27 PM<BR><B>To:</B>
Burton, Jason<BR><B>Cc:</B> cisco-voip@puck.nether.net<BR><B>Subject:</B> Re:
[cisco-voip] Intercluster Trunk what am I missing?<BR><BR></FONT></DIV>
<DIV><FONT size=2>wait until IPv6 comes out and we have to remember stuf
like 3ffe:1900:4545:3:200:f8ff:fe21:67cf</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>*shiver*</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Network Analyst (CCS) * University of Guelph * Guelph,
Ontario N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"I had a coffee and Coke at lunch today...and now, I've got more jitter
than an<BR>IP phone on a long haul 10base2
connection"
LFJ</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=Jason.Burton@CoreBTS.com
href="mailto:Jason.Burton@CoreBTS.com">Burton, Jason</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=Jason.Burton@CoreBTS.com
href="mailto:Jason.Burton@CoreBTS.com">Burton, Jason</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, October 24, 2005 4:23
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] Intercluster
Trunk what am I missing?</DIV>
<DIV><BR></DIV>Man talk about a dumb butt attack. So I was banging my
head against the<BR>wall to find out I had a typo in the ip address for one
of the CM's.<BR>Geez go figure it works after you type in the right
one.<BR><BR>Thanks!<BR><BR>-----Original Message-----<BR>From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>[mailto:cisco-voip-bounces@puck.nether.net]
On Behalf Of Burton, Jason<BR>Sent: Monday, October 24, 2005 11:40 AM<BR>To:
Ryan Ratliff<BR>Cc: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
RE: [cisco-voip] Intercluster Trunk what am I missing?<BR><BR>Now that I
re-read my email this is a single CM to a single CM not a<BR>cluster.
Sorry about that.<BR><BR>-----Original Message-----<BR>From: Ryan Ratliff
[mailto:rratliff@cisco.com] <BR>Sent: Monday, October 24, 2005 11:18
AM<BR>To: Burton, Jason<BR>Cc: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
Re: [cisco-voip] Intercluster Trunk what am I missing?<BR><BR>CM won't
accept an H.225 Setup message from any device not in its
<BR>database. This goes for ICTs as well as regular voice
gateways. <BR>This is why your ICTs always need to be
fully meshed (ie all servers <BR>defined in the trunk on both
sides).<BR><BR>-Ryan<BR><BR>On Oct 24, 2005, at 12:09 PM, Burton, Jason
wrote:<BR><BR>Okay, I've setup an intercluster trunk on one CM cluster that
points <BR>to the foreign CM. I've setup a route pattern that
includes this <BR>trunk, however when I dial I get a busy tone.
What am I missing? Do <BR>I need to configure a trunk on the
other end to make one way calling <BR>function? Both are CM
3.3(4). After I get the test calls working <BR>I'll worry about
CAC and
AAR<BR><BR><BR><BR>Thanks!<BR><BR><BR><BR><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>