I just noticed this thread. So I'm jumping in where it seems to make sense.
Note that 3261 and friends are *not* very clear about this. RFC6337
tried to clarify the original intent, without being normative. (In
retrospect it would probably have been better to make a normative
update.) There we
> I agree with you but does not.
>
> Basically what they are saying is this: If SDP version number
> is incremented then this counts as an update/new offer period.
They can call it whatever they want. RFC 3261 says that the SDP must be
ignored (i.e. it is not an updated answer or new offer).
Ho
I agree with you but Nokia does not.
Basically what they are saying is this: If SDP version number is
incremented then this counts as an update/new offer period.
The problem is I can't find an RFC stating "You MUST NOT increment
version number if no change is made to the SDP"
Even Paul Kyzviat i
> The violation is:
>
> "When a reliable provisional response contains a session description, and
> is
> the first to do so, then that session description is the answer to the
> offer
> in the INVITE request. The answer cannot be updated, and a new offer
> cannot
> be sent in a subsequent reliabl
hus it shouldn't cause the call to be released. With that
>>> > said, some devices have configuration options to violate that
>>> > statement and treat as an updated answer SDP (or a new offer SDP).
>>> >
>>> > RFC 3261 section 13.2.1: "Th
> Sent: Thursday, September 17, 2015 3:29 PM
>> To: Brett Tate
>> Cc: sip-implementors@lists.cs.columbia.edu
>> Subject: Re: [Sip-implementors] SDP version increment without SDP change
>> in
>> early dialog
>>
>> Hi
>>
>> Correct I forgot to
2.1: "The UAC MUST treat the first session
> > description it receives as the answer, and MUST ignore any session
> > descriptions in subsequent responses to the initial INVITE."
> >
> > More inline.
> >
> >> -----Original Message-----
> >>
t; implementors-boun...@lists.cs.columbia.edu] On Behalf Of Roger Wiklund
>> Sent: Thursday, September 17, 2015 1:47 PM
>> To: sip-implementors@lists.cs.columbia.edu
>> Subject: [Sip-implementors] SDP version increment without SDP change in
> early
>> dialog
>>
>
u
> Subject: [Sip-implementors] SDP version increment without SDP change in
early
> dialog
>
> Hi list
>
> I'm seeing the following behavior from an Aastra 400 PBX.
>
> Flow below is ITSP to PBX
>
> INVITE>
> <100Trying
> <183 w/SDP
> PRACK>
>
Hi list
I'm seeing the following behavior from an Aastra 400 PBX.
Flow below is ITSP to PBX
INVITE>
<100Trying
<183 w/SDP
PRACK>
<200OK (PRACK)
<180 w/SDP
>PRACK
<200OK (PRACK)
<200OK (INVITE)w/SDP
ACK>
BYE>
<200OK (BYE)
Each time the PBX sends an SDP, the version number is incremented even
tho
10 matches
Mail list logo
