Re: [Sip-implementors] Query on SIP REGISTER refresh dialog
On 3/10/17 2:49 PM, Dale R. Worley wrote: Puneet Kumar writes: 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? If not then please point out RFC section which blocks a UA from doing it. In general does REGISTER refresh & REGISTER for deregistration MUST be in same dialog as earlier REGISTER? To echo Brett, the sequence of REGISTERs sent by a UAC don't form a dialog. (You might consider each individual REGISTER a seperate dialog containing only one request.) But since they have the same Call-Id and increasing CSeq's, they form a series that in some ways resembles a dialog, that can be called a quasi-dialog or pseudo-dialog. To understand what a UAC should do and the exact effect of a set of REGISTERs, you have to study exactly how RFC 3261 section 10 specifies that REGISTERs are processed by the registrar. And if the "SIP Outbound" extension is being used, RFC 5626. Also, note that the "dialog" nature of registers becomes important for the lifetime of temporary GRUUs. (RFC5627) Thanks, Paul ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] Query on SIP REGISTER refresh dialog
Puneet Kumar writes: > 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? > If not then please point out RFC section which blocks a UA from doing it. > > In general does REGISTER refresh & REGISTER for deregistration MUST be > in same dialog as earlier REGISTER? To echo Brett, the sequence of REGISTERs sent by a UAC don't form a dialog. (You might consider each individual REGISTER a seperate dialog containing only one request.) But since they have the same Call-Id and increasing CSeq's, they form a series that in some ways resembles a dialog, that can be called a quasi-dialog or pseudo-dialog. To understand what a UAC should do and the exact effect of a set of REGISTERs, you have to study exactly how RFC 3261 section 10 specifies that REGISTERs are processed by the registrar. And if the "SIP Outbound" extension is being used, RFC 5626. Dale ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] Query on SIP REGISTER refresh dialog
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
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
