<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 23, 2016 at 2:04 PM, Jefferson B. Limeira <span dir="ltr"><<a href="mailto:jbl@internexxus.com.br" target="_blank">jbl@internexxus.com.br</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi everyone!<br>
<br>
Everyday some channels go to this situation:<br>
<br>
# asterisk -rx 'pri show channels'| head -n 32 | grep 'Yes No Idle Yes'<br>
PRI B Chan Call PRI Channel<br>
Span Chan Chan Idle Level Call Name<br>
1 1 Yes No Idle Yes<br>
1 2 Yes No Idle Yes<br>
1 6 Yes No Idle Yes<br>
1 13 Yes No Idle Yes<br>
1 14 Yes No Idle Yes<br>
1 17 Yes No Idle Yes<br>
1 18 Yes No Idle Yes<br>
1 19 Yes No Idle Yes<br>
1 20 Yes No Idle Yes<br>
1 21 Yes No Idle Yes<br>
1 22 Yes No Idle Yes<br>
1 23 Yes No Idle Yes<br>
1 24 Yes No Idle Yes<br>
1 25 Yes No Idle Yes<br>
1 26 Yes No Idle Yes<br>
1 29 Yes No Idle Yes<br>
<br>
This is an incoming calls only, and all calls on this channels are be rejected.<br>
Telco delivery calls on minor channel available, empowering my problem.<br></blockquote><div><br></div><div>You have not specified the Asterisk nor libpri versions involved. I know your<br>Asterisk version has to at least be mid-v1.8 in order to have the<br>"pri show channels" command.<br></div><div><br></div><div>The PRI call column being Yes is why those channels don't get any more calls.<br></div><div>You will need to find out what abnormal signalling causes the libpri call structure<br>to be left associated with the B channel. It could be glare, call aborted early,<br>hangup never completed, channel got RESTARTed, etc.<br><br></div><div>You will need to read [1] and use the CLI "pri set debug on span x" command.<br></div><div><br></div><div>Richard<br><br>[1] <a href="https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information">https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information</a><br></div></div><br></div></div>