[asterisk-bugs] [Asterisk 0015935]: Faulty SIP device caused not just asterisk but the entire system to lock up every 20 minutes on the DOT!

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15935 
====================================================================== 
Reported By:                johnakabean
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15935
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.26.2 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-09-22 14:03 CDT
Last Modified:              2009-09-30 10:37 CDT
====================================================================== 
Summary:                    Faulty SIP device caused not just asterisk but the
entire system to lock up every 20 minutes on the DOT!
Description: 
Based on the every 20 minutes, I'm guessing its occurring during the
reregistration; so, the category may be incorrect. I have no zaptel devices
and am using Dahdi dummy.

I checked through the asterisk logs and found nothing with verbose 99
pertaining to that device other than registrations.
====================================================================== 

---------------------------------------------------------------------- 
 (0111640) lmadsen (administrator) - 2009-09-30 10:37
 https://issues.asterisk.org/view.php?id=15935#c111640 
---------------------------------------------------------------------- 
Can you try:  session-timers=refuse

And see if that helps at all? This is just a weird hunch for some reason
based on some other bug reports. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-30 10:37 lmadsen        Note Added: 0111640                          
======================================================================