[SIPForum-discussion] [Sip-implementors] To-Tag in REGISTER message

Vivek Talwar vivek.talwar at globallogic.com
Tue Oct 30 11:37:30 UTC 2012

Hi Keerthi,

      In case of refresh REGISTER or De-REGISTER the CSeq will not be same.
If CSeq is same then yes its a case of loop detection.

Vivek Talwar

On Tue, Oct 30, 2012 at 4:47 PM, Keerthi Srinivasan <
keerthivarmansrinivasan at gmail.com> wrote:

> All,
> When UA sends REGISTER request to the server it does not contain the To-Tag
> and Server is accepts the Registration (200 OK) will have the To-Tag.
> If the Refresh or Deregister does not have the To-Tag in the REGISTER
> message. Is the server will accept the Refresh or Deregister REGISTER
> message or will send 482 Loop Detected as per the RFC3261 ( Merged
> Requests)
> Here is the RFC3261 content:
> Merged Requests
>    If the request has no tag in the To header field, the UAS core MUST
>    check the request against ongoing transactions.  If the From tag,
>    Call-ID, and CSeq exactly match those associated with an ongoing
>    transaction, but the request does not match that transaction (based
>    on the matching rules in Section 17.2.3), the UAS core SHOULD
>    generate a 482 (Loop Detected) response and pass it to the server
>    transaction.
>       The same request has arrived at the UAS more than once, following
>       different paths, most likely due to forking.  The UAS processes
>       the first such request received and responds with a 482 (Loop
>       Detected) to the rest of them.
> Is the Server MUST reject or Accept the Refresh / Deregister REGISTER
> request?
> --
> Regards,
> Keerthi
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors at lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


Vivek Talwar
GlobalLogic Inc. | Innovation by Design
Office: +91-120-434-2000 x 3217 | Mobile: +919015330797

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20121030/a2498791/attachment-0002.html>

More information about the discussion mailing list