26 feb 2009 kl. 10.14 skrev Theo Zourzouvillys: > On Thu, Feb 26, 2009 at 8:48 AM, Johansson Olle E <[email protected]> > wrote: >> So looking at the BNF, it's >> user-param = "user=" ( "phone" / "ip" / other-user) >> >> What is user=ip ? > > This is the default when there is no "user" parameter in the URI, and > it, means that the user part or the URI is an identifier at the host > being addressed in the host porition of the URI. TO be picky - you say only host. Does this also imply that the domain part is indeed a host and should not be looked up for NAPTR/SRV records?
> > >> And user=<other-user> > > RFC4967 is the other defined one. Thanks. user=dialstring Anyone that has seen this anywhere? > > > Also note while on the subject, tel URI's SHOULD be a global-number > (+xxxx) or have a phone-context parameter, so: > > sip:[email protected];user=phone > > is wrong, and should either be: > > sip:[email protected];user=phone > (which is the same as tel:+441234567890) > > or > > sip:441234567890;[email protected];user=phone > (which is the same as tel:44123456789;phone-context=mydomain.com) > > note however that 2806 (which 3261 references for > telephone-subscriber) does not MUST the context parameter, only SHOULD > - however rfc3966 (which updates 2806) makes the phone-context > parameter a MUST. Thanks for that update! That was an important change indeed. The problem here is always interoperability. If we force that in software - rejecting calls with user=phone and no phone-context - users will start screaming. As always, we should propably try enforcing this, which means that in most cases moving treating user=phone as user=dialstring on incoming calls and setting user=dialstring on outbound will match the current level of implementations. /O _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
