[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

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-29220:
------------------------------------------------

Change 15349 merged by Joshua Colp:
res/res_pjsip_session.c: Check that media type matches in function ast_sip_session_media_state_add.

[https://gerrit.asterisk.org/c/asterisk/+/15349|https://gerrit.asterisk.org/c/asterisk/+/15349]

> 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)