[asterisk-bugs] [JIRA] (ASTERISK-28982) res_pjsip_t38: Does not resume as audio when negotiation fails

[Joshua C. Colp (JIRA)]

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

Joshua C. Colp updated ASTERISK-28982:
--------------------------------------

    Assignee: Christian Berger
      Status: Waiting for Feedback  (was: Triage)

Can you elaborate why you think this should be treated as a separate issue despite ASTERISK-28441 existing? It's the same failure result. Are you just concerned that if the other one is fixed it may not cover this specific case?

> res_pjsip_t38: Does not resume as audio when negotiation fails
> --------------------------------------------------------------
>
>                 Key: ASTERISK-28982
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28982
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_fax, Resources/res_pjsip_t38
>    Affects Versions: 13.32.0, 16.11.1
>            Reporter: Christian Berger
>            Assignee: Christian Berger
>            Severity: Minor
>
> We operate Asterisk as a B2Bua in our network. It's task is to transcode, write CDRs and act as a T38 gateway. We are currently trying to move over to PJSIP from the legacy SIP stack.
> We have noticed the following potential bug: When T38 is negotiated on a call leg, voice traffic to it will stop. However even if T38 is rejected it will not send anything via RTP.
> This issue sounds like ASTERISK-28441, however the patch there does not appear to change the problem. In fact the changed function does not seem to be called at all.
> We have, however, found one potential bug in t38_fallback_response_cb. Provisional Response codes 1xx are handled as failures. However this doesn't seem to solve the problem.



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