Re: [reSIProcate-users] Using hostname in RR/Via causing send to fail

[Andrew Wood <ajwood@xxxxxxx>]

Thanks Adam that makes a bit more sense now.

What I wanted to do is use the hostname rather than an IP in case a 
particular server failed, that way stuff could still be sent to the 
backup proxy.

Strange how with an IP it can find a transport but not with a hostname


Adam Roach wrote:
> Andrew Wood wrote:
> > But why is it the RR & Via header causing the problem? Surely that 
> > shouldnt make any difference to where the request is sent to?
>
> No, but the value in the Via header field makes a difference where it 
> is sent *from*. The log you sent is saying that the proxy can't find 
> an appropriate transport to send from.
>
> You're kind of treading new ground here. While I'm certain there are 
> some provisions in resip for stateless proxy handling, I don't know of 
> anyone who has built it to build a full-fledged stateless proxy. For 
> any application *other* than a stateless proxy, it makes no sense to 
> put anything in the Via header field other than an IP address -- 
> responses have to come back through exactly the same box the request 
> did so that the transaction can be correlated correctly.
>
> In fact, even with a stateless proxy, putting a name in the Via header 
> field really gains you nothing. Except for certain very old RFC 
> 2543-based clients, the next hop is going to tag any such Via with a 
> "received=192.168.254.201," and make sure that the response goes back 
> there.
>
> Short answer: put your IP address in the Via header field, and this 
> should all just work. You can (and should) continue to use the DNS 
> name in the Record-Route header field.
>
> /a
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email 
> ______________________________________________________________________