2009/9/16 Iñaki Baz Castillo <[email protected]>: > ---------- > If hostname is not NULL, Request-URI is rewritten based on gateway's > URI scheme and hostname, and destination URI is set based on gateway's > URI scheme, IP address, port, and transport protocol. Upon subsequent > calls, the same is done, but instead of rewriting Request URI, a new > branch is added. > --------- > > Ok, this could explains my issue (however, $ru *is* rewritten for the > first selected gw !!!). > > > Anyhow, I also read: > > --------------- > 1.3.6. hostname_column (string) > Name of the column holding gateway's hostname that is used in > Request-URI, when request is sent to the gateway. Note that request is > not forwarded based on hostname, but based on gateway's IP address in > destination uri. > --------------- > > I'd really would like this to be true, but the fact is that, after the > first gw fails, I receive an error (if it has a custom hostname): > > Sep 16 18:22:45 [25444] CRITICAL:core:mk_proxy: could not resolve > hostname: "lolololololo" > Sep 16 18:22:45 [25444] ERROR:tm:uri2proxy: bad host name in URI > <sip:qwwsad...@lolololololo>
One more possible issue: As far as I understand 'next_gw()' sets $du. However, I do t_on_branch before relaying the request and $du is <null>. How is possible? This occurs for the first selected gw and for the others. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
