Action Required: Disable Customer Android Push

[KyriakosP]

For better reliability of Push required to wake up the phone on inbound call or messages, we are updating Google’s Firebase Cloud Messaging (FCM) library. A custom account is no longer required and in fact is no longer supported by Google. To keep receiving inbound call and chat notifications, you should upgrade to Update 8 as soon as possible. I...

Continue reading the Original Blog Post.

 

[QueBall]

YES!

Laziness and procrastination of ignoring the advice to apply my own Google API keys wins in the end. None of my managed instances got a custom API key as long as it was still working I didn't see much point.

Now can you throw in some generic S3 compatible storage option for the backups (our other API annoyance) so we do not use google storage for backups? Would love Backblaze or Wasabi for cheap backups!

 

[bravad]

We are controlling through the firewall, we do not accept all outgoing TCP 443 traffic.
Can you give us the address of the 3CX PUSH Server for Android?

 

[cobaltit]

So if you are controlling through the firewall, you should also be able to do logging through the firewall which would show you where it's trying to go.

But there is no 3CX Push Server. As the article states, they are using Firebase Cloud Messaging. This article has more information including a link to the Google documentation for FCM ports and firewall configuration: