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

[Michael Maier (JIRA)]

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

Michael Maier updated ASTERISK-28452:
-------------------------------------

    Attachment: sdp-version-v2.patch

The previously attached quick fix doesn't fix the problem completely, because there is not just the increment broken, but the SDP session handling completely (the SDP session used for the ReInvite is the SDP of the initial INVITE instead of the INVITE + AUTH). See https://www.mail-archive.com/asterisk-dev@lists.digium.com/msg44766.html

The sdp-version-v2.patch takes this into consideration and better tries to ensure, that SDP session is always incremented and never decremented by adding timestamp and cseq number.

> 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
>            Severity: Minor
>              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)