[asterisk-bugs] [JIRA] (ASTERISK-27657) res_pjsip_t38: ATA fails with hangupcause 58(Bearer capability not available)

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Fri Mar 23 17:41:39 CDT 2018


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

Richard Mudgett edited comment on ASTERISK-27657 at 3/23/18 5:41 PM:
---------------------------------------------------------------------

I've traced this all the way back to the 15.0.0-beta1, so the problem lies somewhere in the jump from 14.6 and 15 as far as I can tell.
I applied this patch to releases < 15.2 to avoid crashing during testing ASTERISK-27364


was (Author: fortytwo):
I've traced this all the way back to the 15.0.0-beta1, so the problem lies somewhere in the jump from 14.6 and 15 as far as I can tell.
I applied this patch to releases < 15.2 to avoid crashing during testing https://issues.asterisk.org/jira/browse/ASTERISK-27364

> res_pjsip_t38: ATA fails with hangupcause 58(Bearer capability not available)
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-27657
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27657
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_fax, Resources/res_pjsip_t38
>    Affects Versions: 15.0.0-beta1, 15.2.0, 15.3.0
>            Reporter: Jared Hull
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: fax, pjsip
>         Attachments: pjsip.conf.txt, res_fax.conf.txt, t38_asterisk14-6.pcap, t38_log.txt, t38.pcap
>
>
> Sending a T.38 fax from an ATA is failing with hangup cause 58(Bearer capability not available) on Asterisk 15.2, but the same device and dialplan on Asterisk 14.6 works.
> There are several strange things in the log:
> # {{pjsip set logger on}} reports some duplicate T.38 re-INVITEs being recieved from the ATA, but a packet capture on the Asterisk server and a pcap on the SBC server relaying to the Asterisk server show that only one INVITE is there. It also looks like Asterisk is processing both
> # Sometimes Asterisk sends {{491 Another INVITE transaction in progress}} in response to the T.38 re-INVITE from the ATA.
> # 109 is the ATA requesting T.38, I don't know what this means.
> {noformat}[Feb  5 17:39:01] DEBUG[7126][C-0000001d]: res_fax.c:3275 fax_gateway_detect_t38: T.38 disabled on channel PJSIP/109-00000060{noformat}
> # Asterisk 15.2 sends an INVITE back to the ATA after receiving the ACK, but Asterisk 14.6 does not (because it has begun the fax transmission by this point).
> {noformat}[Feb  5 17:39:01] DEBUG[10811]: res_pjsip_session.c:1664 ast_sip_session_refresh: Sending session refresh SDP via re-INVITE to 109{noformat}



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



More information about the asterisk-bugs mailing list