[asterisk-bugs] [Asterisk 0014030]: mISDN layer stops working

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14030 
====================================================================== 
Reported By:                t-o
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14030
Category:                   Channels/chan_misdn
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-12-08 07:11 CST
Last Modified:              2009-02-04 09:45 CST
====================================================================== 
Summary:                    mISDN layer stops working
Description: 
After having accepted a lot of calls, the mISDN layer gets unusable; no
more calls are accepted.

asterix*CLI> misdn show channels
Chan List: 0x83872c0
bc with pid:0 has no Ast Leg
P[ 0] received 1k Unhandled Bchannel Messages: prim 120282 len 128
from addr 52010101, dinfo ffffffff on this port.

A restart of the asterisk software clears the problem.
====================================================================== 

---------------------------------------------------------------------- 
 (0099428) t-o (reporter) - 2009-02-04 09:45
 http://bugs.digium.com/view.php?id=14030#c99428 
---------------------------------------------------------------------- 
Some notes:

1)
The version information above was wrong.
The problem in the form described occurs in 1.4.21.2.
In 1.4.22, the "no ast leg" problem also occurs from time to time, but 
seems to vanish always by itself after some seconds.
Nevertheless, misdn.log keeps to get messages like
  Wed Feb  4 07:39:25 2009: P[ 1]   --> !! lib: No free channel!
  Wed Feb  4 07:39:25 2009: P[ 1]   --> we have already send
Release_complete
although there definitely would be free channels on other ports in the
same group.

2)
@picciuX: Yes, I agree that this looks quite similar! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-04 09:45 t-o            Note Added: 0099428                          
======================================================================