V20 Update 10 Alpha 2: Freedom to Deploy Vendor Tested Firmware to Individual Phones

[KyriacosS_3CX]

Dear 3CX team, thanks for the update, looking great, testing the new features. I noticed one thing on our alpha that is different to stable releases. Maybe that is only on my instance, the call history shows permission errors and the user has to be at least supervisor to see the abandoned queue calls. In the past user permissions were sufficient. Was there a change with regards to the call history or permissions?

Hello,

Can you check if you have "Abgebrochene Warteschleifenanrufe in den letzten Anrufen für Nutzer, Rezeptionen und Abteilungsadministratoren verbergen " enabled in System > Options > Apps? If yes, then what you are seeing is the correct behaviour.

 

[Ryan_Fisher_Techmode]

Great update! My team will enjoy the updates for FW and Phone provisioning as well as the new transcription prompts. Does the 3CX AI server need to be updated as well?

 

[ThomB_3CX]

@centrovis Thanks for your feedback.
Couldn't reproduce your issue.

Could you kindly go to Admin > System > Options > Apps tab and confirm that the first option "Hide Abandoned Queue Call in Recents for Users, Receptionists and Department Administrator" is disabled.

​

 

[patrickb_de]

I noticed that since Alpha 2, the global properties for backup notification emails starting with "MAILTEMPLATE_BACKUPSUCCESS_" are no longer configurable or editable.

Is there an alternative way to customize these email templates now, or has this functionality been removed entirely?

 

[Ryan_Fisher_Techmode]

Is anybody else having issues with SSO using the Microsoft365 integration? After the update we are getting errors about a redirect URI mismatch. I even rebuilt the app from scratch and am still getting the error. See below.

AADSTS50011: The redirect URI 'https://xxxxxxxxxxxx/oauth2office2' specified in the request does not match the redirect URIs configured for the application 'aececb81-a400-40f9-aec9-9f563cecb8b3'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this.

 

[Charles_3CX]

Is anybody else having issues with SSO using the Microsoft365 integration? After the update we are getting errors about a redirect URI mismatch. I even rebuilt the app from scratch and am still getting the error. See below.

AADSTS50011: The redirect URI 'https://xxxxxxxxxxxx/oauth2office2' specified in the request does not match the redirect URIs configured for the application 'aececb81-a400-40f9-aec9-9f563cecb8b3'. Make sure the redirect URI sent in the request matches one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this.

Please open a support ticket with us at 3CX technical support to advise on this.

 

[ThomB_3CX]

@Ryan_Fisher_Techmode this is a bug in the SP10 Alpha build. Will be fixed for Beta.

 

[rickybogo]

thank you guys...

 

[tronic]

Upgrading to the new Update 10 Alpha 2 from Alpha 1 - on our demo system caused the integrations page to show the error "Please contact administrator," so we had to restore a backup.

Is this isolated to us?

 

[KyriacosS_3CX]

Upgrading to the new Update 10 Alpha 2 from Alpha 1 - on our demo system caused the integrations page to show the error "Please contact administrator," so we had to restore a backup.

Is this isolated to us?

Hi, did you happen to save any logs? What integrations did you have if any? Other sections were working OK?

 

[tronic]

Hi, did you happen to save any logs? What integrations did you have if any? Other sections were working OK?

Everything else worked fine, as it took some time for use to be noticed. I will take a snapshot and give it another go for you and do some verbose logging

 

[tronic]

Same thing: upgrading again from the Alpha 1 to Alpha 2. Thought might be resources, but bumping them up didn't change things.

 

[KyriacosS_3CX]

Same thing: upgrading again from the Alpha 1 to Alpha 2. Thought might be resources, but bumping them up didn't change things.

Hi, I have DM'ed you for followup.

 

[KyriacosS_3CX]

Hi @centrovis ,

Did our suggestion resolve the issue?

 

[KyriacosS_3CX]

Hi @tronic ,

I believe the team has resolved the issue?

 

[tronic]

Hi @tronic ,

I believe the team has resolved the issue?

Yes all sorted thanks.

 

[patrickb_de]

Hi,

since Update 10 Alpha 2, we have no longer been able to modify department role rights via the XAPI. A PATCH request to Groups({id}) including Rights returns HTTP 204, but the values remain unchanged afterwards. Other fields of the same Group (e.g. Name) are updated as expected.

Is this intended behavior i.e. are role rights now fixed and only manageable through the predefined roles or user assignments or is this unintended behavior where write operations on Groups.Rights are silently ignored?

 

[telebit]

@KyriacosS_3CX Same issue as @tronic reported above: after the update to V20 Update 10 Alpha 2 (build 20.0.10.1621, 3CX hosted instance telebit.3cx.pl) the Integrations page shows "Internal server error occurred. Please contact administrator". Everything else works. GET /xapi/v1/CrmIntegration returns HTTP 500 with an empty body; PATCH, Pbx.Test and template delete on the CRM module return 500 as well, while CrmTemplates/Pbx.GeCrmtTemplates() and the M365 integration endpoint work. Before the update I had a custom CRM template ("Tarifon") configured; the template file is gone after the update. I don't need the CRM integration anymore, so resetting it is fine. Could you apply the same fix as for tronic?

 

[telebit]

Additional impact: starting any new external conversation (SMS via Generic SMS trunk) fails with "Autofac.Core.DependencyResolutionException in 'GetOrCreateConversation' line 5773 – An exception was thrown while activating Integration.Crm.Storing.CrmProcessorWrapper". So the broken CRM integration config blocks all SMS/external chats, not just the Integrations page. Note: while trying to unblock it I uploaded a placeholder CRM template named "Tarifon" (a copy of the Database MySQL template) – please remove it together with the CRM config reset.