Push delay Android - Redmi 9c

[QuotumVOIP]

Hello,

I have major delays when I'm calling to internal 3cx extention.

When I end the call, sometimes the phone rings for one second, or the phone displays a missed call.

On my iphone I don't have any delay.

Checked firewall, dns, last updates 3cx server(16), last update 3cx app.

Does anyone knows the solution for this problem?

 

[QuotumVOIP]

Some phones reponses fast, others still delayed.

 

[NickD_3CX]

Some phones reponses fast, others still delayed.

In that case, this may be something related to the network the User's phones are on.
When 3CX sends a PUSH message, we send it to Google, then Google is tasked with delivering it to the devices that the users are running the 3CX app on.

Does this happen consistently for certain users? What network (WiFi/LTE) are they using when this happens?
Also, does it happen on certain make/model Android Phones, or is is random?

I am trying to detect the pattern in which this happens to try and narrow down where it could caused from.

 

[QuotumVOIP]

In that case, this may be something related to the network the User's phones are on.
When 3CX sends a PUSH message, we send it to Google, then Google is tasked with delivering it to the devices that the users are running the 3CX app on.

Does this happen consistently for certain users? What network (WiFi/LTE) are they using when this happens?
Also, does it happen on certain make/model Android Phones, or is is random?

I am trying to detect the pattern in which this happens to try and narrow down where it could caused from.

They are all on the same WIFI network.

No random with users. All on wifi.

There are 2 types of phones, 4 iphones (no problem), 8 android (Redmi 9c) phones.

only the android phones have those problems.

 

[QuotumVOIP]

https://www.3cx.com/community/threa...-incoming-call-notification.77978/post-356978

seems like the same problem of this thread.

 

[NickD_3CX]

I think 5s is considered OK, considering the journey a PUSH Message follows:
PBX --> Google PUSH Service --> Mobile Phone User --> Wake up device --> Ring 3CX App Client

You can't get much better than this, and ironically in most cases, the most "time-consuming" part is the phone waking up.
Some phones maybe slightly faster than others, but again a 3-4 second delay between hearing ringing on the Callers side and the Mobile App ringing is expected.

 

[QuotumVOIP]

I think 5s is considered OK, considering the journey a PUSH Message follows:
PBX --> Google PUSH Service --> Mobile Phone User --> Wake up device --> Ring 3CX App Client

You can't get much better than this, and ironically in most cases, the most "time-consuming" part is the phone waking up.
Some phones maybe slightly faster than others, but again a 3-4 second delay between hearing ringing on the Callers side and the Mobile App ringing is expected.

Tnx for the support and feedback.

ok, that's also the reason why it's faster on IOS, I think.

 

[NickD_3CX]

In my personal life I happen to be an Android user, but I have to admit the Apple does have a lot good things going.
Specifically the fact that they control the hardware AND the software that goes on their devices, allows them to optimize better in general.

Regardless though, Androids work great as well, but you get a more diverse experience depending on the device you are holding.
Most Apple-priced Androids may be sliiightly faster, but in no case do I think that your 5-second delay is a problem.

 

[BobPost]

I was having the same issues with the Android client so I got a network capture during the push process. I'm running 16.0.1078 3cx on Debian and was using public DNS servers. I was initially using google DNS but tried ATT as well with the same results. I found on each push the OS was doing a DNS query for IPV4 and IPV6. The IPv4 query would respond immediately but the IPV6 would timeout on each first attempt. About 5 seconds later the system would do another DNS query for IPv4 and IPV6 and both would respond immediately and then Android client would get the push message. This was very consistent. On the server I uncheck the automatic binding to IPV6 adapters and the result was the same.

I then changed the Debian OS to use my internal DNS servers and found that the the IPV4 and IPV6 queries were both responding immediately on the first attempt and the push notifications on the Android phones were almost as fast as the desktop phones. I have not had any delay push notifications since changing the DNS on the Debian OS to my internal DNS servers.

 

[QuotumVOIP]

I have still the same problem. Sometimes after 15 rings the phone starts ringing.

DNS is internal. ipv6 is disabled.(on linux, not just web interface)

Sometimes some phones ringing almost immediately and one phone during 15 rings before start.