[asterisk-bugs] [JIRA] (ASTERISK-20149) Crash when faxing SIP to SIP with strictrtp set to yes
Michal Rybarik (JIRA)
noreply at issues.asterisk.org
Fri Jan 31 22:29:03 CST 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-20149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214734#comment-214734 ]
Michal Rybarik commented on ASTERISK-20149:
-------------------------------------------
Function fsk_rx() in libspandsp is segfaulting probably because it can process only slinear frames, but currently also alaw/ulaw frames are passed to it. Alaw/ulaw frame is usually 160 bytes long, but fsk_rx() is trying to read 320bytes, so segfault may happen.
I'm attaching patch for Asterisk 11 module res_fax_spandsp, it should resolve this issue. Now alaw/ulaw frames are transcoded to slinear before they are passed to libspandsp, and other frame formats are ignored. (Other frames will probably never reach this place, but I rather check it).
If you still have problem after applying this patch, set debug level to 5, make call, and attach asterisk log then...
> Crash when faxing SIP to SIP with strictrtp set to yes
> ------------------------------------------------------
>
> Key: ASTERISK-20149
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20149
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_fax, Resources/res_fax_spandsp
> Affects Versions: 10.6.0, 11.5.0
> Reporter: Alexandr Gordeev
> Assignee: Alexandr Gordeev
> Severity: Critical
> Attachments: backtrace.1346914431.1467.11, backtrace_20120719.txt, backtrace_20120720.txt, backtrace_20121205.txt, backtrace_20130814_2.txt, backtrace_20130814.txt, full_20120719.txt, full_20120720.txt, t38_gw_crash_dec_20.backtrace, t38_gw_crash_dec_20.pcap.gz, traffic_20120719.dump, traffic_20120720.dump
>
>
> Crash Asterisk (2) when faxing.
> Schema :
> Other PBX - > pri - > Asterisk 10.6.0 (1) - > sip,g729,t38 - > Asterisk 10.6.0 (2) - > sip,g711,t30- > Other PBX
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list