My interpretation would be that this is not wrong. According to RFC
3261 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.
The implication is that the addition of the Record-Route header to a
final positive reply is necessary only in replies that serve to
establish a dialog, not replies to subsequent requests that take place
within a dialog or are used to terminate a dialog.
Furthermore, 12.2 ("Requests Within a Dialog") says:
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.
-- Alex
On 12/31/2009 04:09 AM, [email protected] wrote:
> Hi All,
>
> I have a small query related to record-route header in BYE and response
> to it.
>
> Record-route is used so that all the future requests in a dialog pass
> through a certain set of proxy servers.
> In case of BYE, which would be terminating a dialog, if record-route
> header is added to it, should the 2xx response to BYE also contain
> record-route header?
> Is it wrong, if a server doesn't add record-route header while building
> 2xx response for BYE request?
>
> Thanks,
> Sunil
>
>
> Please do not print this email unless it is absolutely necessary.
>
> The information contained in this electronic message and any attachments to
> this message are intended for the exclusive use of the addressee(s) and may
> contain proprietary, confidential or privileged information. If you are not
> the intended recipient, you should not disseminate, distribute or copy this
> e-mail. Please notify the sender immediately and destroy all copies of this
> message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient should
> check this email and any attachments for the presence of viruses. The company
> accepts no liability for any damage caused by any virus transmitted by this
> email.
>
> www.wipro.com
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
--
Alex Balashov - Principal
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
