Problem with notifications Failed to send FCM PUSH to device

[mlarky01]

The problem went away for us with the V20 updates.

 

[Abrahams]

I have updated v20 to last version,but the problem still exist,I can't find any other information how to solve this problwm

 

[Vali_3CX]

I have updated v20 to last version,but the problem still exist,I can't find any other information how to solve this problwm

What's the device brand/model and OS?

 

[Abrahams]

We've tested on Samsung A51, Samsung S24, iphone 11

 

[Vali_3CX]

Oh, so it happen also on iOS, in this case seems to be a PBX configuration problem, you may check if the licence is valid
https://www.3cx.com/community/threa...-without-facilityid-after-v20-upgrade.125034/

Anyway, strictly for Android CX client, you can turn on the Keep Active in the settings, see if it's working.

 

[Abrahams]

The license is valid, and firewall has no issue

 

[portugaltrails]

Im having the exact same problem in v18.

Cellphones don't ring even with alllllll battery and APP settings to performance mode.
I have a lot of cellphones with this challenge. Samsung, new OPPO and Xiaomi Redmi 10.

Curiosity: it didn't happen yet with an OPPO old model and Huawei old model.

Im looking forward for a solution. Please help me.

 

[SAV Distrimatic]

Hello,
I get the same error message on my dashboard. It is a PRO version hosted by 3CX and the operator is Dstny. I have never encountered the problem before with V18, I only have the problem on my first instance deployed in V20. I'm experiencing the problem on a Samsung galaxy A71, on which I have no problem with accounts from other instances that are configured on it. The problem also occurs with Iphone 14. At first the symptom was that the call did not even arrive on the Android or Apple device, then after a few days the problem evolved without me doing anything and now the call is arriving but in “unknown”. Did you find the solution to resolve these issues?
Thank you so much

 

[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,

 

[Scot Busby]

We have 3 users which have Android cell phones connected to the 3CX system. The remaining users are iPhones. We just upgraded over the weekend to v20 and these 3 phones have been filling the event log with these errors. They are repeating and all the same, minus the extension.

Failed to send FCM PUSH to device samsung SM-S901U(Ext.XXXX). Received error from server: NotFound: Not Found. Find more info at: https://firebase.google.com/docs/reference/fcm/rest/v1/ErrorCode

Anything anyone did to resolve this or is this a missing setting on our system for these types of phones?

Thank you!

 

[pmterp]

We have started getting reports of clients experiencing this issue.
In our case, the client is on the latest v18 build (18.0.9.31) and using a Samsung Galaxy S10+. They have disabled battery optimization.
If the device has been unused, it'll fail to ring while the PC app is ringing. Then it will get notifications for a little while after that.
Seeing "FCM returns Unauthorized: Unauthorized" and "Got Unauthorized from FCM (token is expired?)" in the System Service log.
Is there anything we can do or additional information we can provide to help get this resolved?