1 Jul
2010
1 Jul
'10
10:34 p.m.
2010/7/1 Juha Heinanen <jh(a)tutpro.com>om>:
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@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@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@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?
Isn't a bug in Twinle (even if I realized of it using Twinkle and K
1.5 with SIP TCP)? This is: what is the TCP difference between the
SUBSCRIBE sent by Twinkle before and after restarting it?
--
Iñaki Baz Castillo
<ibc(a)aliax.net>