Ravi, see inline
----- Original Message ----- From: "Ravi S" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, March 17, 2006 12:10 PM Subject: [Sip-implementors] SIP Registration > The section "10.3 Processing REGISTER Requests" of rfc3261 specifies > the following rules for updating the bindings > > "If the Call-ID value in the existing binding differs from the Call-ID > value in the request, the binding MUST be removed if the expiration > time is zero and updated otherwise. If they are the same, the > registrar compares the CSeq value. If the value is higher than that of > the existing binding, it MUST update or remove the binding as above. > If not, the update MUST be aborted and the request fails." > > What i can understand from this is, for each contact the registrar > maintains the call-id and cseq. For each re-registration it compares > the call-id with the stored call-id. If it matches the cseq should be > greater than the cseq stored. > > But in REGISTER call flows of rfc 3665 the updation of contacts > (section 2.2. Update of Contact List) shows the same Call-ID but with > CSeq lesser than that of the initial REGISTER request. Is this call > flow correct or am I missing something? > I think section 2.2 should be seen separate from 2.1, but then still CSeq=1 would not happen in reality since according to the storyboard there has been an initial registration before, and 2.2 is an update of that. So it should have been > 1 (or even > 2 in case of authentication) So it's a flaw in the example Regards, jeroen > --Ravi > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
