Android app push messages coming with delay

Status
Not open for further replies.

alex.filip

Premier Customer
Joined
Oct 3, 2022
Messages
14
Reaction score
0
Hello

Please help us to find what is the problem with push messages to android phones. If phone is not unlocked (display off) more than 5 min, all push messages come after 2+ minutes.
No problem with calls, only messages. If Android phone is unlocked - message come instantly and these problem is with all Android phones (we use 50+ different phones with different android versions and different 3cx app versions - latest or beta).
All recommendations from https://www.3cx.com/docs/android-push-troubleshooting/ we implemented, even Enabled “Keep Active” feature but no results.
We tried to get the logs from 3cx management console with the Verbose option enabled. Can you tell me which log file we can find the information we need in?

One example from Android app log (with verbose logging enabled):
2023-10-10 16:08:00.238 14013-26488 I/3CXPhone.FcmService:Got FCM message, sent at 1696942520083, now is 1696943280236 (diff 760153 ms), TimeToLive: 86400s, priority: 2, original priority: 2
 
Hello

Please help us to find what is the problem with push messages to android phones. If phone is not unlocked (display off) more than 5 min, all push messages come after 2+ minutes.
No problem with calls, only messages. If Android phone is unlocked - message come instantly and these problem is with all Android phones (we use 50+ different phones with different android versions and different 3cx app versions - latest or beta).
All recommendations from https://www.3cx.com/docs/android-push-troubleshooting/ we implemented, even Enabled “Keep Active” feature but no results.
We tried to get the logs from 3cx management console with the Verbose option enabled. Can you tell me which log file we can find the information we need in?

One example from Android app log (with verbose logging enabled):
2023-10-10 16:08:00.238 14013-26488 I/3CXPhone.FcmService:Got FCM message, sent at 1696942520083, now is 1696943280236 (diff 760153 ms), TimeToLive: 86400s, priority: 2, original priority: 2
Hi there,
what DNS Servers are you using on the server?
 
As a first step you need to ensure that the PBX is updated to the latest build
Also have you installed the PBX on HyperV?
 
Is the NTP installed on your HyperV?
 
As a first step you need to ensure that the PBX is updated to the latest build
Also have you installed the PBX on HyperV?
No, it's not the latest, we plan to update it. But we have these problems from the beginning (different PBX versions).
 
No, it's not the latest, we plan to update it. But we have these problems from the beginning (different PBX versions).
We saw it one some machines when the used DNS servers are too slow to resolve the Apple or Android push Servers, so try to change the DNS Servers to Google or Cloudflare and then test again
 
At this point you need to update the PBX to the latest build as currently you are not able to activate.
As @Ritter Technologie suggested check your DNS.
 
  • Like
Reactions: TheodorosG_3CX
We saw it one some machines when the used DNS servers are too slow to resolve the Apple or Android push Servers, so try to change the DNS Servers to Google or Cloudflare and then test again
Apple is OK, bthw
 
At this point you need to update the PBX to the latest build as currently you are not able to activate.
As @Ritter Technologie suggested check your DNS.
It is not a DNS problem AFAIC. Infrastructure is big enough, fix phones from both inside and outside is ok.
 
The fix phones don't use or connect to push servers
 
Your issue is the same on Wifi and mobile data?
 
The PUSH is delivered from the PUSH servers of Google or Apple. It is not related with the ip phones or SBC.
As suggested ensure first that the PBX is updated to the latest build.
 
Call comes in, the 3CX notifies the PUSH Servers, and then the push servers notifies the Smartphone
 
  • Like
Reactions: TheodorosG_3CX
The PUSH is delivered from the PUSH servers of Google or Apple. It is not related with the ip phones or SBC.
As suggested ensure first that the PBX is updated to the latest build.
Ok, no problem
 
The PUSH is delivered from the PUSH servers of Google or Apple. It is not related with the ip phones or SBC.
As suggested ensure first that the PBX is updated to the latest build.
Thx, we will try with the update, but like I said, the problem is from the beginning and every time the update (at that time) was the latest one.
 
Status
Not open for further replies.

Forum statistics

Threads
112,147
Messages
590,959
Members
165,167
Latest member
Finatra.us