3CX Reporting CDR Integration

[MesutOzturk]

I am working on CDR records process. We are trying to charge calls.

Our CDR settings : 3CX CDR service is service / Passive Socket and also we gaved proper ip and port.

Now we behave like client to this socket and getting CDR records. Until here we have no problem.

But we tested transfer calls, by the way we are using desktop phone app of 3CX. For instance, we began to call as internal no 1005 to internal no 1006 then we blind transfer to outgoing number such as 0532XXXXXXX.

Here, there is two conversation, one is between 1005 and 1006 and the other one is between 1006 and 0532XXXXXXX. So we expect two CDR record seperated but we are receiving just one CDR as united.

The Problem is :
The CDR is giving right chain but we don't know duration of call between 1005-1006 or 1006-0532XXXXXXX so we have total duration of call. We need seperated CDR record to charge 1005 and 1006.

Same situation is exist on normal transfer senario.

Thanks in advance for responses.
Best Regards.

 

[Cjay]

As you have noted, you only get one CDR produced per call and this only has 3 timestamps: Call start, Answer & End times. There's currently no way of deducing from the CDR the timing of the various events within the call chain.

 

[VoIPTools]

I concur with @Cjay. But let me point out an additional concern. Relying on a IP socket connection is a recipe for failure. As with all software and networking solutions, there will be times when the socket connection is down either for software updates, failures, etc. When your socket is down, you lose the call data and there is no way to catch up. A better approach is to use physical CDR files. Then, if your CDR service goes down for any reason, no problem because you can simply process any files not previously handled. But to Cjay's point, regardless of how many places a call is transferred, there will only be one CDR file that summarizes the cradle-to-grave steps of the call. There is a "chain" field that lists everyone that touched the call, but no individual leg information. By the way, our 3CX Exporter tool can automatically, in real-time, process the CDR files.

You could run 3CX call reports and export the data as a CSV, but that is a purely manual process.

Another option would be to use our REST API / Exporter to replicate all the 3CX data (every 60 seconds) to SQL / MySQL and build whatever reports you need using the reporting tool you prefer (Power Bi, Crystal Reports, Excel, etc.)