V20 Update 6 RC3

[nikolascx]

New Grafana Dashboards & Reports.​

Update 6 Release Candidate 3 is now live and includes 7 new Grafana dashboards as well as 3 bug fixes to existing dashboards. RC3 builds on feedback from the ALPHA, BETA, RC1 & RC2 releases and marks the last step before the final release. We envision that this release candidate will be the releas...

Continue reading the Original Blog Post.

 

[UCMUserAZ]

Installed. No seen issues. Thanks.

 

[UCMUserAZ]

Great new dashboards for Postgres! All came over and imported fine. Question, I do not have a public.cdrbilling table in PostGres for a few of the dashboards. Is there a way to get that enabled or created on the 3cx side? Thanks again!

 

[rlg]

• Removed SNOM D812 & D815 as Router Capable due to hardware restrictions on these models (they will work in Local LAN & Stun).

Could you tell us more about the hardware limitation please ?
Thank you !

 

[nikolascx]

Great new dashboards for Postgres! All came over and imported fine. Question, I do not have a public.cdrbilling table in PostGres for a few of the dashboards. Is there a way to get that enabled or created on the 3cx side? Thanks again!

Thanks for the feedback.
You don't see it, but it is there. Inside Settings > Variables
This is where Grafana stores Variables
db_cdroutput_path

On PostgreSQL, we do not ask - we just set it to public.cdroutput because thats where the Offloader will put the data.

Hope this answers your question

 

[nikolascx]

Could you tell us more about the hardware limitation please ?
Thank you !

HI @rlg
Best ask Snom on this one. I am also a little surprised.. We really do not have much details to share.

 

[KoesioOccitanieTech]

I'm looking to the new "10 - Missed Calls & Redialed Callbacks" dashboard, and it's for redial checking for extension; but can we imagine the same thing for missing call of a queue ? Is it possible ?

Thank you.

 

[Sajjad.Khurshid]

@nikolascx

Thanks for this update.


We currently have a Pro 3CX 8 SC license that we're using for testing purposes and a Pro 64 SC license in production. Before deploying any updates, we need to test them on the 8 SC environment.


However, I'm unable to test the Grafana integration on the 8 SC license. Could you please assist with this? I need guidance on how we can test the update before pushing it to production.

 

[nikolascx]

I'm looking to the new "10 - Missed Calls & Redialed Callbacks" dashboard, and it's for redial checking for extension; but can we imagine the same thing for missing call of a queue ? Is it possible ?

Thank you.

@KoesioOccitanieTech
Definitely. We will add this in a dedicated Queue viz because it is very important.
The one dashboard you see for Queues, that will not be one for long.. We will start to fork out..

 

[KoesioOccitanieTech]

@KoesioOccitanieTech
Definitely. We will add this in a dedicated Queue viz because it is very important.
The one dashboard you see for Queues, that will not be one for long.. We will start to fork out..

Really cool to know that there will be more and more template in the future. I'm really not into SQL and having these template ready to go is a really nice.

Typicaly, the redial dashboard for queues will help me to switch a big customer to V20

 

[nikolascx]

@nikolascx

Thanks for this update.


We currently have a Pro 3CX 8 SC license that we're using for testing purposes and a Pro 64 SC license in production. Before deploying any updates, we need to test them on the 8 SC environment.


However, I'm unable to test the Grafana integration on the 8 SC license. Could you please assist with this? I need guidance on how we can test the update before pushing it to production.

Hi @Sajjad.Khurshid

Thanks for sharing your concern regarding testing the Grafana integration before pushing updates to your production system.

I completely understand the desire to thoroughly test all changes in a non-production environment first — that’s a best practice in most IT scenarios. However, in this particular case, I’d like to provide some clarification and reassurance that might help guide your decision-making.

The Grafana integration is only available starting from the 16 SC Pro license tier and above, which means your 8 SC license unfortunately does not support this feature. That’s by design and not a limitation or oversight.

More importantly, the Grafana integration is an observability add-on, not a core telephony or PBX feature. It does not impact core call services, SIP trunks, call flows, provisioning, or security. Think of it like the indicator lights on your car — helpful for insight, but not critical to the car’s ability to drive. Even if the integration were to fail (which is highly unlikely in a standard deployment), your production system will continue to function flawlessly.

Testing everything on the 8 SC environment might seem logical, but in this case, it’s not technically viable since the integration doesn’t exist there.

Hope this helps.

 

[UCMUserAZ]

Thanks for the feedback.
You don't see it, but it is there. Inside Settings > Variables
This is where Grafana stores Variables
db_cdroutput_path

On PostgreSQL, we do not ask - we just set it to public.cdroutput because thats where the Offloader will put the data.

Hope this answers your question

For some of the dashboards the variables are public.cdroutput and public.cdrbilling. I see the public.cdroutput in Postgres that came over from 3cx, but not the public.cdrbilling. Dashboard says public.cdrbilling does not exist. Is there a way to get that cdrbilling activated so it comes over from 3cx? Thanks in advance.

 

