| Summary: | ASTERISK-27018: Crash in res_rtp_asterisk.c | ||||
| Reporter: | Jared Hull (fortytwo) | Labels: | |||
| Date Opened: | 2017-05-25 15:47:12 | Date Closed: | 2017-05-25 15:59:39 | ||
| Priority: | Critical | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_rtp_asterisk | ||
| Versions: | 13.15.1 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) crash.log ( 1) gdb.txt | |||
| Description: | We have an instance of Asterisk with 570 endpoints which processes some 2800 calls in a work day.
Unfortunately, we do not have a full verbosity asterisk logs. Hopefully someone might be able to make sense of our back trace and point us in the right direction? | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-05-25 15:47:13.307-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: Richard Mudgett (rmudgett) 2017-05-25 15:59:31.959-0500 This is already fixed by ASTERISK-26835 | ||||