Re: [SR-Users] jsonrpcs - safest way to get data

Hello, Your requirement to frequently dump millions of user location entries on a loaded production system sounds a bit odd to me. Maybe you can elaborate a bit on your requirements. If you have the requirement to access this data frequently, maybe getting it from the database directly is the better idea. If you want to get it from kamailio, choose a module that provides the option to configure the number of children (e.g. like dgram_workers in jsonrpcs) and set it to a sufficient number. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users &lt;sr-users-bounces(a)lists.kamailio.org&gt; On Behalf Of Ilie Soltanici Sent: Tuesday, October 6, 2020 12:29 AM To: Kamailio (SER) - Users Mailing List &lt;sr-users(a)lists.kamailio.org&gt; Subject: [SR-Users] jsonrpcs - safest way to get data Hello, I'm trying to periodically get all registered contacts from the Kamailio memory in the json format. JSONRPCS module have 3 different types of transport to get this data. I just wonder what will be the safest transport for the Kamailio to get all this data? Because all this data it's not so important, I want to gather it without affecting the main process or with the minimal effect on the Kamailio SIP Processing module. 1. The HTTP transport - very useful, working async, but because it depends on the xhttp module - which works synchronously I'm afraid that for big data with contacts this type of transport can affect the kamailio performance. 2. FIFO - this transport also is very fast, working locally - but it's synchronous, I'm not sure how it will affect Kamailio SIP Processing when the local database will have few millions of users registered. 3. DGRAM - also seems to be very fast, working locally or remotely through the UDP protocol, but again it's synchronous and I'm not sure that this transport is returning any output for the request, I tried - but didn't get back anything, while for changing something it worked fine. Maybe it was a misconfiguration in my config file. What would be your recommendation for this case? Thank you.