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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13136 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13136
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-23 02:32 CDT
Last Modified:              2008-11-19 09:53 CST
====================================================================== 
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'.
====================================================================== 

---------------------------------------------------------------------- 
 (0095069) putnopvut (administrator) - 2008-11-19 09:53
 http://bugs.digium.com/view.php?id=13136#c95069 
---------------------------------------------------------------------- 
I based my assumption that the write() was blocking because of the locks
which are currently held in blitzrage's latest core show locks output. I'm
not sure exactly what blitzrage's test setup is, but if there was something
which was previously causing the connect() to block, then I would be
willing to bet that in his test setup, the same obstruction is causing the
write() to also block.

However, if his setup was causing the connect() to block, I would expect
that the error returned would have caused the subsequent write() to not
occur. Are we certain that the connect() succeeded?

blitzrage, just to clarify, could you describe how you set up your tests
for this? Also, did you ever see a console error message like the
following:
"Unable to connect <something> to <something else>:<some reason>" ? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-19 09:53 putnopvut      Note Added: 0095069                          
======================================================================