>From 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.
So my guess is that if it's the same request (same Contact header, Call-ID,
expiration etc), it can be the same CSeq. In any case you should follow the
10.3 to figure out what you should do with the Register request.
/Filippos
On Mon, Jun 27, 2022 at 5:04 PM Gilson Urbano Ferreira Dias <
[email protected]> wrote:
> Can I have the same CSeq numbering originating from the same server in
> Register messages?
>
> Note that the previous messages were being incremented by one as CSeq =
> ..., 932840, 932841.
>
> Suddenly, the server decided to send CSeq = 1 in three consecutive Register
> messages for different Call-Ids.
>
> I tried reading https://www.rfc-editor.org/rfc/rfc3261#section-12.2.1.1
> and
> https://www.rfc-editor.org/rfc/rfc3261#section-8.1.1.5, but I'm still not
> sure if this is the expected behavior.
>
> Could someone please clarify?
>
> A--------------Request: INVITE (Call-ID = A) (Cseq =
> 932841)------------>B
> <--------------Status: 100 Trying (Call-ID = A) (Cseq =
> 932841)------------
> <--------------Status: 200 OK (Call-ID = A) (Cseq =
> 932841)------------
> ---------------Request: ACK (Call-ID = A) (Cseq =
> 932841)------------>
>
> <--------------Request: Register (Call-ID = B) (Cseq =
> 1)-----------------
> <--------------Request: Register (Call-ID = C) (Cseq =
> 1)-----------------
> ---------------Status: 200 OK (Call-ID = B) (Cseq =
> 1)----------------->
> <--------------Request: Register (Call-ID = D) (Cseq =
> 1)-----------------
> ---------------Status: 200 OK (Call-ID = C) (Cseq =
> 1)----------------->
> ---------------Status: 403 Forbidden(Call-ID = D) (Cseq =
> 1)----------------->
>
> Regards,
>
> Gilson Urbano
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
