[sr-dev] tcp problems exists also in older version of sr

[Andrei Pelinescu-Onciul]

On Oct 30, 2009 at 10:44, Juha Heinanen <jh at tutpro.com> wrote:
> i thought that tcp problem (using wrong ip address) appeared only in
> latest sr code, but now i saw it also in older version.
> 
> to repeat, register twinkle using tcp from behind nat.  call twinkle
> from another sip phone that is using udp.  twinkle receives 200 ok, but
> never the ack.  sr cannot forward ack to twinkle and reports:
> 
> Oct 30 10:36:56 localhost /usr/sbin/sip-proxy[3911]: WARNING: <core> [tcp_main.c:1200]: WARNING: tcp_do_connect 192.168.0.169:5074: could not find corresponding listening socket for 192.X.Y.2, using default... 
> Oct 30 10:36:57 localhost /usr/sbin/sip-proxy[3924]: INFO: Routing in-dialog BYE from <sip:foo.bar at bar.com> to <sip:jh_bar_com at 192.168.0.169:5074;transport=tcp>Oct 30 10:37:01 localhost /usr/sbin/sip-proxy[4023]: ERROR: <core> [tcp_main.c:3747]: connect 192.168.0.169:5074 failed (timeout)  
> 
> where 192.X.Y.2 is NONE of the addresses sr is listening at, but ip of
> eth0 interface.

Use 
tcp_source_ipv4=....
if you want a force source address, or make sure the route to 192.X.Y.0
 use src=desired_src_address or just let sr listen on all interfaces.

Andrei