Hello,
I'm testing kamailio with a SIP client with presence support, when I get a connection
drop from a client (i.e when the client lost the access to the Internet connection) I do
not receive the change in the status to offline immediately, I just received when the
timeout from the presentity database finishes.
I know that I'm able to change the expiry parameter from the presentity table, but
that increases my battery consumption and the data exchange, the same happens if I reduce
the publish interval on the client side.
The connection with the server are connected with the TLS or TCP.
@miconda Suggested that a solution could be:
"For TCP/TLS, what can work, it's to use tcpops module which can execute an event
route when a tcp/tls connection is dropped. If you track the association of connection id
with the call-id of the presence publish, then you may be able to do some tricks and lower
the expires of the published presence state. I haven't had the time to see what's
possible there, but could worth investing.
An alternative would be to enhance presence module to behave as registrar/usrloc (which
can delete contact records on connection drop) to expire documents when tcp/tls connection
is closed (not sure if anyone already added it)."
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/915