Hello Henning,
I tried the dialog profile sharing with dmq&dialog modules and now the syncing works between the two kam nodes. Thank you!
Is there a way to keep the dialog profiles persistent (load from db if kam restarts)? I was thinking a scenario where kam1 has already the call limit maxed out and kam2 suddenly reboots and after reboot, kam2 should be aware of dialogs on kam1 to be able to limit calls again correctly.
Cheers, Olli
Hi Olli,
if I have interpreted the question and the situation in which you are correctly, the way to persist a dialog in DB is to use the db_mode param https://kamailio.org/docs/modules/5.2.x/modules/dialog.html#dialog.p.db_mode you have 4 possibilities to persist that data in DB
-
*0 - NO_DB* - the memory content is not flushed into DB; -
*1 - REALTIME* - any dialog information changes will be reflected into the database immediately. -
*2 - DELAYED* - the dialog information changes will be flushed into DB periodically, based on a timer routine. -
*3 - SHUTDOWN* - the dialog information will be flushed into DB only at shutdown - no runtime updates.
Cheers,
Giovanni
--
Giovanni Tommasini | evosip
web: https://evosip.cloud
Il giorno ven 4 ott 2019 alle ore 08:31 Olli Attila attiolli@gmail.com ha scritto:
Hello Henning,
I tried the dialog profile sharing with dmq&dialog modules and now the syncing works between the two kam nodes. Thank you!
Is there a way to keep the dialog profiles persistent (load from db if kam restarts)? I was thinking a scenario where kam1 has already the call limit maxed out and kam2 suddenly reboots and after reboot, kam2 should be aware of dialogs on kam1 to be able to limit calls again correctly.
Cheers, Olli _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hello Olli,
the profile information should be also synchronized with DMQ – but not sure if they are also synchronized during startup. If kam2 reboots it should get the dialog information from kam1 after it has started.
Have you tried if its works already?
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://skalatan.de/services
From: Olli Attila attiolli@gmail.com Sent: Friday, October 4, 2019 5:54 AM To: Henning Westerholt hw@skalatan.de Cc: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: Re: [SR-Users] Call limit through shared database
Hello Henning,
I tried the dialog profile sharing with dmq&dialog modules and now the syncing works between the two kam nodes. Thank you!
Is there a way to keep the dialog profiles persistent (load from db if kam restarts)? I was thinking a scenario where kam1 has already the call limit maxed out and kam2 suddenly reboots and after reboot, kam2 should be aware of dialogs on kam1 to be able to limit calls again correctly.
Cheers, Olli
Hello Henning,
Ok I think I was wrong when I assumed the mysql would do the dialog profile syncing somehow during kamailio reboot but instead the DMQ is actually doing it like you posted earlier.
I traced with wireshark and noticed that after kam2 rebooted itself and became responsive again, kam1 node informed the kam2 with the active dialog profiles via dmq.
Thank you.
--Olli
pe 4. lokak. 2019 klo 15.33 Henning Westerholt (hw@skalatan.de) kirjoitti:
Hello Olli,
the profile information should be also synchronized with DMQ – but not sure if they are also synchronized during startup. If kam2 reboots it should get the dialog information from kam1 after it has started.
Have you tried if its works already?
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
From: Olli Attila attiolli@gmail.com Sent: Friday, October 4, 2019 5:54 AM To: Henning Westerholt hw@skalatan.de Cc: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Subject: Re: [SR-Users] Call limit through shared database
Hello Henning,
I tried the dialog profile sharing with dmq&dialog modules and now the syncing works between the two kam nodes. Thank you!
Is there a way to keep the dialog profiles persistent (load from db if kam restarts)? I was thinking a scenario where kam1 has already the call limit maxed out and kam2 suddenly reboots and after reboot, kam2 should be aware of dialogs on kam1 to be able to limit calls again correctly.
Cheers,
Olli
-
Giovanni Tommasini - evosip -
Henning Westerholt -
Olli Attila