<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Look at CDR's to find the reason for the disconnects and go from
there. <br>
<br>
<a class="moz-txt-link-freetext" href="http://cc.bingj.com/cache.aspx?q=sisk+dropped+call&d=4869380558094460&mkt=en-US&setlang=en-US&w=478afbb6,93f4cb92">http://cc.bingj.com/cache.aspx?q=sisk+dropped+call&d=4869380558094460&mkt=en-US&setlang=en-US&w=478afbb6,93f4cb92</a><br>
<br>
Open a TAC case if you need assistance.<br>
<br>
/Wes<br>
<br>
On Tuesday, November 17, 2009 7:19:30 PM, Jim Reed
<a class="moz-txt-link-rfc2396E" href="mailto:jreed@swiftnews.com"><jreed@swiftnews.com></a>
wrote:<br>
<blockquote cite="mid:C7288BA2.2E03C%25jreed@swiftnews.com" type="cite">
<title>InterCluster Disconnects</title>
<font size="4"><font face="Verdana, Helvetica, Arial"><span
style="font-size: 14px;"><b>I will do my best to explain this as
clearly as possible. Please advise if additional information is needed.<br>
<br>
We have two (2) separate VoIP systems that communicate via intercluster
trunks across an MPLS WAN. For purposes of this discussion, we'll call
them System GPC and System CMNM. System GPC is 4.5-Meg MPLS and system
CMNM is 9-Meg MPLS.<br>
<br>
When the contact center number is dialed on System GPC, the calls are
forwarded to an extension (aka route point) on System CMNM that puts
the caller into the contact center script.<br>
<br>
The caller hears the initial recording with no problem. That recording
instructs the caller to press 2 for option A; press 3 for option B;
press 4 for option C; etc. etc.<br>
<br>
On somewhat frequent occasions, when the caller makes their selection,
the call is disconnected.<br>
<br>
This does not happen on calls that are placed to numbers associated
directly with System CMNM.<br>
<br>
System CMNM has a toll free number associated with the contact center.
When I forward the calls from System GPC to that toll free number
instead of the route point on System CMNM, there are no disconnects.<br>
<br>
I have reset the intercluster trunks between the two systems. When I
look at the call statistics in the router(s), they show the code for
normal call clearing.<br>
<br>
Anyone got any thoughts on why the selection of the CSQ option in the
script is causing that disconnect?<br>
<br>
I have looked at the T1 controller stats and the serial interface stats
associated with that PRI controller and there are no errors. System
GPC has no calling issues locally for calls that come in on those same
PRI channels.<br>
<br>
Thank You...<br>
</b></span></font></font><font face="Verdana, Helvetica, Arial"><b><font
size="2"><span style="font-size: 10px;">-- <br>
Jim Reed<br>
Technology Wrangler<br>
Swift Communications, Inc.<br>
970-683-5646 (Direct)<br>
775-772-7666 (Cell)<br>
<br>
</span></font><font size="1"><span style="font-size: 9px;"><i>“Not
only is it not right.<br>
It’s not even wrong.”<br>
</i> The Pauli Proverb<br>
Wolfgang Pauli</span></font></b><span style="font-size: 12px;"><br>
</span></font>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</body>
</html>