| Summary: | ASTERISK-27388: Action QueueStatus - AMI, causing "Segmentation fault" | ||
| Reporter: | Roger Pitigliani (rogerpitigliani) | Labels: | |
| Date Opened: | 2017-10-31 22:54:19 | Date Closed: | 2020-01-14 11:14:14.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_queue Core/ManagerInterface |
| Versions: | 15.0.0 15.1.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Debian 9 Stretch I3 4GB | Attachments: | |
| Description: | Whenever there is a call waiting in queue, when I execute a "QueueStatus" action via http/ami, then Asterisk dies.
Action by the url below http://asteriskhost:8088/mxml/?Action=QueueStatus If there are no waiting calls, the Action responds normally. With Asterisk 14.x, works fine. The QueueEntries are displayed normally and the Asterisk does not stop. Att | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-10-31 22:54:20.310-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. 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-11-01 04:58:30.626-0500 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. Thanks! [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Asterisk Team (asteriskteam) 2017-11-15 12:00:00.833-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 | ||