| Summary: | ASTERISK-26817: autodestruct on dialog in place (method bye). rescheduling destruction for 10000 ms | ||
| Reporter: | Arnaldo R. Gonzalez Jimenez (chacaman) | Labels: | |
| Date Opened: | 2017-02-23 13:57:10.000-0600 | Date Closed: | 2017-02-23 14:02:51.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 11.25.1 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | OS: Centos 7 64bit Asterisk: 11.25 Test:Asterisk/Freepbx/Elastix/Triboxs Error: autodestruct on dialog in place (method bye). rescheduling destruction for 10000 ms CPU: Intel Xeon 8 Core 3.2Ghz 64GB Ram, RAID 0 SSD OS, RAID 5 SSD Asterisk | Attachments: | |
| Description: | Notes:
I have odbc configure and cdr_adtive to get the information in a second mysql database, I also have cel.conf enabled. The error: autodestruct on dialog in place (method bye) occurs when the second server of Mysql is slow in the part of inserting the registry in the database when the server gets slow then the asterisk starts to generate the error autodestruct on Dialog in place (method bye) and it is necessary to re-initiate the asterisk services, also happens when some dialplan logic is unresponsive in agi or extensions. In order to replicate the error you only have to configure a second mysql server to load it and try to start making calls from asterisk the asterisk start giving the error autodestruct on dialog in place (method bye) | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-02-23 13:57:11.034-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. 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]. By: Joshua C. Colp (jcolp) 2017-02-23 14:02:45.891-0600 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 | ||