On 16-10 21:29, Olle E. Johansson wrote:
i.e., it might make sense to have a configurable max number of tcp connections and then start closing them based on longest inactivity when the limit is exceeded.
Makes sense to me also.
If I understand the NAT problem, NAT devices may also close inactive TCP sessions. This is weird, but it obviously happens. This might be solved by the "NAT ping" stuff in module NAThelper being changed to send a SIP options request on an open TCP session with regular interval.
Better than OPTIONS is a short message consisting of four zeroes only. We also extended usrloc and modified natpinger so it can be configured to ping hosts that are behind NAT only (information about presence of a NAT is stored in location table). When this is enabled it will work regardless of the transport protocol.
Jan.