<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 20, 2012 at 2:22 AM, Steve Davies <span dir="ltr"><<a href="mailto:davies147@gmail.com" target="_blank">davies147@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im"><div class="gmail_extra">On 19 December 2012 21:54, Christopher Harrington <span dir="ltr"><<a href="mailto:chris@acsdi.com" target="_blank">chris@acsdi.com</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You probably already know this, but 1.4x is very old (released in 2006) and is officially end-of-life.<div><br></div><div>
<a href="https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions" target="_blank">https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions</a><br>
</div><div><br></div><div>You might get more help or better behavior by updating to a newer more current version of Asterisk, such as 1.8 which will be receiving bug fixes into October 2014.</div><div class="gmail_extra">
<br><br><div class="gmail_quote"><div><div>On Wed, Dec 19, 2012 at 3:47 PM, James Lamanna <span dir="ltr"><<a href="mailto:jlamanna@gmail.com" target="_blank">jlamanna@gmail.com</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div dir="ltr">Hi,<div>I have a PSTN Asterisk box that's connected to other dialplan PBXes through IAX2.</div><div><br></div><div>Recently this box was upgraded to 1.4.44 with the latest DAHDI version. I've noticed that if one of the dialplan PBXes calls Congestion(), the PRI will return ISDN code 34 (as its supposed to do).</div>
<div>However, the issue is that subsequent calls into that PRI channel are immediately responded by a Code 44 (channel not available) even though there is no live call on the channel.</div><div><br></div><div>Has anyone else experienced this behavior? Its a pretty crippling behavior since all of our channels eventually become unresponsive until a 'dahdi restart' is issued.</div>
<div><br></div><div>Thanks.</div><span><font color="#888888"><div><br></div><div>-- James</div></font></span></div>
</div></div></blockquote></div></div></blockquote></div><br></div></div><div class="gmail_extra">I believe that what you are describing is a very old bug, which is fixed somewhere in the 1.8 timeline when the interface between DAHDI and Asterisk is changed slightly. I encountered the same issue some time ago. I do not recall the exact conditions under which the issue happens, but I believe it is the attempt to cancel an unanswered inbound call with a specific subset of cause codes.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">If you are using an older Asterisk version, the only workaround is to use Playtones + Hangup() instead of sending the Congestion() or Busy() cause codes.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Regards,</div><div class="gmail_extra">Steve</div></div>
<br></blockquote><div style>Thanks Steve.</div><div style>It must have been introduced between DAHDI 2.4.0 and 2.6.1 or between Asterisk 1.4.35 and 1.4.44.</div><div style>I had a box running Asterisk 1.4.35 + DAHDI 2.4.0 and I never had any issues.</div>
<div style><br></div><div style>-- James</div><div style><br></div></div></div></div>