[nikolascx]

For some of the dashboards the variables are public.cdroutput and public.cdrbilling. I see the public.cdroutput in Postgres that came over from 3cx, but not the public.cdrbilling. Dashboard says public.cdrbilling does not exist. Is there a way to get that cdrbilling activated so it comes over from 3cx? Thanks in advance.

Hi @UCMUserAZ
Great question — and thank you for digging into the Grafana dashboards and the underlying data.

You're absolutely right: the public.cdroutput table appears as expected, but public.cdrbilling may be missing in some cases. The reason is simple — your PBX hasn’t generated any billable outbound calls yet, so the cdrbilling table hasn’t been created automatically.

Currently, the table is only created on-demand, meaning it appears only after the PBX generates outbound calls that are considered billable (e.g., calls that leave the system via a trunk with associated costs). If your environment hasn't made such calls yet, the table simply won't exist.

That said, we recognize this can lead to confusion — especially when pre-built dashboards reference a table that isn't present. To improve clarity and maintain schema consistency, our next update will proactively create the cdrbilling table (even if empty) during initialization, regardless of whether billable calls have been made.

If you’d like to test the table right away, try placing an outbound call through a trunk that incurs a charge (even if it's minimal), and the table should appear automatically after processing.

 

[UCMUserAZ]

Hi @UCMUserAZ
Great question — and thank you for digging into the Grafana dashboards and the underlying data.

You're absolutely right: the public.cdroutput table appears as expected, but public.cdrbilling may be missing in some cases. The reason is simple — your PBX hasn’t generated any billable outbound calls yet, so the cdrbilling table hasn’t been created automatically.

Currently, the table is only created on-demand, meaning it appears only after the PBX generates outbound calls that are considered billable (e.g., calls that leave the system via a trunk with associated costs). If your environment hasn't made such calls yet, the table simply won't exist.

That said, we recognize this can lead to confusion — especially when pre-built dashboards reference a table that isn't present. To improve clarity and maintain schema consistency, our next update will proactively create the cdrbilling table (even if empty) during initialization, regardless of whether billable calls have been made.

If you’d like to test the table right away, try placing an outbound call through a trunk that incurs a charge (even if it's minimal), and the table should appear automatically after processing.

Got it. Sounds great. Makes sense. Thanks!

 

[UCMUserAZ]

Hi @UCMUserAZ
Great question — and thank you for digging into the Grafana dashboards and the underlying data.

You're absolutely right: the public.cdroutput table appears as expected, but public.cdrbilling may be missing in some cases. The reason is simple — your PBX hasn’t generated any billable outbound calls yet, so the cdrbilling table hasn’t been created automatically.

Currently, the table is only created on-demand, meaning it appears only after the PBX generates outbound calls that are considered billable (e.g., calls that leave the system via a trunk with associated costs). If your environment hasn't made such calls yet, the table simply won't exist.

That said, we recognize this can lead to confusion — especially when pre-built dashboards reference a table that isn't present. To improve clarity and maintain schema consistency, our next update will proactively create the cdrbilling table (even if empty) during initialization, regardless of whether billable calls have been made.

If you’d like to test the table right away, try placing an outbound call through a trunk that incurs a charge (even if it's minimal), and the table should appear automatically after processing.

That worked. I see it now once placing an outbound call. Thanks!

 

[nbalmadier]

Hi @nikolascx

I'm trying to get the update on my local server on a 48 SC license but my server doesn't see updates it still on version 20.0 update 5 build 384 Alpha

Is there a specific way to get the update to the version 20.0 update 6 RC3 ?

Thanks in advance for your tips

​

 

[ybello]

@nikolascx thanks for the tip on the billing table, looking forward to the update.

Any chance of Extension/Agent login history being populated on another table? We would like to build a dashboard for that too that tracks Agent Occupancy during a shift period - This is a critical Call Centre Metric for quite a number of organisations.

 

[ybello]

@nikolascx thanks for the tip on the billing table, looking forward to the update.

Any chance of Extension/Agent login history being populated on another table? We would like to build a dashboard for that too that tracks Agent Occupancy during a shift period - This is a critical Call Centre Metric for quite a number of organisations.

By the way, we have installed and implemented the Grafana templates for PostgreSQL - No issues at all, pretty cool Dashboards. Thank you.

 

[UCMUserAZ]

We also upgraded our Grafana to latest 12.0.2 and Postgres to 17.5-1. No issues with the dashboards. Thanks.

 

[K_SAK]

Hi @nikolascx

I'm trying to get the update on my local server on a 48 SC license but my server doesn't see updates it still on version 20.0 update 5 build 384 Alpha

Is there a specific way to get the update to the version 20.0 update 6 RC3 ?

Thanks in advance for your tips

​

If you go to updates section it does not show anything after 5 Alpha, even if you do check for updates? Is your server able to reach the internet? Firewall check is green?