Hi There,
Working with a partner on this case, but hoping for some immediate help here also if possible.
We have some new CAT S42 Phones - Android 10. Proof of concept went fine, and now we're 60 handset deep into a roll out.
We are finding in some very odd occasions, that push notifications for incoming calls are not received by the handset. Only the Missed Calls notification gets immediately delivered and displayed once the call is cancelled. In some instances we are then seeing the push notification getting delivered to the handset with a delay. This causes the handset to ring, but then go off.
So - Call gets made to handset, handset does not ring, missed call notification gets to the handset immediately after call is disconnected. Incoming call alert may or may not come shortly after.
You can see this on the Verbose log on the Android handset;
12-03 09:14:36.615 I/3CXPhone.FcmService( 4962): (thread 5985) Got FCM message, sent at 1606986879683, now is 1606986876615 (diff -3068ms), TimeToLive: 86400s
12-03 09:15:22.969 I/3CXPhone.FcmService( 4962): (thread 5985) Got FCM message, sent at 1606986855193, now is 1606986922969 (diff 67776ms), TimeToLive: 0s
The extension is set up for Push Notification. No issues with notifications to iOS users, and this is not globally occuring for all CAT S42 Android handsets either.
Battery Optimization is disabled for the 3CX app.
Not using own Firebase Cloud Messaging Platform - Although open to using this, but know nothing about the platform, or how to get logs from it.
Help!
Working with a partner on this case, but hoping for some immediate help here also if possible.
We have some new CAT S42 Phones - Android 10. Proof of concept went fine, and now we're 60 handset deep into a roll out.
We are finding in some very odd occasions, that push notifications for incoming calls are not received by the handset. Only the Missed Calls notification gets immediately delivered and displayed once the call is cancelled. In some instances we are then seeing the push notification getting delivered to the handset with a delay. This causes the handset to ring, but then go off.
So - Call gets made to handset, handset does not ring, missed call notification gets to the handset immediately after call is disconnected. Incoming call alert may or may not come shortly after.
You can see this on the Verbose log on the Android handset;
- The call was made to the extension at 09:14:15.
- The android handset did not ring.
- The call was ended (20 second default rule on the extension) at 09:14:35.
- The android notification got the missed call notification immediately. This displayed to the phone. As per the log files;
12-03 09:14:36.615 I/3CXPhone.FcmService( 4962): (thread 5985) Got FCM message, sent at 1606986879683, now is 1606986876615 (diff -3068ms), TimeToLive: 86400s
- About 1 minute later, the android phone rings for a split second then stops. You can see that the push notification for the incoming call arrived at the handset – with a 67 delay;
12-03 09:15:22.969 I/3CXPhone.FcmService( 4962): (thread 5985) Got FCM message, sent at 1606986855193, now is 1606986922969 (diff 67776ms), TimeToLive: 0s
The extension is set up for Push Notification. No issues with notifications to iOS users, and this is not globally occuring for all CAT S42 Android handsets either.
Battery Optimization is disabled for the 3CX app.
Not using own Firebase Cloud Messaging Platform - Although open to using this, but know nothing about the platform, or how to get logs from it.
Help!
