[asterisk-bugs] [JIRA] (ASTERISK-28452) pjsip: <sess-version> of SDP is not incremented though SDP may be changed on reinvite without SDP offer

[Stanislav Abramenkov (JIRA)]

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

Stanislav Abramenkov commented on ASTERISK-28452:
-------------------------------------------------

This answer was written by sauwming
https://github.com/pjsip/pjproject/issues/2620

In the issue page, I believe Ivan has explained it well. Since app/user modifies the local SDP, I think it should be okay to also increase the version. Or is there any reason not to?

Note that I tested the scenario here with pjsua app and without the SDP modification, everything seems to work correctly.
Attached is the sipp scenario I used for testing:
uac-reinv-no-sdp.xml.txt

> pjsip: <sess-version> of SDP is not incremented though SDP may be changed on reinvite without SDP offer
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28452
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28452
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip, Resources/res_pjsip_sdp_rtp
>    Affects Versions: 16.3.0
>         Environment: CentOS 7
>            Reporter: Michael Maier
>              Labels: patch, pjsip
>         Attachments: sdp-version.patch, sdp-version-v2.patch, wrong-SDP-sess-version.txt
>
>
> During late / delayed offer as part of a reInivte during an outbound call, the SDP sent to the provider in the 200 OK is changed compared to the initial INVITE - but the <sess-version> isn't incremented. This is against RFC6337, 5.2.5. Subsequent Offers and Answers.
> See the attached Trace!



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