[Home]

Summary:ASTERISK-29088: Autodestruct on dialog. Asterisk stopped working.
Reporter:Edi (edmond_dobrova@hotmail.com)Labels:
Date Opened:2020-09-21 02:17:09Date Closed:2020-10-04 11:43:57
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:16.13.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Hi there, i am having issue with asterisk since version 16.11.0. Every 3-5 days the asterisk stop working every extension get disconnected and nothing is working, after restarting asterisk everything works normal.I upgraded to asterisk 16.13.0 and still have the issue. My extensions are using PJSIP and my trunk is using SIP.I get a lot of these message:
WARNING[19077] chan_sip.c: Autodestruct on dialog 'ee4c92e28e7e61747e3dcc318545b978@0.0.0.0' with owner SIP/SIPTRUNKPROVIDER-00000f09 in place (Method: BYE). Rescheduling destruction for 10000 ms
Comments:By: Asterisk Team (asteriskteam) 2020-09-21 02:17:10.432-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) 2020-09-21 05:49:30.855-0500

We suspect that you have a deadlock occurring within Asterisk. Please follow the instructions on the wiki [1] for obtaining debug relevant to a deadlock. Once you have that information, attach it to the issue. Be sure the instructions are followed exactly as the debug may otherwise not be useful.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock

Additionally note that chan_sip is community supported, so if there is an issue within it then response times will reflect that - and there is no guarantee on whether it will be investigated at all.
By: Edi (edmond_dobrova@hotmail.com) 2020-09-22 02:17:34.785-0500

I changed Trunk from SIP to PJSIP and see if its going to happen again, if yes i will do the backtrace.Thanks
By: Edi (edmond_dobrova@hotmail.com) 2020-10-04 06:43:21.941-0500

It looks like the issue was with chan sip, since i moved to pjsip i dont have issue anymore.