This enhancement is submitted to improve the SIP and HTTP charactristics during
A preferred solution for a Ericsson point of view would be to implement a time-
to-live (TTL) feature on each socket. The TTL would be expressed in time or
number of messages and once the TTL expires the socket would be closed in a
controlled way. Once a socket is closed it would be up to the sip-stack or
external node to re-open them again according to the standard behavior.
Also making it possible to set the TTL in runtime would enable us to lower it
during upgrades when a lot of changes in the cluster membership will happen.
Once the system is back in a stable state the TTL could be set to a very high
I believe it's a trade-off between the time it takes to even out the load after
a failure and the impact on traffic.