<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.5">
<TITLE>Re: [cisco-voip] Intercluster-trunk calls not working in one direction</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText47853 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Ryan,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>the CSS is well configured... Can you point
me to a good translator to troubleshoot this issue?</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Thanks,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Ruben</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Ryan Ratliff
[mailto:rratliff@cisco.com]<BR><B>Sent:</B> Mon 16/04/2007 19:41<BR><B>To:</B>
Ruben Montes (Europe)<BR><B>Cc:</B>
cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip]
Intercluster-trunk calls not working in one direction<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>ICT calls are just H.323 with an extra IE added for CM stuff
so <BR>troubleshoot it just like an H.323 gateway. Point your
favorite <BR>Q931 translator at the CCM traces and see what's there
(alternatively <BR>get a sniffer capture from the originating CM of the
failed call). <BR>Does the CM send the H.225 Setup message?
What happens from there?<BR><BR>If the CSS on the branch office's Trunk going to
the central site was <BR>removed then you'll get unallocated/unassigned
number in the H.225 <BR>Release Complete.<BR><BR>-Ryan<BR><BR>On Apr 16,
2007, at 1:31 PM, Ruben Montes ((Europe)) wrote:<BR><BR>Hello,<BR><BR>I have one
central site CCM cluster that connects with two branch <BR>offices (1 and
2), each one with each own CCM cluster (pub+sub).<BR>We have configured
intercluster trunks between all of them.<BR><BR>We are having a problem
stablishing calls in one direction between <BR>the central site and one of
the branch offices. From the central site <BR>point of view, configuration
is the same for both branch offices <BR>(device pool, partition, CSS,
etc...).<BR>One intercluster trunk is working fine in both directions
(with <BR>branch office 2), but in the other one, calls are only working in
one <BR>direction (from branch office to central site). From the
other <BR>direction calls are not being established.<BR><BR>I have tried to
change the CCM preference in the trunk configuratioin <BR>in both endpoints
with always the same result: calls only working <BR>from Branch Office 1 to
Central Site.<BR><BR>I'm really stuck with this, any help would be greatly
appreciated...<BR><BR>Thanks in
advance,<BR><BR>Ruben<BR>_______________________________________________<BR>cisco-voip
mailing list<BR>cisco-voip@puck.nether.net<BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></FONT></P></DIV>
</BODY>
</HTML>