CDR 2.0 - Brings Better Reporting

[nikolascx]

Redesigned CDR logging brings more powerful reporting.​

The CDR system has been rewritten to improve data handling and support larger deployments. The new design simplifies the internal table structure, reduces database load and allows direct integration with external storage and analytics tools. It provides a foundation for man...

Continue reading the Original Blog Post.

 

[tronic]

Question regarding the CDR offload. Can this be over the internet? Like, is the data encrypted?
For example, if the server was in AWS Lightsail, can you still offload this to say GCP (BigQuery) or to an onsite database?

 

[KoesioOccitanieTech]

Hello,

This news confirme the final release in few days ?

 

[N_G]

Very Soon hopefully

 

[Alphabetic]

Whats the future looking like with being able to utilise other platforms? Where I really need this, my customer is heavily invested in Microsoft 365. Is there a way (or going to be) we can Offload to a 365 service to then be able to use PowerBI? I can sit and wait for this if it's on the road map otherwise do I get PostGres on a VM and do it this way? Or something like Azure database for Postgres?

 

[N_G]

The power bi is separate from the database that you will use. We will certainly make some templates for power bi as well. So Google or postgres needs to be used and then you can use grafana and later power bi. Actually with some powerbi knowledge you could even do it now but we're going to be doing it. We also use power bi our selves...

We will also do mysql maybe even SQL server.. just need a little bit more time

 

[Alphabetic]

The power bi is separate from the database that you will use. We will certainly make some templates for power bi as well. So Google or postgres needs to be used and then you can use grafana and later power bi. Actually with some powerbi knowledge you could even do it now but we're going to be doing it. We also use power bi our selves...

We will also do mysql maybe even SQL server.. just need a little bit more time

Great news, cant wait

 

[RonaldVanhove]

Hello,

Looking forward to the new reporting.
But my question is:
Are the current CDR-file and cl_tables still being filled with data when I upgrade to "update 6" (we're still at update 4).
Or is it a hard transition to CDR2.0.

Reason:
We import all the data in our own mysql-database and expand it heavily with our own crm-data, to let it end up in one big table.
We use Apache superset for visualizing the data.

 

[Marco pbx]

Is there any template for power BI or as just SQL for custom reports?
3CX creates the table itself and there are many columns in the created table.
it seems hard to create custom reports , views from this table for beginners.

CREATE TABLE information_schema.cdroutput (
cdr_id uuid NOT NULL,
call_history_id uuid NULL,
source_participant_id uuid NULL,
source_entity_type varchar NULL,
source_dn_number varchar NULL,
source_dn_type varchar NULL,
source_dn_name varchar NULL,
source_participant_name varchar NULL,
source_participant_phone_number varchar NULL,
source_participant_trunk_did varchar NULL,
source_participant_is_incoming bool NULL,
source_participant_is_already_connected bool NULL,
source_participant_group_name varchar NULL,
source_participant_billing_suffix varchar NULL,
destination_participant_id uuid NULL,
destination_entity_type varchar NULL,
destination_dn_number varchar NULL,
destination_dn_type varchar NULL,
destination_dn_name varchar NULL,
destination_participant_name varchar NULL,
destination_participant_phone_number varchar NULL,
destination_participant_trunk_did varchar NULL,
destination_participant_is_incoming bool NULL,
destination_participant_is_already_connected bool NULL,
destination_participant_group_name varchar NULL,
destination_participant_billing_suffix varchar NULL,
base_cdr_id uuid NULL,
originating_cdr_id uuid NULL,
creation_method varchar NULL,
creation_forward_reason varchar NULL,
termination_reason varchar NULL,
terminated_by_participant_id uuid NULL,
continued_in_cdr_id uuid NULL,
cdr_started_at timestamptz NULL,
cdr_ended_at timestamptz NULL,
cdr_answered_at timestamptz NULL,
termination_reason_details varchar NULL,
processed bool NULL,
migrated bool NULL,
main_call_history_id uuid NULL,
source_presentation varchar NULL,
offload_id int8 NULL
);

 

[Marco pbx]

I already found the templates here : https://www.3cx.com/docs/aws-postgresql-configuration/
Super easy to import Grafana. Later I will try to use the same queries in power BI too.

 

[RonaldVanhove]

Hello,

Looking forward to the new reporting.
But my question is:
Are the current CDR-file and cl_tables still being filled with data when I upgrade to "update 6" (we're still at update 4).
Or is it a hard transition to CDR2.0.

Reason:
We import all the data in our own mysql-database and expand it heavily with our own crm-data, to let it end up in one big table.
We use Apache superset for visualizing the data.

Will someone answer please?

 

[KyriacosS_3CX]

@RonaldVanhove ,

It's a hard transition.
You can find details of the new data structures here: https://www.3cx.com/docs/call-detail-record-guide/

Best,
Ks.

 

[edossantos_sipcaller]

Will someone answer please?

No, the old cl_tables are not filled anymore. You will need to adjust your processing of this data using the information from the new CDRs table.