Hi, Sorry about the resend; however I wanted to mention that you also might want to look at RFC 5626 (and RFC 5627) since it updates RFC 3261.
> -----Original Message----- > From: Brett Tate [mailto:br...@broadsoft.com] > Sent: Friday, March 10, 2017 6:35 AM > To: 'Puneet Kumar'; 'sip-implementors@lists.cs.columbia.edu' > Subject: RE: [Sip-implementors] Query on SIP REGISTER refresh dialog > > > If a UA uses different dialog-ID (say new Call-ID & No To header tag) > > for REGISTER refresh with same contact address then it is allowed? > > Yes; however you should read RFC 3261 section 10. For instance, section > 10.2.4 indicates "UA SHOULD use the same Call-ID for all registrations during a > single boot cycle" and section 10.2 indicates that using the same Call-ID helps > detect a delayed REGISTER. > > > In general does REGISTER refresh & REGISTER for deregistration MUST be > > in same dialog as earlier REGISTER? > > No. As RFC 3261 section 10.2 indicates "REGISTER request does not establish > a dialog". REGISTER creates what some call a pseudo dialog since Call-ID > should be reused but the refresh/deregister does not contain a To tag. _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
