V20 U7 Alpha: Major Boosts to 3CX System Management for Admins

Status
Not open for further replies.

N_G

Founder
Joined
Jun 6, 2006
Messages
4,857
Reaction score
9,291

System health monitoring natively within the 3CX platform.​

Update 7 Alpha, coming hot off the heels of the successful Update 6 Final release, delivers several major improvements for system administration. Amazon AWS S3 buckets are now included for remote storage. 3CX System Watcher assists Admins in actively monitoring core 3CX...
Continue reading the Original Blog Post.
 
Last edited by a moderator:
Hi,

Having the option "Audio Quality Metrics", that would be amazing :)
Going to test that for sure.

Paulo
 
Oh my god, what a good gift before summer break !
The new Queue Missed calls / Callback dashboard have now the manual callback checking !

1753887534868.png

Does the manual checking work even if queues don't have "auto callback" enable ?

Thank you,
Best regards.
 
Christmas in July! 3CX Summary/Sentiment, enhanced report filtering, SBC management, and SmsPrefix!!!
 
Hi,
Some news about the per-department contacts, as it was announced months ago ?
Can't see it in the upcoming items from this blog post :)
Thank you !
 
Hi,
Some news about the per-department contacts, as it was announced months ago ?
Can't see it in the upcoming items from this blog post :)
Thank you !
Update 8 coming soon - very good results being tested as we speak so wait abit it coming cool.
 
Awesome update! Installed fine. One thing, with the banner about Remote Storage setup, I have the remote storage fully setup with SMB, but the banner still displays as partial. Is there some other config needed for the partial setup to be satisfied? Thanks again.
 
Christmas in July! 3CX Summary/Sentiment, enhanced report filtering, SBC management, and SmsPrefix!!!
Did you find the SMS prefix thing? I haven't.
 
  • Like
Reactions: GregG_3CX and N_G
Grafana templates looking great! Just imported the PostgreS ones. Thanks.
 
Awesome update! Installed fine. One thing, with the banner about Remote Storage setup, I have the remote storage fully setup with SMB, but the banner still displays as partial. Is there some other config needed for the partial setup to be satisfied? Thanks again.
Nevermind on this. It just wanted me to select the boxes to enable storage for all the folders. Once I did that, the banner went away. Thanks.
 
Updated postgres to latest 17.5-3 and Grafana to latest 12.1.0.0. No issues. Dashboards look good.
 
While the update features are nice. I don't really agree with the big banner notification for remote storage not being configured. A lot of companies have their own backup solutions that are done at the VM level where the backups in 3CX are not really needed. There should be an option to disable this notification.
 
While the update features are nice. I don't really agree with the big banner notification for remote storage not being configured. A lot of companies have their own backup solutions that are done at the VM level where the backups in 3CX are not really needed. There should be an option to disable this notification.
Per the blog it'll be required for 3CX hosting so would make sense to show the warning there, but yes we handle backups also.
 
What an unexpected surprise!
Thank you 3CX Team!
Keep up the good work!
 
Per the blog it'll be required for 3CX hosting so would make sense to show the warning there, but yes we handle backups also.

And perhaps it would be a good time to point out that this is primarily about Remote Storage, not Backup. The intention is (and self hosted can benefit from this too) for the 3CX instance/machine to not be used for long term storage and retrieval of anything - in the end it's not a file or database server. Moving those tasks to external systems lets the PBX do its primary function with far greater efficiency.

Customers and Partners can leverage this new operational concept to optimize how their resources are put to best use.
 
Oh my god, what a good gift before summer break !
The new Queue Missed calls / Callback dashboard have now the manual callback checking !

View attachment 48821

Does the manual checking work even if queues don't have "auto callback" enable ?

Thank you,
Best regards.
Hello again,

Does the manual callback checking require U7 version ?
Because i'm testing with a 3CX U6 and only the automatic callback get register ?
Maybe there is more table/variable that come with the U7 to make this possible ?

1753950906796.png

Thank you,
Best Regards.
 
Hello again,

Does the manual callback checking require U7 version ?
Because i'm testing with a 3CX U6 and only the automatic callback get register ?
Maybe there is more table/variable that come with the U7 to make this possible ?

View attachment 48827

Thank you,
Best Regards.

@KoesioOccitanieTech
Great question!
Yes, this can work with Update 6 as well, since it involves a dashboard-level change.

Here’s how the manual callback logic works:
A call is received by a queue with three agents, but it ends up being missed. For the callback to be properly recognized and tracked, the redial attempt must be made by one of those three original agents in the queue.

We believe this approach is correct because expanding the check to include all users would result in excessively heavy SQL queries. By limiting it to the original queue agents, we significantly improve performance.

Also, there's a high likelihood that the callback will indeed be handled by one of the intended queue agents, so this restriction is both practical and efficient.

--

Thank you for your contributions! Several of your suggestions made it into this release, so great work and please keep them coming!
 
@KoesioOccitanieTech
Great question!
Yes, this can work with Update 6 as well, since it involves a dashboard-level change.

Here’s how the manual callback logic works:
A call is received by a queue with three agents, but it ends up being missed. For the callback to be properly recognized and tracked, the redial attempt must be made by one of those three original agents in the queue.

We believe this approach is correct because expanding the check to include all users would result in excessively heavy SQL queries. By limiting it to the original queue agents, we significantly improve performance.

Also, there's a high likelihood that the callback will indeed be handled by one of the intended queue agents, so this restriction is both practical and efficient.
Hello, thank you for your explanation and that a good approach to restrict to queue agents only.

But it's not working for me, here is the step I did :

- Calling a queue with one agent
- Call ends after 20sec of wait / call abandonned
- The one agent calling back and i let the call last ~30sec
- Force the push of the CDR into database
- Check my grafana

The manual callback doesn't show, I did the same step but with callback enable on queue and it works.

I'm using posgresql database, maybe I did something wrong.

Thank you for your contributions! Several of your suggestions made it into this release, so great work and please keep them coming!
Happy to hear it, thank you for your trust and i will keep trying to give ideas. :p
 
Status
Not open for further replies.

Forum statistics

Threads
111,990
Messages
590,165
Members
164,927
Latest member
tohoken1