[asterisk-bugs] [Asterisk 0016713]: PRI locks randomly, hangup cause 102, "recovery on timer expiry".

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16713 
====================================================================== 
Reported By:                alecdavis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16713
Category:                   Channels/chan_dahdi
Reproducibility:            random
Severity:                   block
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 241456 
Request Review:              
====================================================================== 
Date Submitted:             2010-01-27 04:21 CST
Last Modified:              2010-01-27 17:41 CST
====================================================================== 
Summary:                    PRI locks randomly, hangup cause 102, "recovery on
timer expiry".
Description: 
Every week once or twice our PRI locks up. The easiest way I've found to
get it started again is to issue at the CLI 'dahdi restart'

When it is locked up, inbound pri calls are not accepted.

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

---------------------------------------------------------------------- 
 (0117278) alecdavis (developer) - 2010-01-27 17:41
 https://issues.asterisk.org/view.php?id=16713#c117278 
---------------------------------------------------------------------- 
uploaded full debug trace 28-01-10-missed-setup.txt

Below while this happended I was capturing the Jtec dchannel with Jtec
tools.
 
0248 E1M-B    100128 11:03:14.72 Q.931 SETUP                   C/Ref 6092 
Org
0251 E1M-B    100128 11:03:23.79 Q.931 SETUP                   C/Ref 6092 
Org
0253 E1M-B    100128 11:03:29.00 Q.931 RELease                 C/Ref 6092 
Org
0255 E1M-B    100128 11:03:34.00 Q.931 RELease                 C/Ref 6092 
Org

0259 E1M-B    100128 11:03:47.29 Q.931 SETUP                   C/Ref 6093 
Org
0261 PBX-A    100128 11:03:47.29 Q.931 CALL PROCeeding         C/Ref 6093
Dest
0262 PBX-A    100128 11:03:47.35 Q.931 ALERTing                C/Ref 6093
Dest
0265 PBX-A    100128 11:03:50.42 Q.931 CONNect                 C/Ref 6093
Dest
0267 E1M-B    100128 11:03:50.53 Q.931 CONNect ACKnowledge     C/Ref 6093 
Org

Although there are a few seconds difference between systems the RELease 13
seconds before the next Successful setup corresponds with the astersik
debug log.

Asterisk didn't see the SETUP messages, but saw the RELEASE messages???? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-27 17:41 alecdavis      Note Added: 0117278                          
======================================================================