11 Jan
2011
11 Jan
'11
10:49 a.m.
Hi Juha,
have the TCP keepalives addressed the problem? If not, could you send
a PCAP? (ideally from both upstream and downstream perspective)
Thanks!
-jiri
On 1/10/11 11:32 AM, Andrei Pelinescu-Onciul wrote:
On Jan 09, 2011 at 21:41, Juha
Heinanen<jh(a)tutpro.com> wrote:
Andrei Pelinescu-Onciul writes:
It uses setsockopt (if tcp_keepalive = yes is present in the .cfg).
You don't have to change any kernel variables in proc for sr. You just
need to enable keepalives and set the intervals in the .cfg file
(the above example could be pasted directly in a ser.cfg).
Andrei
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
However you could enable tcp level keepalives and
on linux you can tune
the intervals, e.g.:
tcp_keepalive = yes
tcp_keepidle = 60
tcp_keepintvl = 10
tcp_keepcnt = 3
andrei,
my linux 2.6.32 kernel has these tcp keepalive variables:
tcp_keepalive_intvl tcp_keepalive_probes tcp_keepalive_time
linux tcp keepalive doc says:
Remember that keepalive support, even if configured in the kernel, is
not the default behavior in Linux. Programs must request keepalive
control for their sockets using the setsockopt interface. There are
relatively few programs implementing keepalive, but you can easily add
keepalive support for most of them following the instructions explained
later in this document.
question: does sr request that tcp keepalive is turned on on its tcp
connections or via a function call on a particular connection?