I added some notes about the monitoring type in the readme, improvements are
welcome. Closing this one.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1082#issuecomment-308110351
Closed #1082.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1082#event-1121331792___
Kamailio (SER) - Development Mailing List
sr-dev@lists.kamailio.o
@juha-h - the inter-module/devel api are not required to be in the readme,
there were some attempts in the past, but none really maintained. For example
tm exports couple of dozens of functions, auth has also several exports, ...
Instead it would be good to have proper comments in the code for t
Hi @agranig, @kamailio-sync @
First, the module is still young, so the documentation may be incomplete. I
will improve it asap
Second, my primary idea when started this module was to implement the same
"destinations probing" mechanism found in dispatcher module, both in drouting &
carrierroute
Andreas Granig writes:
> The new keepalive module states that it "performs destinations
> monitoring either for itself, or on the behalf of other modules".
Regarding "on behalf of other modules", I didn't find any API function
documentation in README file.
-- Juha
__
More information in docs is always good. Hopefully @gbour will add more there.
To answer quickly some of your questions based on my review:
* it is SIP-based monitoring (keepalive pinging with OPTIONS, like dispatcher
does)
* PR #1066 enhanced drouting to use keepalive module for monitoring
The new keepalive module states that it "performs destinations monitoring
either for itself, or on the behalf of other modules".
What does that mean?
What are the use cases and which problems does it solve?
Which mechanisms does it use (SIP, ICMP, others?)
Some examples would greatly help in the
