V20 Update 8 Final: Leaping Forward with Agentic AI

[N_G]

thats not the queue panel though

 

[patrickb_de]

thats not the queue panel though

I know, but that’s the "missed calls in queue" list, and that’s exactly what most of my customers are missing in the Android/iOS app - which is why i raised the question last night The panel itself isn’t really that important; the call overview is what really matters.

The queue panel works fine in the Android PWA, though - that’s true.

 

[N_G]

missed calls are shown in Recents on the app, not sure what the issue is.

 

[Evolute IT]

missed calls are shown in Recents on the app, not sure what the issue is.

Yes, but the app doesn't show missed queue calls (abandoned), only answered ones. It does show ring group calls tho, both answered and missed.

 

[N_G]

ah yes good point will discuss

 

[patrickb_de]

Yes, but the app doesn't show missed queue calls (abandoned), only answered ones. It does show ring group calls tho, both answered and missed.

For ringgroups, missed calls are only visible if you personally receive the call, and the extension must be available and signaling at that time. Otherwise, only direct personal calls appear in the missed calls list.

You can easily test this yourself: create a ringgroup, add yourself as an "agent", assign a DID to the ringgroup, and make two test calls. First, make a call while you are available with the assigned "agent" and then make another call while the "agents" status is set to DND or the extension is offline. You will only see the first missed call in your call history.

I’ve just tested this again a few moments ago, and the result is the same.

However, a list of "missed queue calls" (abandoned) (and missed ringgroup calls) in the ios and android app would be a huge milestone.

 

[AlexanderJHanna]

Yes, but the app doesn't show missed queue calls (abandoned), only answered ones. It does show ring group calls tho, both answered and missed.

Are you sure about this? Because I see the same Abandoned calls in the WebClient and the Mobile PWA App. Unless I am missing something. Are you added as a Supervisor?

 

[Evolute IT]

Are you sure about this? Because I see the same Abandoned calls in the WebClient and the Mobile PWA App. Unless I am missing something. Are you added as a Supervisor?

We're talking about the mobile native iOS app.

Not the Webclient or PWA. Mobile or desktop doesn't matter there as it is web-based and responsive.

 

[AlexanderJHanna]

We're talking about the mobile native iOS app.

Not the Webclient or PWA. Mobile or desktop doesn't matter there as it is web-based and responsive.

Noted.

 

[Tony Cave]

What a fantastic update!

Thanks for the heads up! I've had a new Yealink T85W waiting in box to test this. Really great news. Not only do we save a bit on provisioning costs, it also simplifies the process with fewer touches and we have as much time as we need to configure the extensions and assign phones.

Are the firmware updates scheduled for a particular time of day? My concern would be that they update during work hours?

 

[SteveITS]

I understood it to be for new phones as they are added..."Update automatically new phones to 3CX supported firmware (BETA)"

 

[Tony Cave]

I understood it to be for new phones as they are added..."Update automatically new phones to 3CX supported firmware (BETA)"

Ahhh, yes that makes sense.. Hopefully it can be extended to the already installed phones at some point with the option to set 'Update Time' that would be really useful...

 

[ivank]

I understood it to be for new phones as they are added..."Update automatically new phones to 3CX supported firmware (BETA)"

That's correct assumption

 

[patrickb_de]

@Charles_3CX

I have a question regarding the Microsoft 365 integration. For some time now, the synchronization with the phone directory and users has been "key-sensitive". Since Microsoft often delivers contact data containing spaces or special characters (including extension or mobile number fields), this occasionally causes issues.

Would it be possible to include a normalization or replace function in a future update that automatically removes special characters and spaces to prevent these problems?

When the M365 sync imports a contact or mobile number in formats such as +1 (1234) 12345 or +1 1234-12345, the PBX does not correctly match or assign the number. It would be very helpful if the system could automatically clean and normalize the numbers so that, regardless of how they are stored in the tenant, they are consistently converted and used in 3CX format (for example: +1123412345).

Additionally, if a user has an incorrectly formatted mobile number but has mobile phone signaling enabled, this can lead to call failures or dropped calls.

Thank's

 

[KyriacosS_3CX]

Hi @patrickb_de, this is probably something for the ideas forums rather than just as a comment here, where it will probably be lost in the noise.

 

[patrickb_de]

Hi @patrickb_de, this is probably something for the ideas forums rather than just as a comment here, where it will probably be lost in the noise.

Just added it to the ideas section: Thread 'Number Normalization for Microsoft 365 Synchronization' https://www.3cx.com/community/threads/number-normalization-for-microsoft-365-synchronization.136650/

 

[ArneDery]

We've been testing with the O365 departments sync. We've always synced it using selected users. However having the option user groups brings a big addition to the game.

We've noticed that the users are correctly created when we use the feature, however the SSO functionality is not working when synced by department. It does not allow me to login using SSO. It redirects me to the login screen after trying.

Currently only way arround is to use selected users again. Which obsoletes the user group feature. Any ideas?

 

[KyriacosS_3CX]

@ArneDery , perhaps a ticket with support to troubleshoot this one.

 

[ArneDery]

@ArneDery , perhaps a ticket with support to troubleshoot this one.

Created, thx

 

[patrickb_de]

ah yes good point will discuss

Hi,

I'd like to come back to the abandoned queue call visibility in the iOS and Android apps because one of my customers is facing an issue after updating to Samsung's One UI 8.5.

The previous workaround of writing missed queue calls into the phone's native call history no longer works for these users. It seems that Google/Samsung no longer grants the WRITE_CALL_LOG permission to third-party apps and Samsung appears to enforce this restriction much more strictly in One UI 8.5.

As a result, my customer is now missing a lot of abandoned queue calls because they no longer appear in the phone's call history. This means users cannot easily see or return these missed calls.

Could you please revisit the possibility of displaying abandoned queue calls directly within the iOS and especially the Android app under the "Missed Calls" section? I believe this would be a very useful feature. There are likely many Samsung Android users who will encounter the same issue once they update to One UI 8.5 or replace their phones.

The suggested workaround is to set the app as the default phone app. I haven't tested this yet, but even if it works, it isn't a practical solution for my customer (or likely for many others) because they frequently switch between the android dialer and the 3CX app.

I believe providing native support for abandoned queue calls within the app would be the best long-term solution and would avoid compatibility issues with newer Android versions. It would also provide a consistent user experience across all Android devices, regardless of manufacturer-specific restrictions.

I hope you can take another look at this feature request, as I believe it will become increasingly important with future Android and (in this special case) Samsung updates.

Thanks

@AvraamM_3CX @MarcosV_3CX @KyriacosS_3CX

PS: Older versions of One UI work fine with both the Beta (20.7.0.5) and Stable (20.6.0.20) versions of the Android app. After updating the same device to One UI 8.5, the feature no longer works with either the Beta or the Stable version.