Hello Community,
in my scenario works multiple user with the kamailio server and uses different clients. They work in a mobile scenario and setup the clients and break the clients in a high period. If they break the clients, sometimes they don't send a bye, but they take off the cable connection during a call. If these devices will connected again and other clients try to call them, they are busy. That is my problem :). Does the Kamailio server provides any function to send a bye message if a clients don't register at a required time? Or is there another solution available? Thanks for help.
Cheers, Kai
On Fri, May 06, 2016 at 07:13:19AM +0000, kai.ohnacker@cbc.de wrote:
in my scenario works multiple user with the kamailio server and uses different clients. They work in a mobile scenario and setup the clients and break the clients in a high period. If they break the clients, sometimes they don't send a bye, but they take off the cable connection during a call. If these devices will connected again and other clients try to call them, they are busy.
Who is generating this busy? Kamailio ("default" config) normally doesn't care.
That is my problem :). Does the Kamailio server provides any function to send a bye message if a clients don't register at a required time? Or is there another solution available?
This is what Session-Timers try to solve (and most of the times fails to due to broken endpoint implementations IMHO).
The dialog module has a keep alive mechanism: http://www.kamailio.org/docs/modules/stable/modules/dialog.html
Take a look at the ka_time/ka_interval/send_bye (and setting ka-src/dst).
Alternatively you could monitor this with an external script, kill dialogs involving users that aren't registered (kind of braking SIP since originating calls and registrations have nothing to do with each other).
-
Daniel Tryba -
kai.ohnacker＠cbc.de