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 <attio...@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 >
_______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
