| Summary: | ASTERISK-21296: SIP module not responding any more | ||||
| Reporter: | Gabriel Birke (describer) | Labels: | |||
| Date Opened: | 2013-03-18 09:39:18 | Date Closed: | 2013-03-25 08:50:32 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 1.8.20.1 11.2.1 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | SuSE Linux 3.0.58-0.6.2-default x86_64 | Attachments: | ( 0) 2_backtrace-threads.txt ( 1) 2_core-show-locks.txt ( 2) backtrace-threads.txt ( 3) core-show-locks.txt | ||
| Description: | Since our update from 1.8.17 to 1.8.20.x our Asterisk installation stops responding to SIP requests. Existing calls continue, but no new calls are processed and the connected phones lose their registration. "module reload" does nothing, only an asterisk restart alleviates the problem.
With 1.8.20.x the behavior occurs unpredictably every 3-7 days (usually in low traffic situations). We've tried updating to 11.2.1 but with this version the behavior occured in more random intervals between 1 and 36 hours. I'll attach the backtrace output after two of these incidents on 11.2 | ||||
| Comments: | By: Matt Jordan (mjordan) 2013-03-21 12:28:46.237-0500 This issue appears to be a duplicate of ASTERISK-21068. The backtrace shows a SIP REGISTER request being processed during execution of 'core show channels' By: Matt Jordan (mjordan) 2013-03-25 09:20:52.855-0500 If you can, please try the patch attached to ASTERISK-21068, ASTERISK-21068-1.8.diff. It should resolve the issue based on the backtraces attached to the various issues. | ||||