[asterisk-bugs] [JIRA] (ASTERISK-27944) res_pjsip_t38: Crash receiving 1xx responses other than 100 before 200 for T.38 reINVITE

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Fri Aug 10 20:00:55 CDT 2018


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

Richard Mudgett updated ASTERISK-27944:
---------------------------------------

    Attachment: jira_asterisk_27944_v2_w_debug_v15.patch

I still don't understand how we could have another final response processed for the T.38 reINVITE.  Maybe the INVITE transaction is timing out at the same time as the 200 OK is coming in?  I've looked at the code but I don't think that situation could cause the crash.

[^jira_asterisk_27944_v2_w_debug_v15.patch] - This patch adds protection from receiving more than one final response to the T.38 reINVITE.  We will ignore any unexpected response.  It also has a NOTICE log level BUGBUG message to make it easy to grep the logs to see if we likely avoided a crash.


> res_pjsip_t38: Crash receiving 1xx responses other than 100 before 200 for T.38 reINVITE
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27944
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27944
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_t38
>    Affects Versions: 15.2.2, 15.4.1
>            Reporter: Joshua Elson
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: fax, patch, pjsip
>         Attachments: core.com-2018-08-01T15-46-31-0600-brief.txt, core.com-2018-08-01T15-46-31-0600-full.txt, core.com-2018-08-01T15-46-31-0600-locks.txt, core.com-2018-08-01T15-46-31-0600-thread1.txt, core.iad.2018-08-10T12-34-02-0600-brief.txt, core.iad.2018-08-10T12-34-02-0600-full.txt, core.iad.2018-08-10T12-34-02-0600-locks.txt, core.iad.2018-08-10T12-34-02-0600-thread1.txt, core.iad.com-2018-06-25T14-06-14-0600-brief.txt, core.iad.com.2018-06-25T14-06-14-0600-full.txt, core.iad.com.2018-06-25T14-06-14-0600-locks.txt, core.iad.com.2018-06-25T14-06-14-0600-thread1.txt, core.iad.com-2018-07-09T09-14-58-0600-brief.txt, core.iad.com-2018-07-09T09-14-58-0600-full.txt, core.iad.com-2018-07-09T09-14-58-0600-locks.txt, core.iad.com-2018-07-09T09-14-58-0600-thread1.txt, crash_dialplan.txt, jira_asterisk_27944_v2_w_debug_v15.patch
>
>
> Crash of Asterisk on T38 session rejection via PJSIP.
> This is happening somewhat routinely on a number of our nodes. The error message in the logs will appear as:
> [2018-06-25 14:06:04] WARNING[3368][C-00005bd3] res_fax.c: channel 'PJSIP/FC-DFW-PROXY-0000f050' refused to negotiate T.38
> There will be a crash with the attached backtrace.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list