JEDWare has no limit on how many calls a report can count. The Call log table stops at 25,000 rows, but every call is still in the totals and the CSV export. The practical limits are the resources of your 3CX server, which delivers the call data, and of the PC that builds the report in the browser. A report over 200,000 calls works, but it takes time.
What happens when you run a report
- Your browser sends the search to the JEDWare integration on your 3CX server: period, agents or queues, call types, weekdays, exclusions and the interval (per day, per hour, down to one minute).
- The integration reads the calls from the 3CX database and sends them to your browser. On a standard 3CX Debian VM with 6 CPUs and 6 GB of memory, six months of agent calls (265,000 calls) took about 20 seconds.
- Your browser calculates the totals, then splits the calls into the intervals you chose. This part runs on your PC, and the time depends on the number of calls and the interval: per hour for six months is a lot of buckets.
The Call log table on screen prints the first 25,000 calls and says so above the table. The totals, the charts and the CSV export always contain every call.
Tips
- 0 calls with the message “3CX Postgre SQL Error: Timeout during reading attempt”: the 3CX server ran out of resources while reading the calls. Shorten the period, for example to 15 days, and run the report again. If it happens often, give the 3CX server more memory or CPU; see JEDWare requirements.
- Use the interval that fits the question. Per day for a month is fast; per minute for a year is not.
- For a report you need every day, week or month, let a scheduled report build it at night and email it to you.
- For very large data sets, pull the numbers through the Statistics API instead of the browser.