Thank you, really helpful, but I need help on what I should look for in
RFC3265, I can't find that there is any mention of SDP's in it ?
BR/pj
Sensitivity: Internal
-Original Message-
From: sip-implementors-boun...@lists.cs.columbia.edu
On Behalf Of Paul Kyzivat
Sent: den 24
Thank you !
From: Kashif Husain
Sent: den 24 september 2019 00:04
To: Sundbaum Per-Johan (Telenor Sverige AB)
Cc: sip-implementors@lists.cs.columbia.edu
Subject: Re: [Sip-implementors] session refresh
And we can also respond with 200OK as mentioned in rfc3261 with no change in
our sdp.
"If
On 9/23/19 5:00 PM, Sundbaum Per-Johan (Telenor Sverige AB) wrote:
Hi !
Can anybody help me find relevant RFC/other info on how UAS should handle
re-INVITE that is intended as a session refresh and not for modifying the
session ?
A pure session refresh is something that can only be
And we can also respond with 200OK as mentioned in rfc3261 with no change
in our sdp.
"If the user is already a member of the session, and the session
parameters contained in the session description have not changed, the
UAS MAY silently accept the INVITE (that is, send a 2xx response
You can check for SDP version of re-Invite, if its same as previous one
then its usually intended for session refresh.
Thanks,
-kashif
On Tue, 24 Sep 2019, 02:30 Sundbaum Per-Johan (Telenor Sverige AB), <
per-johan.sundb...@telenor.se> wrote:
> Hi !
> Can anybody help me find relevant RFC/other
RFC 4028 describes Session Timers in SIP.
RFC 3264, 4317, 4566, 6337 describe SDP as well as SDP offer/answer model.
RFC 6141 describes Re-INVITE and Target-Refresh Request Handling in the
Session Initiation Protocol (SIP).
Hope this helps
___
Hi !
Can anybody help me find relevant RFC/other info on how UAS should handle
re-INVITE that is intended as a session refresh and not for modifying the
session ?
SDP B1 in (3) is identical with SDP B1 in (5)
CallerCallee
|
