V20 U6 Final - All Improved Reporting

[edossantos_sipcaller]

Hi,
after update our CRM integration with Freshdesk not works. And in log informations is missing.
Can you help me?

Please post a new thread here, explaining the issue in detail:
https://www.3cx.com/community/forums/freshdesk/

 

[ajsmith227abts]

Is there something I need to do to enable inbound/outbound call reports? They both show no data. General call log shows all calls.

 

[Alejandro_3CX]

Is there something I need to do to enable inbound/outbound call reports? They both show no data. General call log shows all calls.

The new reports presented in U6 will use new call logs. For legacy call logs before the update this will not apply.

 

[rlg]

And is there any way to purge legacy calls / tables ?
So that we have instances with only the big new table fed ?
@nikolascx perhaps a question for you, as per your last topics / videos on this major change ?
Thank you very much !

 

[ITSmartwork]

Dears,

i have an on premise installation. With the last update(Version 20.0 Update 6 (Build 724 Release)), i see an issue with the call log. Basically on the call ID i see a GUID value instead of the number.
This is a major issue as i need to generate the report for my customer and cannot send this kind of useless data.

Previous one did not had this issue: Version 20.0 Update 5 (Build 551 Release)

Thank you

 

[KyriacosS_3CX]

Dear @ITSmartwork ,

The updated Call Report allows you to have a much improved view of how a call was processed, and a GUID is the Call ID now, in place of a number. Also individual Inbound and Outbound reports give a more simplified view if needed.

The Call ID is simply an ID field - nothing report wise should depend on its type.

Best,
KS.

 

[ITSmartwork]

oh i see. It's a feature and not a bug

thanks!

 

[diplodock]

Question about the report "Queue Missed Calls & Callback Efficiency"
A call to a queue was missed, then the operator made a call to this phone number. But information about the callback made did not appear. Maybe there are some subtleties in the operation of this report. Or does it only show callbacks from the queue with the "allow callback" option enabled?

 

[KyriacosS_3CX]

Or does it only show callbacks from the queue with the "allow callback" option enabled?

Corect. Otherwise how would it know it's a callback and not just a general outgoing call?

 

[diplodock]

A call was missed from this number.Callback after the missed call. By the phone number the call is directed to. We need to understand whether the operator called the missed number. How?

 

[KyriacosS_3CX]

Making use of the build in callback feature is the best option. You can also always correlate outgoing calls report with the dropped calls report, but there is no build in tool that does that correlation.

 

[diplodock]

It's strange, we really need this report to monitor the work of operators.
But there is a report "Missed Calls & Redialed Callbacks@. Which contains information on callback calls. But not to Queue.

 

[diplodock]

Is it possible to have the same report for Queue?

 

[SteveITS]

is there any way to purge legacy calls / tables

From the Dashboard, or System > Maintenance.

 

[SteveBohn]

Have a client on V20 U6 (Build 724) that reported that the intercom function wasn't working anymore. Further digging lead me to find that this appears to only affect the department administrator and system administrator roles. Under both of those roles, even though the "call operations" permissions are set properly, the intercom function does not work properly. It will simply ring the extension rather than intercom. As soon as I switch the role to receptionist, manager, owner or system owner, it works perfectly. Surely this is a bug and not by design? Anyone else experiencing this?

 

[Alejandro_3CX]

Have a client on V20 U6 (Build 724) that reported that the intercom function wasn't working anymore. Further digging lead me to find that this appears to only affect the department administrator and system administrator roles. Under both of those roles, even though the "call operations" permissions are set properly, the intercom function does not work properly. It will simply ring the extension rather than intercom. As soon as I switch the role to receptionist, manager, owner or system owner, it works perfectly. Surely this is a bug and not by design? Anyone else experiencing this?

Hi @SteveBohn intercom can be used only with these roles: Receptionist, Manager, Owner and System Owner.



If the ext user doesn't have any of those roles, then he can't perform that call action.

So it is not a bug, it has been like that since v20 was launched. Please check this guide for the access roles.

 

[nikolascx]

Is it possible to have the same report for Queue?

Dear @diplodock Great question.
You are correct to wonder. And yes, you are perfectly right.
We made it for Queue callbacks only for now as a first step.
But we are expanding the query to also catch calls which were made outside of the queue callback functionality.

What datasource are you using? We can exchange SQL or dashboards so you can have it working before we release. How does that sound?

Thanks for reporting.

 

[Toto_Ad]

Hello,

If I understand correctly, with this new version of 3CX, the call and queue data are no longer stored in the local PostgreSQL database on the server. Instead, to continue using SQL-based reporting tools like Power BI, we need to configure the "Data Connectors" feature to export the data to an external database.

Could you please confirm if this is the correct understanding?

Best regards,

Thomas

 

[KyriacosS_3CX]

Hello,

If I understand correctly, with this new version of 3CX, the call and queue data are no longer stored in the local PostgreSQL database on the server. Instead, to continue using SQL-based reporting tools like Power BI, we need to configure the "Data Connectors" feature to export the data to an external database.

Could you please confirm if this is the correct understanding?

Best regards,

Thomas

Hello,

With v20 U6 the data is still stored locally on a PostgreSQL database.

What changes is in brief:

• The local tables have changed, making for more efficient storage and enabling additional options listed below.
• New build in reports, improved existing ones.
• Export to external data storage engines - BigQuery or external PostgreSQL for now.
• Ability to use tools like PowerBI/Grafana to expand on reporting outside the 3CX system.
• Ability to trim locally stored data and still use external for long term, meaning the local database remains small and more efficient for larger/beasier systems.

Hope this provides a clearer insight.

Best,
KS.

 

[diplodock]

Dear @diplodock Great question.
You are correct to wonder. And yes, you are perfectly right.
We made it for Queue callbacks only for now as a first step.
But we are expanding the query to also catch calls which were made outside of the queue callback functionality.

What datasource are you using? We can exchange SQL or dashboards so you can have it working before we release. How does that sound?

Thanks for reporting.

Thank you so much! I use postgreSQL+grafana for reporting. I would be very happy to try this feature. How can I do this?