[SR-Users] presentity tabla, faster update when drop TCP/TLS connection

Daniel-Constantin Mierla miconda at gmail.com
Mon Nov 21 12:36:09 CET 2016


But no UDP, right? It's what I wanted to know in order to see what kind
of patterns can be applied, given that the UDP is connectionless.

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).

Btw, it's your client (I mean, can you control its
development/features), or it is just some generic sip softphone? Because
there can be some tricks added to the client side as well if you control it.

Cheers,
Daniel

On 21/11/16 12:27, João Resende wrote:
> Can be both option TCP or TLS
>
> 2016-11-21 11:26 GMT+00:00 Daniel-Constantin Mierla <miconda at gmail.com
> <mailto:miconda at gmail.com>>:
>
>     Hello,
>
>     are the clients connected over upd or tcp/tls?
>
>     Cheers,
>     Daniel
>
>     On 21/11/16 12:13, João Resende wrote:
>>     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. Exists a way
>>     to define this? or it is a bug? or should be a new feature?
>>
>>     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. 
>>
>
>     -- 
>     Daniel-Constantin Mierla
>     http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda
>     <http://www.linkedin.com/in/miconda>
>     Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
>
>     _______________________________________________ SIP Express Router
>     (SER) and Kamailio (OpenSER) - sr-users mailing list
>     sr-users at lists.sip-router.org
>     <mailto:sr-users at lists.sip-router.org>
>     http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>     <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> 
>
-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20161121/82439a61/attachment.html>


More information about the sr-users mailing list