Hi Benoît, Having gone down this road myself, I would corroborate what Henning has to say.
Getting large amounts of dialog info in bulk from the JSONRPCS API isn't a particularly good avenue, even if you can make it work with the various buffer sizes. I would also be concerned about any big locks required when iterating over the dialog structures as a whole, since they are stored in shared memory. In many cases, just because something is technically possible doesn't mean you should do it. It seems to me that `dlg.list` may be one of those RPC commands that's best suited to troubleshooting or debugging, rather than regular operational usage. (To be fair, I don't know the locking approach when reading the entire structure, and I imagine some work has gone into optimising it.) What DMQ sync issues with DB storage have you found? I haven't tried it myself, but I would imagine a promising approach would be to have a DMQ peer node whose sole purpose is to sync dialogs to a DB. Have you tried that? Has it not worked out? -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800 __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
