[sr-dev] tcp quick connect is not done reliably

Juha Heinanen jh at tutpro.com
Thu Jul 1 20:27:03 CEST 2010


i have noticed that after i restart sip router, it does not immediately
try to do tcp quick connect when it relays request over tcp.

after restarting sr, i start twinkle and relaying over tcp fails:

Jul  1 21:19:53 localhost /usr/sbin/sip-proxy[24197]: INFO: Routing initial SUBSCRIBE <sip:jh at vm.test.fi> to <sip:127.0.0.1:5082;transport=tcp>
Jul  1 21:19:53 localhost /usr/sbin/sip-proxy[24197]: INFO: t_relay failed with result -1
Jul  1 21:19:53 localhost /usr/sbin/sip-proxy[24197]: INFO: Routing initial PUBLISH <sip:jh at test.fi> to <sip:127.0.0.1:5082;transport=tcp>
Jul  1 21:19:53 localhost /usr/sbin/sip-proxy[24197]: INFO: t_relay failed with result -1

then i restarted twinkle and quick connect was correctly done:

Jul  1 21:20:23 localhost /usr/sbin/sip-proxy[24199]: INFO: Routing initial SUBSCRIBE <sip:jh at vm.test.fi> to <sip:127.0.0.1:5082;transport=tcp>
Jul  1 21:20:23 localhost /usr/sbin/sip-proxy[24199]: INFO: <core> [tcp_main.c:1926]: tcp_send: quick connect for 0xb4e70878

why is quick connect not done reliably?

-- juha



More information about the sr-dev mailing list