On 04/28/2011 10:42 AM, [email protected] wrote:
> Hi
> How UAS should react having received OPTIONS, out of the dialog, with "To"
> field containing tag? Is "8.2.6.2 Headers and Tags" from RFC3261 proper
> requirement for this isue?
> In my case UAS respond with 481Unknown Dialog.
> Regards
> Bartek
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
Hello,
I would consider 481 a compliant answer(and I tried working on a draft
that standardizes this), but from RFC 5057 Section 5.3, that references
RFC 3261
According to [1], "an OPTIONS request received within a dialog
generates a 200 OK response that is identical to one constructed
outside a dialog and does not have any impact on that dialog". Thus,
OPTIONS does not belong to any usage. Only those failures discussed
in Section 5.1 and Section 5.2 that destroy entire dialogs will have
any effect on the usages sharing the dialog with a failed OPTIONS
request.
Various threads seem to suggest that a 200 OK(or whatever answer is
appropriate if the OPTIONS is outside of an known dialog) might also be
a good answer.
Marius
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
