> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of ext Paul Kyzivat > Sent: Wednesday, July 02, 2008 1:32 PM > To: Iñaki Baz Castillo > Cc: [email protected] > Subject: Re: [Sip-implementors] request uri scheme for > REGISTER request > > > > Iñaki Baz Castillo wrote: > > El Wednesday 02 July 2008 18:10:36 Paul Kyzivat escribió: > >> But conventions could be established. Certainly it is tempting to > >> consider transforming > >> > >> tel:1234;phone-context=example.com > >> into sip:[EMAIL PROTECTED] > >> or sip:1234;[EMAIL PROTECTED] > > > > What is the last line?: > > sip:1234;[EMAIL PROTECTED] > > > > The username is: > > 1234;phone-context=example.com > > > > Well, it's a perfeclty valid userinfo in SIP ABNF grammar > (I've tested it just > > now), but since there are no "userinfo" parameters the UAS > receiving this URI > > will not match "1234" but the whole > "1234;phone-context=example.com".
I don't think anyone should expect a UAS to behave any differently than what you've stated. For example; "1234;phone-context=example.com" and "1234;phone-context=example2.com are different users. As stated earlier, this would be useful in support extension dialing (private numbering plans) where these users may not have a direct number to be reached from outside their private domain. It seems useful to allow the phone-context be used privately, not necessarily the same as the URI hostport, but this is up to the network configuration. For example: "sip:1234;[EMAIL PROTECTED]" The request can be routed from outside acme.com to the server for acme.com by locating its service address via DNS SRV, but once inside acme.com, further analysis would be needed to locate the specific service address or server responsible for user "1234;phone-context=deptx.acme" > > > > Is really usable that "userinfo" in real life? > > Well, I said I was imagining ways to transform one into another. > It may not be useful. > > Maybe more sensible way is to use sip:example.com as a Route, > and leave > the tel URI as is in the R-URI. > > Paul > _______________________________________________ > 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
