Summary:	ASTERISK-25349: Asterisk freeze due to schedule ID cancellation failure
Reporter:	Philip Mott (nexbridge)	Labels:
Date Opened:	2015-08-27 05:52:28	Date Closed:	2020-01-14 11:24:14.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Channels/chan_sip/General
Versions:	1.8.32.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Linux Debian 7.7 3.2.0-4-amd64	Attachments:
Description:	The issue starts when we get a schedule ID warning from Asterisk, of which I have provided a few examples below.  Then over the next minute or so Asterisk seems to seize up, in that it stops processing any SIP data and calls stop flowing.  The only way to resolve the issue seems to be to restart Asterisk.  Unfortunately we are unable to provide a backtrace, as implementing debugging symbols is not an option as Asterisk being used in a high-performance production environment and we do not know how to replicate the issue ourselves.  I really hope you are able to fix this soon, as we route over 100 million calls per month and it is the only major source of instability we have found in your platform. WARNING[41873] chan_sip.c: Unable to cancel schedule ID 1294416.  This is probably a bug (chan_sip.c: send_response, line 4400). WARNING[1473] chan_sip.c: Unable to cancel schedule ID 2566854.  This is probably a bug (chan_sip.c: sip_hangup, line 6605). WARNING[1494] chan_sip.c: Unable to cancel schedule ID 177341.  This is probably a bug (chan_sip.c: update_provisional_keepalive, line 4341).
Comments:	By: Asterisk Team (asteriskteam) 2015-08-27 05:52:29.890-0500 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Asterisk Team (asteriskteam) 2015-08-27 05:52:31.051-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].