You need to find the call ID for the call via a show call active voice<br><br>Then...<br><br>clear call voice causecode 1 id [ID from call]<br><br>And that should clear the call... As for cause, we would need to see DSP version, etc...
<br><br><br><br>Jonathan<br><br><div><span class="gmail_quote">On 11/20/06, <b class="gmail_sendername">Kris Seraphine</b> <<a href="mailto:baryonyx5@gmail.com">baryonyx5@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
>From time to time I have customers who have problems with FXS ports 'locking up'. In most cases when this happens the port will be stuck in the S_WAIT_RELEASE state like so.<br><br> 2/0/2 None - S_WAIT_RELEASE FXSLS_ONHOOK
<br><br>I've not found any way to clear this except reloading the router. I'm wondering if anyone can give me some insight as to why this happens and if there's a way to clear the port when it does. <br><br>In this particular case, the connected device is a fax machine. Is it possible that the fax machine is causing some voltage on the line that is seizing the port? If so, can anyone recommend a surge protector to protect against this?
<br><br>This particular customer is running a 2821 with a HD-NM and 12.4(XC)4 but I've had the problem with VIC2-4FXS/DID cards as well. <br><br>Thanks<br><br clear="all"><br>-- <br><span class="sg">kris seraphine
</span><br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br></blockquote></div><br>