[asterisk-bugs] [JIRA] (ASTERISK-30184) res_pjsip_session: re-INVITE after answering results in wrong stream direction of first call leg

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-30184:
------------------------------------------------

Change 19059 merged by Friendly Automation:
core & res_pjsip: Improve topology change handling.

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

> res_pjsip_session: re-INVITE after answering results in wrong stream direction of first call leg
> ------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30184
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30184
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip, Resources/res_pjsip, Resources/res_pjsip_session
>    Affects Versions: 18.13.0
>            Reporter: Maximilian Fridrich
>         Attachments: ASTERISK-30184-fixed-with-delay.pcapng, ASTERISK-30184.pcapng, debug_log_30184.txt
>
>
> Using the Dial application, when the outgoing call leg receives a 200 from the callee answering the call, and then immediately after receives a re-INVITE from the callee updating a media stream direction, Asterisk does not correctly update the media stream of the first call leg (to the caller). Asterisk does send multiple re-INVITES to the first call leg but the last one does not contain the correct stream directions from the re-INVITE.
> When sending the re-INVITE with some delay (e.g. 500ms), Asterisk correctly updates the stream direction of the first call leg (see attached traces).



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