[Home]

Summary:ASTERISK-30493: I don't know the exactly what happening and what causing this issue but the issue i am facing that"Getting Autodestruct dialog message and when it occurs it will stoping and drops the calls"
Reporter:Vijay Kumar (Vijaykestrisk)Labels:
Date Opened:2023-04-14 08:47:17Date Closed:2023-04-14 08:47:21
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:13.23.1 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Centos 7 and HP ML10 Attachments:
Description:ERROR[14714] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
WARNING[12286][C-00005077] channel.c: Exceptionally long voice queue length queuing to Local/WPP39537@twowaycall-0000503a;1
WARNING[8453][C-00004fe2] chan_sip.c: Can't send 10 type frames with SIP write
WARNING[10611][C-00005033] channel.c: Exceptionally long voice queue length queuing to Local/WPP09331@twowaycall-00004ffd;1
WARNING[10295][C-00005024] channel.c: Exceptionally long voice queue length queuing to Local/WPP14530@twowaycall-00004fea;1
WARNING[14714] chan_sip.c: Autodestruct on dialog '1bc539cf24f3b1062453432b0a5d492d@10.0.10.17:5060' with owner SIP/server191021017-000052db in place (Method: BYE). Rescheduling destruction for 10000 ms
Comments:By: Asterisk Team (asteriskteam) 2023-04-14 08:47:20.719-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) 2023-04-14 08:47:21.891-0500

WARNING

JIRA will be going read-only at the end of April, 2023. We will be starting fresh on Github at https://github.com/asterisk/asterisk at that time. No issues or patches will be copied to Github. If you file an issue on JIRA at this time you will need to recreate it on Github after this date. The same applies if you have a patch.

WARNING

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/].