[asterisk-dev] Idle Timers and Keep-Alives

[Ross Beer]

Could the operating system manage this also, for example with the following:

sysctl.conf

net.ipv4.tcp_fin_timeout = 60
net.ipv4.tcp_retries1 = 3
net.ipv4.tcp_syn_retries = 5

# Keep TCP connections alive
net.ipv4.tcp_keepalive_time = 300
net.ipv4.tcp_keepalive_intvl = 60
net.ipv4.tcp_keepalive_probes = 20

>From a chan_pjsip point of view, it would receive notification that the underlying connection has closed.
________________________________
From: asterisk-dev-bounces at lists.digium.com <asterisk-dev-bounces at lists.digium.com> on behalf of Alexander Traud <pabstraud at compuserve.com>
Sent: 05 January 2018 15:44
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Idle Timers and Keep-Alives

> Do we even WANT an idle timer?

I posted my concerns already in <http://gerrit.asterisk.org/6807>: I have a device which crashes when it receives such a keepalive. I could live with a timer when Asterisk is not the registrar but registered somewhere else. But I do not _need_ that either.



--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20180105/45180fa8/attachment.html>