Hi Andreas, IMHO, UAC should not mirror "Record-Route" in 200 OK response to NOTIFY request. Here is the reference from RFC 6665 -
4.3. Proxy Behavior Proxies need no additional behavior beyond that described in [RFC3261] to support SUBSCRIBE and NOTIFY transactions. If a proxy wishes to see all of the SUBSCRIBE and NOTIFY requests for a given dialog, it MUST add a "Record-Route" header field to the initial SUBSCRIBE request and all NOTIFY requests. It MAY choose to include "Record-Route" in subsequent SUBSCRIBE requests; however, these requests cannot cause the dialog's route set to be modified. Proxies that did not add a "Record-Route" header field to the initial SUBSCRIBE request MUST NOT add a "Record-Route" header field to any of the associated NOTIFY requests. So once the dialog is created when UAC receives 200 OK response to SUBSCRIBE, UAC builds the route set. This route set do not changed by subsequent in-dialog NOTIFY requests as per RFC 3261 - 12.2 Requests within a Dialog Requests within a dialog MAY contain Record-Route and Contact header fields. However, these requests do not cause the dialog's route set to be modified, although they may modify the remote target URI. -- Best Regards, Atul Thosar On 20 February 2013 18:48, Andreas Byström (Polystar) < [email protected]> wrote: > 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 > [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
