Your example can't be legal because it isn't a syntactically correct
URI. The header parameters are defined as part of the syntax of a sip
URI, but not for TEL.
Paul
Fortinsky Michael wrote:
> The History-Info header can have entries that contain Reason or Privacy
> headers as part of the entry.
> For example:
>
> History-Info: <sip:[EMAIL PROTECTED];cause=302;
> text="Moved Temporarily">; index=1
>
> The "sip:" and "sips:" URI schemes support headers in the URI, but the
> ABNF for the "tel:" URI scheme (in RFC 3966) does not seem to allow for
> the presence of headers.
>
> So my question is the following - Is it legal for the hi-targeted-to-uri
> to be a "tel:" URI when the Reason and/or Privacy headers are present as
> part of a History-Info entry?
>
> For example, is the following legal:
>
> History-Info: <tel:+1-212-1234567?Reason=SIP;cause=302; text="Moved
> Temporarily">; index=1
>
>
> ============================================
>
> Michael Fortinsky
> [EMAIL PROTECTED]
>
> _______________________________________________
> 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
