Small issues after v20 upgrade

[perfect-touch]

1) Internal calls now only display the first name of the caller - it used to display first name and last name
2) Internal and external calls (ring group) now using the same ring tone - can anyone advise here if the alert-info string has changed?

 

[Mr F]

"I restored to v18u9. Caller display on Yealink devices has returned to displaying first name + last name as before - distinctive ringing for external calls now working again. INVITE to handset via ring group now contains "alert-info=external" for external calls and is absent for internal extensions calling ring group. Definitely seems to be a v20 "issue""

I am also seeing these exact symptoms

 

[perfect-touch]

"I restored to v18u9. Caller display on Yealink devices has returned to displaying first name + last name as before - distinctive ringing for external calls now working again. INVITE to handset via ring group now contains "alert-info=external" for external calls and is absent for internal extensions calling ring group. Definitely seems to be a v20 "issue""

I am also seeing these exact symptoms

I'm so glad someone agrees - the only reply I have had from 3cx staff is that distinctive ringing has never been supported for ring groups and v20 now supports it for queues only I *know* I'm not imagining the dropped alert-info in v20 - I had enough damn complaints about it lol

 

[Mr F]

I restored to v18u9. Caller display on Yealink devices has returned to displaying first name + last name as before - distinctive ringing for external calls now working again. INVITE to handset via ring group now contains "alert-info=external" for external calls and is absent for internal extensions calling ring group. Definitely seems to be a v20 "issue"

I'm so glad someone agrees - the only reply I have had from 3cx staff is that distinctive ringing has never been supported for ring groups and v20 now supports it for queues only I *know* I'm not imagining the dropped alert-info in v20 - I had enough damn complaints about it lol

The first complaint i walked into this morning was "external calls ring like internal calls now" and then another complaint i immediately received was that Office opening hours has been ignored .... and the one was that made me take a deep sigh and revert back was the google speech to text api isn't working.... that was enough to ruin my "last day at work feeling" and revert back.

 

[perfect-touch]

The first complaint i walked into this morning was "external calls ring like internal calls now" and then another complaint i immediately received was that Office opening hours has been ignored .... and the one was that made me take a deep sigh and revert back was the google speech to text api isn't working.... that was enough to ruin my "last day at work feeling" and revert back.

In fairness, v20 not ready for production use but I'm surprised by the number of changes to previous functionality that either aren't being addressed or won't be addressed until update 2 - even for a beta, v20 feels surprisingly immature. I *love* some of the new touches - but the loss of complex inbound routes, CID routing, alert-info on inbound calls etc I must admit that now I've seen the change to call queues that "allow multiple calls", I'm quite disappointed there too... I have to use a different product for queue handling and trunk to a DID for a 3CX ring group to get the desired functionality.

 

[Reinaldo Rolim]

I upgraded a 3CX server (onpremise) at Amazon AWS from version 18 to 20 and I can no longer provision remote extensions (Android/iOS) using the QR Code.

I configured Split DNS on AWS Route 53, with a public zone and a private zone associated with my VPC, resolving both IPs (public and private) to the same FQDN name.

On the EC2 firewall, I configured all the necessary ports, including TCP/UDP port 5090, pointing to 3CX and it didn't work.

When trying to scan the QR Code on Android/iOS devices using mobile data or WiFi, I receive the following error message: QR Provisioning Failed (image).

Any suggestions?

 

[SweetAction]

I upgraded a 3CX server (onpremise) at Amazon AWS from version 18 to 20 and I can no longer provision remote extensions (Android/iOS) using the QR Code.

I configured Split DNS on AWS Route 53, with a public zone and a private zone associated with my VPC, resolving both IPs (public and private) to the same FQDN name.

On the EC2 firewall, I configured all the necessary ports, including TCP/UDP port 5090, pointing to 3CX and it didn't work.

When trying to scan the QR Code on Android/iOS devices using mobile data or WiFi, I receive the following error message: QR Provisioning Failed (image).

Any suggestions?

scan the QR code with a regular qr code reader on your phone. There will be a URL in the scanned data.
Try to load that URL in a web browser of the affected device - what happens?

Resolve any errors preventing it from loading correctly (you should be able to see config details specific to your setup) and you will be in business.

 

[N_G]

The first complaint i walked into this morning was "external calls ring like internal calls now" and then another complaint i immediately received was that Office opening hours has been ignored .... and the one was that made me take a deep sigh and revert back was the google speech to text api isn't working.... that was enough to ruin my "last day at work feeling" and revert back.

The office hours works perfectly but in v20 you have to make some changes - so please review the docs and other questions or wait for the training we are creating for early January

 

[Reinaldo Rolim]

scan the QR code with a regular qr code reader on your phone. There will be a URL in the scanned data.
Try to load that URL in a web browser of the affected device - what happens?

Resolve any errors preventing it from loading correctly (you should be able to see config details specific to your setup) and you will be in business.

Yes, I checked the QR Code and the FQDN URL is correct. I scanned the ports by public FQDN and 443, 5060, and 5090 are responding correctly

Below is a printout of the DNS resolution on the 3cx server and a QR Code test extension that I created to share here on the Forum so we can try to understand what is happening.

The post has been edited by a moderator. Please do not expose personal information, QR codes, FQDNs etc. The second screenshot has been removed.

 

[SweetAction]

Yes, I checked the QR Code and the FQDN URL is correct. I scanned the ports by public FQDN and 443, 5060, and 5090 are responding correctly

Below is a printout of the DNS resolution on the 3cx server and a QR Code test extension that I created to share here on the Forum so we can try to understand what is happening.

The post has been edited by a moderator. Please do not expose personal information, QR codes, FQDNs etc. The second screenshot has been removed.

And when you load the URL in a webbrowser what happens?

 

[Reinaldo Rolim]

And when you load the URL in a webbrowser what happens?

When I paste the QR Code URL into the browser, it downloads the extension provisioning file.

My environment is Debian 12 on Amazon AWS and I am using Let's Encrypt. I tested my FQDN certificate on SSL Labs and it appears with an A grade.

I have been unable to activate new extensions on Android/iOS smartphones since December 29t

 

[SweetAction]

When I paste the QR Code URL into the browser, it downloads the extension provisioning file.

My environment is Debian 12 on Amazon AWS and I am using Let's Encrypt. I tested my FQDN certificate on SSL Labs and it appears with an A grade.

I have been unable to activate new extensions on Android/iOS smartphones since December 29t

Did it say the intermediate certs are present?

You might need a case with 3CX support as I need more specific details that shouldn't be shared on a public forum at this point.

 

[Youdjin]

Any updates on the ringtone issue? My users started complaining that they want the distinctive ringtones back for external and internal calls.

 

[perfect-touch]

Any updates on the ringtone issue? My users started complaining that they want the distinctive ringtones back for external and internal calls.

There is an update in a different thread @Youdjin - pleased to say the issue has been located and fixed - it will be released in one fo the upcoming updates.

https://www.3cx.com/community/threads/v20-missing-alert-info-in-invite.124354/post-587171