[asterisk-bugs] [Asterisk 0013136]: [patch] sip peer qualified failed, asterisk lock.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13136 
====================================================================== 
Reported By:                pabelanger
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   13136
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-07-23 02:32 CDT
Last Modified:              2009-09-30 13:52 CDT
====================================================================== 
Summary:                    [patch] sip peer qualified failed, asterisk lock.
Description: 
We just had asterisk lock on us tonight.  Best we can guess is because we
lost our SIP PEER (via qualify).

See output from 'show core locks'.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0015894 SIP register via tls causes lock on sip...
====================================================================== 

---------------------------------------------------------------------- 
 (0111668) dvossel (administrator) - 2009-09-30 13:52
 https://issues.asterisk.org/view.php?id=13136#c111668 
---------------------------------------------------------------------- 
Awesome, I can see how that should work now, but it is still not perfect.
Connections that never timeout still never go away, they are just moved
into a separate thread.  This is at least a step in the right direction
though.  I plan on following up with a separate patch to address this. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-30 13:52 dvossel        Note Added: 0111668                          
======================================================================