[Home]

Summary:ASTERISK-30448: using the new Spandsp FAX Driver 16.30.0
Reporter:ben kolodny (benphone)Labels:fax
Date Opened:2023-03-02 04:50:47.000-0600Date Closed:2023-03-02 09:05:37.000-0600
Priority:CriticalRegression?Yes
Status:Closed/CompleteComponents:Applications/app_fax
Versions:16.30.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:cento 6Attachments:
Description:{noformat}
/usr/sbin//safe_asterisk: line 171: 27495 Segmentation fault      (core dumped) nice -n $PRIORITY "${ASTSBINDIR}/asterisk" -f ${CLIARGS} ${ASTARGS} > /dev/${TTY} 2>&1 < /dev/${TTY
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2023-03-02 04:50:53.115-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. 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: Joshua C. Colp (jcolp) 2023-03-02 04:52:24.850-0600

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

Asterisk 16 no longer receives bug fixes. If this can be reproduced using Asterisk 18 then follow the instructions to get a backtrace and attach it, to see if the issue is within spandsp itself or within Asterisk instead. If it is within spandsp that is not code we maintain or patch.
By: ben kolodny (benphone) 2023-03-02 05:02:17.946-0600

in 18 everything's just fine working in 3 different systems
just 16 (err a old cento can't compile 18 ) having this problem
should i investigate?
By: Joshua C. Colp (jcolp) 2023-03-02 05:07:13.240-0600

You are free to investigate and resolve it on your own, but as I stated 16 no longer receives bug fixes. No changes will go into it.
By: Asterisk Team (asteriskteam) 2023-03-02 09:01:32.054-0600

This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.