Hello,
if option 2 was easy to setup and gets the job done, I would personally just stay there instead of spending more time on other options.
Cheers,
Henning
From: Sergio Charrua via sr-users sr-users@lists.kamailio.org Sent: Sonntag, 22. Juni 2025 17:43 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Cc: Sergio Charrua sergio.charrua@voip.pt Subject: [SR-Users] Dispatcher vs Keepalive
Hello all,
Just wondering your opinions on this.... The project I'm in uses a REST API to get the routes to relay the call to, and one of the main requirements is whenever an egress gateway is down, inform the REST API about its status, and the same once the gateway is up again. So I was reading the modules docs and was stuck with a question: what would be the best solution to keep track of egress gateways availability?
1 - using Keepalive with DRouting to ping each endpoint's address:port , even though the solution is going to use RTJson with the JSON route list returned from a REST API which makes DRouting virtually useless, unless for using the list of gateways to send OPTIONS too. There is no event:routes to execute every time a gateway is down or up....
2 - using Dispatcher module to "watch" for each endpoint's availability, and make use of the event:route of the Dispatcher module to inform REST API that the endpoint is down or back up once again. Again, RTJson with the JSON route list returned from the REST API would be used to manage routing.
I've done a few tests with Dispatcher, and it was really easy to setup the endpoint "watching" mode as well as the event:routes, but I might give a try on Keepalive if it is the better bet.
Would greatly appreciate your opinions and expertise on this.
Atenciosamente / Kind Regards / Cordialement / Un saludo,
Sérgio Charrua