[Home]

Summary:ASTERISK-29435: Asterisk crash occurs when reading audio callback in control stream file.
Reporter:Akshay (Akshaya_M)Labels:
Date Opened:2021-05-19 12:16:50Date Closed:2021-05-19 12:16:52
Priority:MajorRegression?No
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:11.3.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:OS - Red Hat Enterprise Linux Server release 6.3 (Santiago) Asterisk version - 11.3.0Attachments:
Description:While reading the audio callback messages from control stream, noticed core.
Observations:
1. On calling ast_readaudio_callback() SIGSEGV is seen.

#0  0x00000000004e17a8 in ast_frdup ()
No symbol table info available.
#1  0x00000000004d57c6 in ast_readaudio_callback ()
No symbol table info available.
#2  0x00000000004d5c89 in ast_fsread_audio ()
No symbol table info available.
#3  0x0000000000486d94 in __ast_read ()
No symbol table info available.

Comments:By: Asterisk Team (asteriskteam) 2021-05-19 12:16:50.934-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. 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/].
By: Asterisk Team (asteriskteam) 2021-05-19 12:16:51.739-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) 2021-05-19 12:16:52.476-0500

The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process.