[asterisk-bugs] [Asterisk 0018629]: Possible deadlock on 1.6.2.12, 14 and 15

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18629 
====================================================================== 
Reported By:                justintonation
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18629
Category:                   Core/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.15 
JIRA:                       SWP-2961 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-01-17 01:22 CST
Last Modified:              2011-01-25 17:38 CST
====================================================================== 
Summary:                    Possible deadlock on 1.6.2.12, 14 and 15
Description: 
After hours to days the system appears to reach a deadlocked state.  SIP
phones lose registration, in-flight calls continue, no new calls can be
established.  Need a "service asterisk restart" to get going again.

Problem is usually first observed when phones lose registration (120
seconds between registrations).

System has never been observed to reach this state overnight or on a
weekend so it appears to only happen when the system is actively handling
calls.


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

---------------------------------------------------------------------- 
 (0131054) justintonation (reporter) - 2011-01-25 17:38
 https://issues.asterisk.org/view.php?id=18629#c131054 
---------------------------------------------------------------------- 
Thanks fsegatoz!

SNOMs and BLFs keep coming up - may not mean anything because people will
search for issues that report similar environments to their own, but it
does make you think...

I had a quick look and at our site we have 14 out of 35 phones with a BLF
subscribed to their own number.  This includes 3 of the four extensions
that are in the ringall queue on the main switchboard number which is where
most of the call action is.

Was there something specific that made you think that this self-monitoring
might be associated with the problem or were you in a situation where you
just had to try whatever you could think of to get the system running
reliably again? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-25 17:38 justintonation Note Added: 0131054                          
======================================================================