Hadriel Kaplan wrote:
>
>> -----Original Message-----
>> From: sip-implementors-boun...@lists.cs.columbia.edu [mailto:sip-
>> implementors-boun...@lists.cs.columbia.edu] On Behalf Of Iñaki Baz
>> Castillo
>> Sent: Thursday, March 12, 2009 5:59 PM
>>
>> What to do with the SIP URI host part?
>
> They're gone. They were attributes of the SIP URI, not a TEL URI.
>
>
>> Could these SIP userinfo "parameters" be ignored?:
>
> Nope, you shouldn't ignore them. If you ignore them you're affecting the
> resultant TEL URI you create. For example the common TEL URI parameters of
> "rn" and "npdi" are pretty important to keep around. :)
>
> But assuming you are authoritative for the domain of the SIP-URI, and
> actually understand the user parameters (instead of just treat them as opaque
> strings), then you can pretty much do what you want. Ultimately you're doing
> local policies, because the SIP-URI referenced your domain, and you're
> authoritative for it. (btw, what URI are you changing - the req-uri?)
I'd like to re-emphasize and expand what Hadriel is saying:
A server authoritative for the domain of the sip URI may do this, or
*any* conversion of the URI as it wishes.
But if you are *not* authoritative for the domain of the URI, then you
have no business doing this translation at all. Just because the URL
appears to contain a phone number does not mean you are permitted to do
the conversion. The conversion loses information and may not preserve
the intent of whoever supplied the URI.
For instance, it may be that its important that the connection be made
via sip. Once converted to TEL, subsequent routing may take it to a GW
and out of the sip protocol.
Thanks,
Paul
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
