Hi people, this is my first time that I writing to this list and I nedd some help... When kamailio lost connection with a user registred over TLS (timeout for examlple), I want this user be unregister in kamailio too. How can I make this unregister?
Thank you...
2010/4/20 Bruno Bresciani bruno.bresciani@gmail.com:
Hi people, this is my first time that I writing to this list and I nedd some help... When kamailio lost connection with a user registred over TLS (timeout for examlple), I want this user be unregister in kamailio too. How can I make this unregister?
It's a commendable feature request, but it's not implemented right now.
On 4/20/10 7:30 PM, Iñaki Baz Castillo wrote:
2010/4/20 Bruno Brescianibruno.bresciani@gmail.com:
Hi people, this is my first time that I writing to this list and I nedd some help... When kamailio lost connection with a user registred over TLS (timeout for examlple), I want this user be unregister in kamailio too. How can I make this unregister?
It's a commendable feature request, but it's not implemented right now.
it might now be easy to catch connection lost (forward or wait state case). Also, unregistering a contact is not really following the rfc, anyhow, this is not something complex to add if you have the contact details.
What you can do right now is to avoid trying to send if the connection is not longer open, see: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#set_forward_no...
Contact is in memory, but no penalty for performances. Very useful for NAT cases or when UA is supposed to keep the connection open.
Cheers, Daniel
On 4/20/10 8:29 PM, Daniel-Constantin Mierla wrote:
On 4/20/10 7:30 PM, Iñaki Baz Castillo wrote:
2010/4/20 Bruno Brescianibruno.bresciani@gmail.com:
Hi people, this is my first time that I writing to this list and I nedd some help... When kamailio lost connection with a user registred over TLS (timeout for examlple), I want this user be unregister in kamailio too. How can I make this unregister?
It's a commendable feature request, but it's not implemented right now.
it might now be easy to catch connection lost (forward or wait state case).
^^^ I meant: it might NOT be easy ...
E.g., for forward case, detection is after config processing, when trying to relay. If there are many branches, it is not even reported if one branch succeeds or sends another negative reply code.
Also, unregistering a contact is not really following the rfc, anyhow, this is not something complex to add if you have the contact details.
What you can do right now is to avoid trying to send if the connection is not longer open, see: http://www.kamailio.org/dokuwiki/doku.php/core-cookbook:3.0.x#set_forward_no...
Contact is in memory, but no penalty for performances. Very useful for NAT cases or when UA is supposed to keep the connection open.
Cheers, Daniel
-
Bruno Bresciani -
Daniel-Constantin Mierla -
Iñaki Baz Castillo