CDR missing records

[Paul Otter]

PBX
Professional Perpetual 16.0.504
OS Windows 2016 Server (VM)

We have a logging server that collects CDR output from 3cx, and records the results in our oracle database.
This has worked well for the last few years, but we have recently noticed that not all calls are being recorded.

The logging server is a custom C# application on a different machine.
It uses system.net.sockets and has been thoroughly tested with multiple simultaneous connections.

Has anyone else had this issue ?
Should I expect to find any PBX logging of a failed CDR output ?

Any suggestions on how to proceed ?

Thank you

Potski

 

[JohnS_3CX]

Hi @Paul Otter

Something to note, if the connection "breaks" at certain time intervals, any calls going through at that time will not reach your logging server and they will effectively be "lost" (even though they still exist in the 3CX logs). I would start my investigation by checking the connection or temporarily switching to file-based CDR rather than socket-based (to confirm the calls are logged by 3CX and then focus at troubleshooting your net/sockets)

 

[VoIPTools]

As JohnS_3CX suggests, I would convert to the file-based CDR approach. Countless times in the forums I have suggested that people NOT use the sockets approach simply because if anything happens to the socket, the data will be lost forever. The sockets approach was designed specifically for hotel management systems that only support a socket connection.

With the file-based approach if your service goes down, or there is a brief network blip, etc. it has no impact on your process. When the service comes back up, or the network is restored, you simply process the files and catch up. There will never be any data loss. And frankly, processing text files is far simpler than building a resilient socket connection.

Finally, one last bit of advice, I always configure 3CX to create an individual file for each call (rather than one file containing multiple calls). I also ensure ALL the fields are included, not just the default fields.

 

[Paul Otter]

Thank you both for your responses.
You've given a good explanation of the cause of the issue,and offered a good solution.

Much appreciated.

Potski