Thanks for your Henning, at least I will sleep better knowing I am not completly idiot :-))Starting with 3.0, most of tcp parameters are changeable at runtime via RPC (you can use sercmd):
I haven't noticed related to INVITE timers (such as the 408) because I only make my client behind NAT to register and re-register and verify it is always reachable in time thanks to this TCP keep-alive. Tomorrow I will try to make a couple a calls to see if I get this 408 you mentionned.
Is there a way (either with a parameter or changing source code) a to control the frequency of TCP k.a. ?
CheersPascal
2010/5/7 Henning Westerholt <henning.westerholt@1und1.de>
On Friday 07 May 2010, Pascal Maugeri wrote:> [..]
> tcp_keepalive=yes
> tcp_keepidle=10
> tcp_connection_lifetime=3600
>
>
> The TCP connection is kept alive and TCP Keep-Alive packets are sent when
> the TCP connection is idle.
>
> But I don't understand why the time between KA is not linear:
> Could you explain me where do come from these values of 75 seconds, 23, 54Hi Pascal,
> ?
>
> Everything works well: my client behind NAT is kept connected but I'd like
> to understand why it does work :-)
sounds indeed interesting. :-) Perhaps a problem with the internal timers.. Do
noticed also other timer related problems, like for internal INVITE 408
replies or similar?
Cheers,
Henning
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-- Daniel-Constantin Mierla * http://www.asipto.com/ * http://twitter.com/miconda * http://www.linkedin.com/in/danielconstantinmierla