Jonathan Rosenberg wrote:
[snip]
> There are two cases here that are being intermixed.
> 
> In case one, the originating UA wants to reach a user with a specific
> username AND domain name, and that domain name is totally outside the
> network of the originating UA. For example, if I want to reach [EMAIL PROTECTED],
> and I'm within bar.com. In case two, I'm on a gateway and I dial a number.
> There is not really a destination domain associated with this number. What
> should it be?

Yes - I don't think I was very clear originally in saying the
problem I have is with implementations that cannnot deal with
reaching a user who's domain is outside their the network.
They always re-write the Request-URI to be the local domain, 
even when this is clearly the wrong thing to do. I would also 
argue that when an implementation does rewrite the Request-URI 
to the local domain it is much better to use a domain name than 
the proxy's IP address.

Cheers,
Neil
-- 
Ubiquity Software Corporation, UK        http://www.ubiquity.net

> In case one, it is absolutely INCORRECT to modify the request URI to be my
> local domain. When sending the request to my local proxy, it would look
> like:
> 
> INVITE sip:[EMAIL PROTECTED] SIP/2.0
> 
> and then be sent NOT to foo.com, but to my local proxy. Changing the request
> URI to bar.com to reach the local proxy is an error; user joe is not within
> that namespace.
> 
> However, in case two, the destination number can rightly be considered to be
> within the domain of the orginating caller. Thats because it knows how to
> reach phone numbers. Remember, just because a proxy for bar.com gets a
> request with a URI thats [EMAIL PROTECTED], does not mean a user some-name
> must have registered with a REGISTER. It means that the proxy for bar.com
> knows what to do with the user some-name. Its perfectly fine for this proxy
> to treat numbers in the user part of its domain as telephone numbers,
> especially if they are indicated as such with user=phone, and then route
> them to a gateway with some phone routing database.
> 
> So, in that case, if I'm in bar.com, and I dial a number - 5551212, its
> reasonable to send that to my own proxy with the URI [EMAIL PROTECTED] In
> this case its not even really a local-outbound proxy anymore. Using the IP
> address of the proxy is also OK IFF the proxy is configured to know that
> requests with that given IP address represent "its domain of ownership".
> Using the domain name is better for lots of reasons, though, including SRV
> usage. Whether this is allowed is a matter of configuration.
> 
> -Jonathan R.

Reply via email to