[asterisk-bugs] [JIRA] (ASTERISK-21242) Segfault when T.38 re-invite retransmission receives 200 OK

[Ashley Winters (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-21242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashley Winters updated ASTERISK-21242:
--------------------------------------

    Attachment: t38-retransmission-segfault-debug.log

Near the top of the log, "timed-out during the T.38 negotiation". On a later re-INVITE retry, you see a 200 OK followed by "switched to T.38 FAX session '1115'". Segfault followed immediately afterwards.
                
> Segfault when T.38 re-invite retransmission receives 200 OK
> -----------------------------------------------------------
>
>                 Key: ASTERISK-21242
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21242
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_fax, Resources/res_fax_spandsp
>    Affects Versions: 11.2.1
>         Environment: CentOS 6.2 x86_64
>            Reporter: Ashley Winters
>            Severity: Critical
>         Attachments: gdb-t38-retransmission-segfault.txt, t38-retransmission-segfault-debug.log
>
>
> If res_fax falls back to audio after timing out on T.38 upgrade, and chan_sip continues retrying the re-INVITE, and the remote end responds to one of the retransmissions (after res_fax times out) with a 200 OK, a T.38 frame will be delivered to the res_fax_spandsp driver without the t38 subsystem being initialized.
> This results in a segfault.

--
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