Cannot send FCM PUSH without FACILITYID after V20 upgrade

[BMGLABTECH]

I recently Upgraded to V20, since then I get errors (Event ID 50020) in my logs about not being able to send push notifications to smartphones.

 Failed to send FCM PUSH to device motorola moto g52(Ext.741). Internal exception occured:
 System.Exception: Cannot send FCM PUSH without FACILITYID specified at
 _3CX.Push.PushTransport.GetFcmToken(Boolean forceRefresh) at
 _3CX.Push.PushTransport.PushAndroidFcmV1(PushTask pushTask) at
 _3CX.Push.PushTransport.PushAndroidFcm(PushTask pushTask)

I also noticed that when comparing my PBX Parameters to this list I am missing the GCM_HOST parameter. GCM_AUTH and GCM_SENDERID are blank

Edit: I tried setting the GCM_HOST parameter manually but it did not change anything

 

[nikolascx]

Hello thanks for the update
We are checking with prio.

 

[ivank]

Does your license show "Valid" in the Admin / System / License page? Try refreshing it if not.

 

[BMGLABTECH]

The License is valid and the Firewall checker also has no complaints.

 

[BMGLABTECH]

Updating to RC4 seems to have fixed the issue

 

[Abrahams]

How to update to RC4?

 

[SweetAction]

How to update to RC4?

Navigate to the updates tab and click install as needed
/#/office/system/updates

 

[SAV Distrimatic]

Good afternon,

I got the same issue on a new 3CX instance version : Version 20.0 Update 1 (Build 731 Release) , anytime I try to get a call on a phone (Iphone or android system (I tried with Samsung and Xiaomi)) i got the error 50020 : Failed to send FCM PUSH to device samsung SM-A715F(Ext.11). Internal exception occured: System.Exception: Cannot send FCM PUSH without FACILITYID specified at _3CX.Push.PushTransport.GetFcmToken() at _3CX.Push.PushTransport.PushAndroidFcmV1(PushTask pushTask) at _3CX.Push.PushTransport.PushAndroidFcm(PushTask pushTask)

My licence is valid.

 

[SAV Distrimatic]

Hello,

I haven't had a response from 3CX but I wanted to provide a response for other members of the community who might come across this. The issue appears to have resolved itself, and 3CX has released the final version of V20.0 Update 2 (Build 715 Release) which I ran this morning, which appears to have completely fixed the issues on both Android and Android. on iPhone. The only problem that persisted was that on my Android I received the call twice, that is to say on the "3CX" application and on the "Phone" application. On the "3CX" application, the call arrived authenticated but on the "Phone" application, the call arrived as "unknown" and of course it was this notification that took over. So I found a way to modify this setting in the "3CX" application. You have to go to the status settings via the little pencil and uncheck the "Make my mobile ring simultaneously" option. However, this option was not activated in my user's profile when I checked on the admin console. This is if this information can be useful to anyone else...

BR,

 

[nikolascx]

HI Team
I was checking this but after a code review, we found nothing.

Does this happen every time?
Does it happen on all the networks where you are connected?

This is an edge case and I have no other reports like this. Although in some networks, and with some phones I did experience this behavior. Mostly with android. I think it is network related and also phone related. Multiple push registrations cause this confusion.

Try and get more experience and keep the server build and mobile apps stable (unchanged) for some time.

now update 2 is released final so You can update and stay on it.