[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
Target Version:             1.6.0.5
Asterisk Version:           1.6.0 
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-02-27 16:46 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'.
====================================================================== 

---------------------------------------------------------------------- 
 (0100933) notthematrix (reporter) - 2009-02-27 16:46
 http://bugs.digium.com/view.php?id=13136#c100933 
---------------------------------------------------------------------- 
Recently This bug did not acounter anymore.
I changed 3 things.

1 set session timers to

session-timers=refuse
session-expires=110
session-minse=90
session-refresher=uas

2 set my grandstream ht-503 devices so they dont restart evryday when
checking for new firmware.
it wil be off air for 15 sec and then reconects.

3 I chached qualify to 5000

I noteced that when qualify response gets over 1999 it wil get (too
lagged)
Is it not that the default in qualify=yes valau is 2000?
maby it conflicts whit (too lagged) in some way?

atleast one of theese things must be related to it.
maby this info helps 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-27 16:46 notthematrix   Note Added: 0100933                          
======================================================================