[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    [Sip-implementors] Mirroring record-route in 200 OK for NOTIFY?
From:       Andreas_Byström_(Polystar) <andreas.bystrom () polystar ! com>
Date:       2013-02-20 13:18:22
Message-ID: 7E8670B53A8E6945BBB8B7589ED2C41C01C3E090671E () idun ! polystar ! se
[Download RAW message or body]

Hi

If a UA subscribes to register events it will first send out an SUBSCRIBE request, \
receive a 200 OK for that request and eventually receive a NOTIFY. If that NOTIFY \
requests includes a Record-Route header, should that header be mirrored into the 200 \
OK for NOTIFY that the UE creates?

RFC3261 says that
12.1.1 UAS behavior

   When a UAS responds to a request with a response that establishes a
   dialog (such as a 2xx to INVITE), the UAS MUST copy all Record-Route
   header field values from the request into the response (including the
   URIs, URI parameters, and any Record-Route header field parameters,
   whether they are known or unknown to the UAS) and MUST maintain the
   order of those values.

But 200 OK for NOTIFY cant be considered as a response that creates a dialog?

Checked RFC6665 and didn't manage to find some hints on how to create the 200 OK. \
Could someone please point out where I can find the rules for creating on this 200 OK \
response and if the Record-Route should be mirrored or not

Regards,
// Andreas


_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


[prev in list] [next in list] [prev in thread] [next in thread]