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(a)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(a)gmail.com>
Sent: Friday, October 4, 2019 5:54 AM
To: Henning Westerholt <hw(a)skalatan.de>
Cc: Kamailio (SER) - Users Mailing List <sr-users(a)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
--
"Logic is the art of going wrong with confidence."