[asterisk-bugs] [Asterisk 0012766]: Failure of resetting of a PRI B-Channel causes deadlock in process

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12766 
====================================================================== 
Reported By:                mavetju
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12766
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-31-2008 01:31 CDT
Last Modified:              05-31-2008 04:33 CDT
====================================================================== 
Summary:                    Failure of resetting of a PRI B-Channel causes
deadlock in process
Description: 
By default, once every hour, the Asterisk system resets the channels of a
PRI. This workflow is based on "reset the first channel"; when the reset
gets acknowledged "let's reset the next channel" until all channels are
done. This works fine if all channels get acknowledged, but when an
acknowledgment isn't received, the whole system is deadlocked for that
PRI.

====================================================================== 

---------------------------------------------------------------------- 
 mavetju - 05-31-08 04:33  
---------------------------------------------------------------------- 
According to Figure A.4/Q.931 of the Q.931 specification this has to happen
with the T316 timer which isn't implemented in Asterisk but which is
optional. Their suggested timeout is 2 minutes. See chapter 5.5 of the
Q.931 specification. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-31-08 04:33  mavetju        Note Added: 0087602                          
======================================================================