Thx Andrew,
So according to the standard, it must be escaped but in reality it is
send not escaped. So it depends on the SIP stack implementation if it
will be considered as a valid request or not ? Product A will parse
the message but product B can drop the message because it strictly
implements RFC3261 and considers the message being invalid ?
Regards,
Kurt
On 23 May 2008, at 17:47, Andrew Pogrebennyk wrote:
> Kurt,
>
> Look into the section 25.1 of RFC3261:
>
> SIP-URI = "sip:" [ userinfo ] hostport
> uri-parameters [ headers ]
> userinfo = ( user / telephone-subscriber ) [ ":" password ] "@"
> user = 1*( unreserved / escaped / user-unreserved )
> user-unreserved = "&" / "=" / "+" / "$" / "," / ";" / "?" / "/"
> unreserved = alphanum / mark
> mark = "-" / "_" / "." / "!" / "~" / "*" / "'"
> / "(" / ")"
> escaped = "%" HEXDIG HEXDIG
>
> So, any character MAY be quoted (using "escaped" construct) (but
> SHOULD NOT if "unreserved", see 2.3 of RFC2396), and some
> characters SHALL be quoted (because they are not listed in
> unreserved or user-unreserved). So, '#' SHALL be escaped (but is
> often written unescaped in the real world).
>
> Mailing List wrote:
>> Hi,
>> Is it allowed to have the "#" in the request uri (.e.g. sip:999#
>> [EMAIL PROTECTED] ) or in the Contact header or must it be escaped
>> using %23 (
>> [EMAIL PROTECTED]).
>> Thx
>> Kurt
>
> --
> Sincerely,
> Andrew Pogrebennyk
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
