Would be nice if it would be possible to - make timer of "default_timeout" reset to 0 when keep-alive reply is received from remote part of call leg, so that the timeout expires (triggering call termination) only if some call party gets offline (we don't want just to limit the duration of normal call, even if call parties don't send any new SIP requests); OR - make unresponsiveness of call parties to keep-alive messages (controlled with ka_timer, ka_interval parameters) lead to some action, like call termination.
Please advise if I miss something, and how to implement this better. Thanks in advance.
Hello,
On 06/07/15 12:29, Andrey Utkin wrote:
Would be nice if it would be possible to
- make timer of "default_timeout" reset to 0 when keep-alive reply is
received from remote part of call leg, so that the timeout expires (triggering call termination) only if some call party gets offline (we don't want just to limit the duration of normal call, even if call parties don't send any new SIP requests); OR
- make unresponsiveness of call parties to keep-alive messages
(controlled with ka_timer, ka_interval parameters) lead to some action, like call termination.
Please advise if I miss something, and how to implement this better. Thanks in advance.
if there is no response to keepalive, the call should be terminated in like 10 seconds.
Cheers, Daniel
2015-07-07 10:07 GMT+03:00 Daniel-Constantin Mierla miconda@gmail.com:
if there is no response to keepalive, the call should be terminated in like 10 seconds.
Thank you for quick reply Daniel. Can this be different for the case of TLS connections? I guess this can matter.
2015-07-08 15:22 GMT+03:00 Andrey Utkin andrey.krieger.utkin@gmail.com:
2015-07-07 10:07 GMT+03:00 Daniel-Constantin Mierla miconda@gmail.com:
if there is no response to keepalive, the call should be terminated in like 10 seconds.
Thank you for quick reply Daniel. Can this be different for the case of TLS connections? I guess this can matter.
Terrible sorry, it turned out that I was wrong - keepalives actually were not sent, because this was missing:
dlg_set_property("ka-src"); dlg_set_property("ka-dst");
Before, I just had set "ka_timer" and "ka_interval" and thought it is enough, and it is not obvious from module manual that it is not enough. Also Kamailio was sometimes sending OPTIONS, bug I guess to test availability of registeration entries, and I thought they are dialog keep-alive requests. Is a documentation update pull request welcome, to add a note that dlg_set_property() is necessary to enable KA sending?
-
Andrey Utkin -
Daniel-Constantin Mierla