22 May
2015
22 May
'15
3:03 p.m.
On 22/05/15 14:53, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
current readme text lets the reader to understand that
handle_lost_tcp
applies to all modes:
If set to 1, Kamailio will remove location records made via
TCP/TLS/WS/WSS transports when it looses corresponding tcp
connections.
in order to avoid confusion, perhaps it should list in which modes the
variable has effect.
Add anything that is relevant to docs. The feature came via a patch from
the community, iirc -- maybe the docs were not clear as the commit comments.
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio World Conference, May 27-29, 2015
Berlin, Germany - http://www.kamailioworld.com
Just to
make sure, does handle_lost_tcp now work also in DB-Only mode?
IIRC, the intitial implementation was based on iterating through the
records in memory and checking if the associated connection still
exists. It is in the same iteration to detect expired records. So I
don't think it was extended for db only as I have not noticed any update
on it. With current approach will required loading all records in memory
to check. A different approach to act when connection has been closed
and the query the database for its id might be better.
A recent addition was to close the tcp connection if the associated
usrloc record has expired.