[asterisk-bugs] [JIRA] (ASTERISK-27936) res_pjsip_session doesn't update media when a 200 comes in with a different port than a 183

[George Joseph (JIRA)]

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

George Joseph updated ASTERISK-27936:
-------------------------------------

    Status: Open  (was: Triage)

> res_pjsip_session doesn't update media when a 200 comes in with a different port than a 183
> -------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27936
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27936
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_session
>    Affects Versions: 13.21.0, 15.4.0
>            Reporter: George Joseph
>            Severity: Minor
>              Labels: pjsip
>
> Some UASs provide custom ringback or other early media on a dedicated port.  They send a 183 progress message with an SDP answer that has the early media port as the audio port.  When the call is connected, they then send back a 200 OK also with an SDP that now has the final media port as the audio port.
> res_pjsip_session doesn't get notified of the updated media because pjproject o nly notifies Asterisk if the To tag is different on the 200 than on the 183 (forked INVITE).



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