26 feb 2009 kl. 09.38 skrev Theo Zourzouvillys: > On Thu, Feb 26, 2009 at 8:32 AM, Johansson Olle E <[email protected]> > wrote: > >> I've seen that - but that's not a reference to a Tel: uri. > > Yes, it is - telephone-subscriber is straight out of rfc2806. Thanks, that is exactly what I missed. Then it's more clear and I can write off the other implemenations as buggy.
Btw, 2806 is obsoleted by RFC 3966. Asterisk has an option where we add user=phone only if the user part of the request URI is a valid phone number according to the tel: rfc. > > >> In my opinion, this is >> very vague and implementations differ a lot. I've seen >> implementations >> that require only digits when user=phone is set. > > Just because some implementations don't do what the spec says it > doesn't mean it's vague: it means people don't read things and > implement them properly :-) Yes. But I missed that telephone-subscriber was a reference to rfc 2806 > > >> The Tel: Uri allows other characters, especially the "+". > > it allows those defined by telephone-subscriber in rfc2806, with the > exception called out in 19.1.2: > > The telephone-subscriber subset of the user component has special > escaping considerations. The set of characters not reserved in the > RFC 2806 [9] description of telephone-subscriber contains a number > of > characters in various syntax elements that need to be escaped when > used in SIP URIs. Any characters occurring in a telephone- > subscriber > that do not appear in an expansion of the BNF for the user rule MUST > be escaped. So looking at the BNF, it's user-param = "user=" ( "phone" / "ip" / other-user) What is user=ip ? And user=<other-user> /O _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
