| Summary: | ASTERISK-27951: Segfault in res_pjsip_t38.so on incoming fax | ||||
| Reporter: | Robert Bailey (rbailey1) | Labels: | fax | ||
| Date Opened: | 2018-07-02 19:28:12 | Date Closed: | 2018-07-02 19:51:49 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/chan_sip/T.38 | ||
| Versions: | 15.1.3 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | CentOS Linux release 7.4.1708 Asterisk 15.1.3 (from source) T38Modem 3.15.3 (from source) Hylafax 5.5.9 (from source) | Attachments: | ( 0) coredump_backtrace.tgz | ||
| Description: | Regularly through the day, it appears that inbound faxes are causing Asterisk to segfault with errors like the following:
[29817.163018] asterisk[95893]: segfault at 8 ip 00007f25bf390bac sp 00007f25b3777850 error 4 in res_pjsip_t38.so[7f25bf38d000+7000] System was previously stable, and nothing was changed prior to this issue beginning. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2018-07-02 19:28:13.660-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: Robert Bailey (rbailey1) 2018-07-02 19:30:38.090-0500 Core dump backtrace | ||||