Summary:	ASTERISK-28814: Asterisk stops processing SIP requests because of an undetermined reason
Reporter:	Volodya Ivanets (Volodya)	Labels:
Date Opened:	2020-04-07 07:57:40	Date Closed:	2023-01-25 11:32:02.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:	13.29.1	Frequency of Occurrence	Occasional
Related Issues:
Environment:	CentOS release 6.10 x64 Kernel version is: 2.6.32-754.24.3.el6.x86_64 Mysql version is: 5.1.73-8	Attachments:
Description:	Our system randomly stops processing SIP requests. I don't know the exact reason why. When it's happening I can execute any Asterisk CLI command. But "sip reload" command will be accepted only one time. The reload will not actually happen. Asterisk returns message about previous sip reload not finished when trying to repeat the command. I have Asterisk core dump from when this was happening that I can provide. Thank you.
Comments:	By: Asterisk Team (asteriskteam) 2020-04-07 07:57:40.870-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: George Joseph (gjoseph) 2020-04-07 10:33:57.027-0500 The chan_sip channel driver is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available. Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1] If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way. [1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process [2]: http://www.asterisk.org/community/discuss [3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties You should attach the output from ast_coredumper to make it easier for a community member that may have time to investigate. Did this issue occur with earlier releases of Asterisk?  If not, what was the first release that has the problem? By: Volodya Ivanets (Volodya) 2020-04-08 04:15:49.499-0500 Hello, This problem was first noticed on Asterisk version 13.27. But I can not confirm if it would not happen on previous versions. Also, it looks like any attachment will be accessible for everyone. Is this true, how can I make sure that only required people have access to the core dump? Thank you! By: George Joseph (gjoseph) 2020-04-08 13:13:53.098-0500 If your attachment has sensitive data you can either alter the sensitive data before posting it or wait until someone can work your issue then arrange to share it with them privately. By: Volodya Ivanets (Volodya) 2020-04-09 04:21:21.428-0500 Got it. Thank you.