Differences between CDR record and Total Queue Report

[Juan Herrera]

Hi
I have created a method to extract the information from the CDR socket and read it with an external report program, the data is stored in a database with the same characteristics as the cdr.log file. at this point everything is fine.
The problem occurs when at the end of the day you compare the report generated based on the CDR socket vs the general report of the queues, the totals that are shown do not match.
When this happened I have checked the calls for answers, I have noticed that some workers have all their calls registered in the CDR socket, but other workers do not have the correct total, as shown in the 3cx wallboard.
For this reason I would like to know why the CDR socket is not capable of writing 100% of the data or are there some calls that it does not register? are there any settings to change for this? is it normal to happen?

I will leave two images, one where you see the totals regarding the call queue and another corresponding to the reading that I do from the CDR socket, you see the difference in the totals.

 

[VoIPTools]

First, using the socket connection works great, when it works. But if you have any networking blip, you can lose a call, or worse lose the socket connection entirely (depending on how it is coded). You would need to code a resilient connection. In my opinion, it is far safer to process the CDR files (I recommend one file per call). Then, if your service goes down, no-worries, just process any new files when your service restarts.

Second, I have heard (you will need to verify) that a call transferred from one agent to another allocates all the time to the first agent... something non-obvious like that. I would recommend you turn on writing to files so you can see exactly what 3CX is generating. Your socket connection will get exactly the same information, but it's far easier to diagnose using the files.

Finally, If you do not want to hassle with this yourself, we can parse all the CDR files for you and place the data into a SQL/MySQL database with our 3CX Exporter tool. Exporter can access the CDR files even on cloud hosted 3CX servers running on Linux.

Like your socket connection, Exporter processes the CDR files in real-time.

 

[Juan Herrera]

Hi

I understand the explanation and it has enough logic, I have reviewed my log application and it has not requested a connection at any time, for this I do not want to hold my connection responsible, according to your information that could affect that the CDR numbers are not the same as those of the 3cx wallboard ?

Tanks