Summary: | ASTERISK-30228: Lot of „Autodestruct on dialog with owner SIP/XXXX in place (Method: BYE). Rescheduling destruction for 10000 ms“, and finally „taskprocessor.c: The 'stasis/p:channel:all' task processor queue reached 500 scheduled tasks“ | ||
Reporter: | Vitalij Bogomolnikov (Vito) | Labels: | |
Date Opened: | 2022-09-14 11:51:58 | Date Closed: | |
Priority: | Critical | Regression? | Yes |
Status: | Open/New | Components: | Channels/chan_sip/CallCompletionSupplementaryServices |
Versions: | 16.8.0 | Frequency of Occurrence | Frequent |
Related Issues: | |||
Environment: | Ubuntu 20.04 LTS | Attachments: | |
Description: | We encountered with strange Asterisk hanging. We have a lot of Asterisk servers connected to a lot of providers, but this problem exists only with Asterisk servers connected to one provider.
Sometimes (randomly: one time per week or sometimes per day) Asterisk can't correctly Hangup incoming call. We see a lot of Warnings "Autodestruct on dialog with owner SIP/XXXX in place (Method: BYE). Rescheduling destruction for 10000 ms". Then we get Warning „taskprocessor.c: The 'stasis/p:channel:all' task processor queue reached 500 scheduled tasks“. We don't find any way to destroy bad channel from CLI. Only one way help - Asterisk restart. We tried to change different SIP settings, but unsuccessfully. Please help us to resolve this problem. We made a some coredumps. How to send files to you? | ||
Comments: | By: Asterisk Team (asteriskteam) 2022-09-14 11:52:04.036-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Joshua C. Colp (jcolp) 2022-09-14 12:21:57.292-0500 Just to chime in before this gets fully triaged - there is no sending files to Sangoma. You can attach files here, but chan_sip is not supported by Sangoma. By: George Joseph (gjoseph) 2022-09-16 08:02:40.913-0500 The chan_sip channel driver is in 'deprecated' 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 |