423 Interval Too Brief retry CSeq issue

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Send a REGISTER with an Expires value smaller than the server will allow
2.
3.

What is the expected output? What do you see instead?
The server sends a 423 Interval Too Brief, with a Min-Expires header. The 
REGISTER that the client then sends has the same CSeq as the first attempt. I 
think it should have a CSeq that is one higher.

What version of the product are you using? On what operating system?
Client version 2.3.6

Please provide any additional information below.

Original issue reported on code.google.com by iiaGa...@gmail.com on 7 Feb 2012 at 1:12

[GoogleCodeExporter]

Can you check in RFC and give me a feedback before any correction.

Original comment by jmauffret@gmail.com on 10 Feb 2012 at 6:05

• Changed state: Started

[GoogleCodeExporter]

Here's is what I see in RFC 3261:
Section 8.1.3.5 Processing 4xx Responses: While 423 isn't listed, the section 
does indicate that for the listed responses (401,413,415,416,420) the request 
is retried with the appropriate modifications using the same Call-ID, To, and 
From, and with a CSeq that is one higher. With other status responses a retry 
may or may not be possible.

Section 10.2: 
     CSeq: The CSeq value guarantees proper ordering of REGISTER
           requests.  A UA MUST increment the CSeq value by one for each
           REGISTER request with the same Call-ID.

Original comment by iiaGa...@gmail.com on 10 Feb 2012 at 4:57

[GoogleCodeExporter]

Fixed in next release

Original comment by jmauffret@gmail.com on 21 Feb 2012 at 3:11

• Changed state: Fixed