[asterisk-bugs] [Asterisk 0017865]: BRI NT ptmp: Active channels not cleard when i/f goes down

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Aug 25 19:44:11 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17865 
====================================================================== 
Reported By:                wimpy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17865
Category:                   Channels/chan_dahdi
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0-beta4 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-15 11:29 CDT
Last Modified:              2010-08-25 19:44 CDT
====================================================================== 
Summary:                    BRI NT ptmp: Active channels not cleard when i/f
goes down
Description: 
If the connection to the terminal is lost, while there are open channels on
the interface, red alarm is reported, but the open channels are never
cleared.

Additionally, if you manually try to channel request hangup, Asterisk
crashes.
====================================================================== 

---------------------------------------------------------------------- 
 (0126346) rmudgett (administrator) - 2010-08-25 19:44
 https://issues.asterisk.org/view.php?id=17865#c126346 
---------------------------------------------------------------------- 
I am not aware of any documented overview of what is done where in
dahdi/libpri/chan_dahdi.
Simply put:
dahdi - layer 1 hardware drivers
libpri - Q.921/Q.931 messaging
chan_dahdi/sig_pri - alarms, B channel allocation, some Q.931 overview
processing

Also libpri and chan_dahdi/sig_pri have their own data structures dealing
with specific calls.

B channel allocation and alarm handling are done in chan_dahdi/sig_pri
which is where I think your problem is to be found.

However, since the crash you are seeing is happening within libpri a
backtrace with an unoptimized asterisk and libpri may help.

To build libpri without optimization use this command after a make clean:
make LIBPRI_OPT= 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-25 19:44 rmudgett       Note Added: 0126346                          
======================================================================




More information about the asterisk-bugs mailing list