[Home]

Summary:ASTERISK-29282: Frequently getting auto destruct messages even after restarting server or only asterisk (not entire server)
Reporter:govind anupam k (anupamgovind9)Labels:
Date Opened:2021-02-08 10:54:35.000-0600Date Closed:2021-02-22 12:00:00.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:18.2.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Attachments:
Description: Autodestruct on dialog '775d39544179cc0d23a671d65b78d7e2@IP:port' with owner SIP/abc1-00000019 in place (Method: BYE). Rescheduling destruction for 10000 ms
Comments:By: Asterisk Team (asteriskteam) 2021-02-08 10:54:37.652-0600

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: govind anupam k (anupamgovind9) 2021-02-08 11:02:55.071-0600

Please let me know on how it can be resolved  
By: Joshua C. Colp (jcolp) 2021-02-08 11:16:06.509-0600

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

However please note that chan_sip is community supported. This means it is up to the community to investigate and resolve any issues in it, if after providing the information something does seem to be present.

The chan_pjsip module on the other hand is supported by Sangoma and receives bug fix attention from Sangoma.
By: Asterisk Team (asteriskteam) 2021-02-22 12:00:00.559-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines