On 6/28/22 4:19 AM, Gilson Urbano Ferreira Dias wrote:
Dale,
The three pseudo-dialogs are for different AORs.
It would be very helpful if you would post the full messages.
Thanks,
Paul
Does this change anything in the analysis?
Regards,
Gilson Urbano
Filippos,
They are 3 different (Call-ID, tag, Contact, From, and To) Register
requests using the same CSeq, and from the same server.
I think the server is not following 10.2 because the second Register
message containing a different Contact header is sent before the final
response of the first
Dale,
The three pseudo-dialogs are for different AORs.
Does this change anything in the analysis?
Regards,
Gilson Urbano
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
Gilson Urbano Ferreira Dias writes:
> 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
>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),
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
