<HTML>
<HEAD>
<TITLE>Re: [cisco-voip] Intercluster Dialing Issue</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Ryan,<BR>
Just timed a call and it began to ring at about fifteen (15) seconds after I pressed the last digit. Certainly looks like it’s waiting for more digits but I don’t see any dial patterns that seem to be pertinent. The numbers I’m dialing are in the 11xxx range and the only route pattern I have in there that begins with 11 is a 11XXX route pattern. I’ll see if I can get some traces set up to determine what’s happening.<BR>
<BR>
Thank You...<BR>
<BR>
<BR>
On 3/17/09 11:24 AM, "Ryan Ratliff" <rratliff@cisco.com> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>45 seconds is pretty long for interdigit timeout, it's 15 seconds by <BR>
default. Is the 45 seconds before you hear ringback or does it ring <BR>
for 45 seconds? How long into this does the phone you are calling to <BR>
actually start to ring?<BR>
<BR>
You need to look at CCM traces from both clusters and see the <BR>
timestamp of the call leaving the one cluster and arriving at the <BR>
other one. It may be an intermittent delay in the WAN.<BR>
<BR>
-Ryan<BR>
<BR>
On Mar 17, 2009, at 12:54 PM, Jim Reed wrote:<BR>
<BR>
Hello, everyone. My first post to this forum so will try to provide <BR>
enough info to fully explain the issue.<BR>
<BR>
We have two (2) Call Manager clusters connected via an MPLS WAN. <BR>
When I try to directly dial a five (5) digit extension on cluster B <BR>
from cluster A, the first time I dial the call can take up to forty-<BR>
five (45) seconds to connect. If I dial an extension, immediately <BR>
hang up and then immediately dial that same extension again, the call <BR>
goes right through. My first thought was that I had a conflicting <BR>
dial pattern that was waiting for more digits before timing out and <BR>
completing the call but that does not appear to be the case. Just <BR>
wondering if anyone else has run into a similar issue and what they <BR>
may have found the issue to be. This worked without issue for quite <BR>
some time so its likely some change that we made when adding another <BR>
location has caused the issue but thus far I have not been able to <BR>
track it down.<BR>
<BR>
Thank You...<BR>
--<BR>
Jim Reed<BR>
Technology Wrangler<BR>
Swift Communications, Inc.<BR>
970-683-5646 (Direct)<BR>
775-772-7666 (Cell)<BR>
<BR>
_______________________________________________<BR>
cisco-voip mailing list<BR>
cisco-voip@puck.nether.net<BR>
https://puck.nether.net/mailman/listinfo/cisco-voip<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
<BR>
-- <BR>
Jim Reed<BR>
Swift Communications, Inc.<BR>
970-683-5646 (Direct)<BR>
775-772-7666 (Cell)<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>