3 Jan
2020
3 Jan
'20
2:40 p.m.
Hello,
still enjoying a few days out of the office, so I haven't gone to the code
to check and say something for sure, but I expect to be rather simple to
add support for out-of-dialog keepalive -- a different tm function has to
be used, the callback function for response handling and params likely to
be mostly reuse of existing code.
Cheers,
Daniel
On Thu, Jan 2, 2020 at 10:01 PM Alex Balashov <abalashov(a)evaristesys.com>
wrote:
On Thu, Jan 02, 2020 at 09:26:23PM +0100,
Daniel-Constantin Mierla wrote:
--
Daniel-Constantin Mierla - https://www.asipto.com
https://twitter.com/miconda - https://www.linkedin.com/in/miconda
Kamailio Advanced Training - https://www.asipto.com/u/kat
There can be also another (simpler, half-way)
variant where the
OPTIONS are sent out of the dialog just to detect when the caller or
callee is disconnected () from the network, which is the usual case
that can happen. Sending the OPTIONS within the dialog is for
additional detection of the case when the call was cut somehow event
the end point it is still on the net (e.g., buggy UA).
Hi Daniel, thanks for your response.
What is the simplest thing to do here for a time-economic point of view?
Might it be to add a modparam which indicates whether requests are sent
in-dialog or out-of-dialog? Or does the instrumentation for that require
a lot of conditional logic at various points due to the amount of state
kept in the in-dialog case?
Thanks!
-- Alex
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users