Summary:	ASTERISK-14864: Faulty SIP device caused not just asterisk but the entire system to lock up every 20 minutes on the DOT!
Reporter:	John S. (johnakabean)	Labels:
Date Opened:	2009-09-22 14:03:52	Date Closed:	2011-06-07 14:01:07
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_sip/Registration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
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. ****** ADDITIONAL INFORMATION ****** Running CentOS fully updated (including kernel) from Centos repository. Asterisk was configured with default options.
Comments:	By: Jason Parker (jparker) 2009-09-22 14:04:24 Per bug reporting guidelines, we need SIP debug and console output. By: John S. (johnakabean) 2009-09-22 14:05:25 I will gladly send you the faulty device so you may use it to try to make asterisk more stable in any of these cases. By: John S. (johnakabean) 2009-09-22 14:08:40 I will add the device back to the network and post anything related to it with sip debugging later but, at the moment, I can't afford a lockup. By: Leif Madsen (lmadsen) 2009-09-23 09:39:20 Setting this to feedback while we await the reporter to provide some information that allows us to move this forward. By: John S. (johnakabean) 2009-09-23 14:37:51 Whatever the bad device is doing, asterisk is locking up the system before showing what was sent from the device in the console with "sip debug ip (deviceip)" By: John S. (johnakabean) 2009-09-23 14:38:54 doesn't appear in the log either By: Tilghman Lesher (tilghman) 2009-09-24 03:06:18 In that case, it's probably best to obtain a packet dump, with tcpdump or wireshark. By: Kirill Katsnelson (kkm) 2009-09-24 03:06:26 @johnakabean: just a suggestion, you might want to use tcpdump(8) to capture SIP exchange with the device. By: Leif Madsen (lmadsen) 2009-09-30 10:37:01 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. By: Leif Madsen (lmadsen) 2009-10-26 09:56:09 Closed due to lack of feedback. If the reporter is able to provide the requested information, please reopen this issue. Thanks!