Android APP - Receving missing call but not ring

[telnetnz]

We recently upgrade 3cx to latest 18.0.237. Mutiple clients then complains their android APP could not be ring randemly, but just directly get miss call even they keep the APP running on the phone. On the 3cx dashboard, i find the following error log:

Failed to send FCM PUSH to device HUAWEI BLA-L29(Ext.709). Internal exception occured: An error occurred while sending the request.
Failed to send FCM PUSH to device samsung SM-G970F(Ext.900). Internal exception occured: An error occurred while sending the request.
Failed to send FCM PUSH to device vivo vivo 1716(Ext.907). Internal exception occured: An error occurred while sending the request.

It seems that it only happened after upgrade to 18.0.237. Outbound Call function is working well all time. please help invesitage and advice.

 

[GiannosI_3CX]

Hi @telnetnz, thank you for your feedback.
Could you please clarify if Keep Active mode is enabled or not?

 

[telnetnz]

Thanks, the 3cx APP client use is 16.7.8, which is the latest version in google play. However, the "keep active mode" is only available after 3cx andriod app v18. Can you advise how client can download this version of app? thanks

 

[GiannosI_3CX]

You would have to join the BETA program for that. Find 3CX within Play Store and locate "Join the Beta", then press "Join".

 

[Vali_3CX]

the 3cx APP client use is 16.7.8, which is the latest version in google play

What's the Android version of that device? And what brand is that device? The 3CX client we just released yesterday (18.0.3) is not available on devices running Android less than 8.0.

 

[telnetnz]

What's the Android version of that device? And what brand is that device? The 3CX client we just released yesterday (18.0.3) is not available on devices running Android less than 8.0.

my phone is samsung s21 ultra with android 11, but google play shows the version is still 16.7.8. You also check it on https://play.google.com/store/apps/details?id=com.tcx.sipphone14.

 

[Vali_3CX]

Seems like a Google (particular!) store issue, we'll check and let you know.
Thanks for spotting it!

 

[Vali_3CX]

@telnetnz
It was a problem in store "propagation", we encountered such delay in the past but not SO long - now should be OK, please check and let us know.

Sorry for inconvenience!