Re: [reSIProcate-users] How to detect TCP connection failure
Without the pong timeout, the on going receive on the TCP socket should eventually produce a socket error - sometimes up to 2 min after the last send attempt on the socket. Keepalives help here to ensure we are constantly sending something.
If you need faster detection via the Keepalive Pong logic, then the other side must conform to RFC5626 and send a keepalive pong when it receives the ping. This behaviour is enabled in resip only when RFC5626 (outbound) support is fully turned on. More info on this is here:
http://www.resiprocate.org/DUM_Client_Outbound_Support
You do not need to call KeepAliveManager add. This is called by DUM when you create a registration or a dialog to a destination (as long as the keepliave manager is enabled).
Scott