> Hi All, > I think the same CSeq no. is contradictory. Even in the > UAS behaviour, the handling for the same CSeq is not defined. > In section 12.2.2 under UAS behaviour it is described as > > RFC 3261: Section12.2.2 UAS Behaviour: > If the remote sequence number was not empty, but the > sequence number > of the request is lower than the remote sequence number, > the request > is out of order and MUST be rejected with a 500 (Server Internal > Error) response. If the remote sequence number was not empty, and > the sequence number of the request is greater than the remote > sequence number, the request is in order. > > If it would be valid, then RFC would have clearly mention > that the request with same sequence number MUST/SHOULD be accepted.
Section 12.2.2 is part of section 12.2 - Requests within a Dialog. I have already shown that the REGISTER and SUBSCRIBE are not in the same dialog, and hence this prohibition is irrelevant. Regards, Michael Procter _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
