<div><br>DNA can be your friend then.</div>
<div> </div>
<div>CMIP/DNA (Dialed number analyser)</div>
<div> </div>
<div>Scott<br></div>
<div class="gmail_quote">On Tue, Mar 17, 2009 at 10:54 AM, Jim Reed <span dir="ltr"><<a href="mailto:jreed@swiftnews.com">jreed@swiftnews.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><font face="Verdana, Helvetica, Arial"><span style="FONT-SIZE: 12px">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...
<div>
<div></div>
<div class="h5"><br><br><br>On 3/17/09 11:24 AM, "Ryan Ratliff" <<a href="mailto:rratliff@cisco.com" target="_blank">rratliff@cisco.com</a>> wrote:<br><br></div></div></span></font>
<div>
<div></div>
<div class="h5">
<blockquote><font face="Verdana, Helvetica, Arial"><span style="FONT-SIZE: 12px">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>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br><br></span></font></blockquote></div></div><font face="Verdana, Helvetica, Arial"><span style="FONT-SIZE: 12px"><br><br>-- <br><font color="#888888">Jim Reed</font>
<div class="im"><br>Swift Communications, Inc.<br>970-683-5646 (Direct)<br>775-772-7666 (Cell)<br><br></div></span></font></div><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" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br></blockquote></div><br>