[Home]

Summary:ASTERISK-26301: rtp_engine: ast_rtp_codecs_payload_code Crash
Reporter:Ross Beer (rossbeer)Labels:
Date Opened:2016-08-17 06:15:37Date Closed:2020-01-14 11:14:09.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/RTP Resources/res_rtp_asterisk
Versions:13.10.0 Frequency of
Occurrence
Related
Issues:
Environment:Fedora Server 23Attachments:( 0) backtrace_20160817_clean.txt
Description:Crash on unlock of codecs
Comments:By: Asterisk Team (asteriskteam) 2016-08-17 06:15:38.588-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: Rusty Newton (rnewton) 2016-08-18 09:15:22.133-0500

Thanks for the report.

Was this one-off or is it repeatable?

What was happening at the time of the crash, can you include a messages/full log?



By: Asterisk Team (asteriskteam) 2016-09-01 12:00:00.489-0500

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