[asterisk-bugs] [JIRA] (ASTERISK-29220) After T38 reinvite response of 488 a subsequent G711 reinvite is not processed correctly. Instead the previous T38 session media is used

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-29220:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> After T38 reinvite response of 488 a subsequent G711 reinvite is not processed correctly. Instead the previous T38 session media is used
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-29220
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29220
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_session
>    Affects Versions: 16.7.0
>         Environment: Debian 8 & 9
>            Reporter: Robert Cripps
>            Assignee: Robert Cripps
>              Labels: fax
>
> A fax call is established negotiated to G711 pcmu. If A or B leg receives a T38 reinvite that is propagated correctly to the other leg. If the other leg responds with 488 that is again correctly propagated back to the T38 reinvite sender. However, if the T38 reinvite sender then sends a G711 reinvite, asterisk sends another T38 reinvite to the other leg.
> The Asterisk 13 behavior was to 200 OK the subsequent G711 reinvite back to the sender. 
> A patch for res_pjsip_session.c fixes this problem. It will follow in due course when I get my head around the process



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