[asterisk-bugs] [JIRA] (ASTERISK-27944) Crash on T38 Rejection

[Joshua Elson (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243944#comment-243944 ] 

Joshua Elson commented on ASTERISK-27944:
-----------------------------------------

This was on 15.2.2, although we've seen it on all 15.x versions.

Let me see if I can get a way to pull the SIP trace and the console log. This doesn't happen on all T38 negotiation rejections, but a subset of them.

Looking for a fully reproducible way to create this state and haven't quite found it yet, but it does occur with regularity on our cluster nodes, even under light to moderate load.

> Crash on T38 Rejection 
> -----------------------
>
>                 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: Joshua Elson
>              Labels: fax, pjsip
>         Attachments: 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
>
>
> 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)