[asterisk-bugs] [JIRA] (ASTERISK-27944) Crash on T38 Rejection
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Mon Jun 25 15:59:54 CDT 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243941#comment-243941 ]
Asterisk Team commented on ASTERISK-27944:
------------------------------------------
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].
> 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
> Labels: fax, pjsip
>
> 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