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.
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.
Can be both option TCP or TLS
2016-11-21 11:26 GMT+00:00 Daniel-Constantin Mierla miconda@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 Mierlahttp://twitter.com/#!/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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
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@gmail.com mailto:miconda@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@lists.sip-router.org <mailto:sr-users@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>
Sorry for the double email,
I do not use UDP.
I can control also the client side, what do you think that is the simplest way to archive this goal?
best João
2016-11-21 11:37 GMT+00:00 João Resende ms92resende@gmail.com:
Hello,
Can be both option TCP or TLS. I don't test with udp.
best, João
For the topic here I need to look a bit at the code in order to see what can be done now in an easier way. If I find it easier to just add some C code to simplify a bit kamailio.cfg, will you be interested in testing with kamailio master branch (devel version)? Because it would be rather impossible for me these days to setup quickly a testbed for such case..
If you control the client, one thing is to rely on push notifications to optimize some communication with the server. I will also write more once I know how they can be related with the internal structures we have.
Also, for battery life of the watcher as well as getting most up to date information, by subscribing only when the person it's looking at the contact in the body list and subscribe with expires=0 in order to get only one notification...
Cheers, Daniel
On 21/11/16 12:43, João Resende wrote:
Sorry for the double email,
I do not use UDP.
I can control also the client side, what do you think that is the simplest way to archive this goal?
best João
2016-11-21 11:37 GMT+00:00 João Resende <ms92resende@gmail.com mailto:ms92resende@gmail.com>:
Hello, Can be both option TCP or TLS. I don't test with udp. best, João
I can try to test, I think that this would be an important feature to kamailio.
I know that I could do that in the client but it is better be arranged on the server side i guess.
best João
2016-11-21 12:04 GMT+00:00 Daniel-Constantin Mierla miconda@gmail.com:
For the topic here I need to look a bit at the code in order to see what can be done now in an easier way. If I find it easier to just add some C code to simplify a bit kamailio.cfg, will you be interested in testing with kamailio master branch (devel version)? Because it would be rather impossible for me these days to setup quickly a testbed for such case..
If you control the client, one thing is to rely on push notifications to optimize some communication with the server. I will also write more once I know how they can be related with the internal structures we have.
Also, for battery life of the watcher as well as getting most up to date information, by subscribing only when the person it's looking at the contact in the body list and subscribe with expires=0 in order to get only one notification...
Cheers, Daniel
On 21/11/16 12:43, João Resende wrote:
Sorry for the double email,
I do not use UDP.
I can control also the client side, what do you think that is the simplest way to archive this goal?
best João
2016-11-21 11:37 GMT+00:00 João Resende ms92resende@gmail.com:
Hello,
Can be both option TCP or TLS. I don't test with udp.
best, João
-- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
Hello,
I got distracted by other tasks and then the winter holidays. Can you open an item on:
- https://github.com/kamailio/kamailio/issues
not to forget again about this enhancemet request.
Cheers, Daniel
On 21/11/2016 13:09, João Resende wrote:
I can try to test, I think that this would be an important feature to kamailio.
I know that I could do that in the client but it is better be arranged on the server side i guess.
best João
2016-11-21 12:04 GMT+00:00 Daniel-Constantin Mierla <miconda@gmail.com mailto:miconda@gmail.com>:
For the topic here I need to look a bit at the code in order to see what can be done now in an easier way. If I find it easier to just add some C code to simplify a bit kamailio.cfg, will you be interested in testing with kamailio master branch (devel version)? Because it would be rather impossible for me these days to setup quickly a testbed for such case.. If you control the client, one thing is to rely on push notifications to optimize some communication with the server. I will also write more once I know how they can be related with the internal structures we have. Also, for battery life of the watcher as well as getting most up to date information, by subscribing only when the person it's looking at the contact in the body list and subscribe with expires=0 in order to get only one notification... Cheers, Daniel On 21/11/16 12:43, João Resende wrote:
Sorry for the double email, I do not use UDP. I can control also the client side, what do you think that is the simplest way to archive this goal? best João 2016-11-21 11:37 GMT+00:00 João Resende <ms92resende@gmail.com <mailto:ms92resende@gmail.com>>: Hello, Can be both option TCP or TLS. I don't test with udp. best, João
-- 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
Hello,
I already open the issue https://github.com/kamailio/kamailio/issues/915
I can try to help :)
Best, João
2017-01-05 7:59 GMT+00:00 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
I got distracted by other tasks and then the winter holidays. Can you open an item on:
not to forget again about this enhancemet request.
Cheers, Daniel
On 21/11/2016 13:09, João Resende wrote:
I can try to test, I think that this would be an important feature to kamailio.
I know that I could do that in the client but it is better be arranged on the server side i guess.
best João
2016-11-21 12:04 GMT+00:00 Daniel-Constantin Mierla miconda@gmail.com:
For the topic here I need to look a bit at the code in order to see what can be done now in an easier way. If I find it easier to just add some C code to simplify a bit kamailio.cfg, will you be interested in testing with kamailio master branch (devel version)? Because it would be rather impossible for me these days to setup quickly a testbed for such case..
If you control the client, one thing is to rely on push notifications to optimize some communication with the server. I will also write more once I know how they can be related with the internal structures we have.
Also, for battery life of the watcher as well as getting most up to date information, by subscribing only when the person it's looking at the contact in the body list and subscribe with expires=0 in order to get only one notification...
Cheers, Daniel
On 21/11/16 12:43, João Resende wrote:
Sorry for the double email,
I do not use UDP.
I can control also the client side, what do you think that is the simplest way to archive this goal?
best João
2016-11-21 11:37 GMT+00:00 João Resende ms92resende@gmail.com:
Hello,
Can be both option TCP or TLS. I don't test with udp.
best, João
-- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 28-30, 2016 - http://www.asipto.com
--
Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com