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

noreply at bugs.digium.com noreply at bugs.digium.com
Wed Jul 23 09:36:49 CDT 2008


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-beta9 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-23-2008 02:32 CDT
Last Modified:              07-23-2008 09:36 CDT
====================================================================== 
Summary:                    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'.
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 07-23-08 09:36  
---------------------------------------------------------------------- 
Wow, there's something majorly wrong here. chan_sip and chan_zap both have
functions called "restart_monitor" and for some reason chan_zap is calling
the one defined in chan_sip.

That, however, does not explain why the lock which was legitimately
acquired in chan_sip has not been unlocked yet. It would be helpful to get
a backtrace of that thread to see where it's stuck. If you can provide the
output of "thread apply all bt full" from gdb, it would be helpful.

Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-23-08 09:36  putnopvut      Note Added: 0090604                          
======================================================================




More information about the asterisk-bugs mailing list