PUSH notifications problem

Discussion in 'Android' started by johnbrunsden, Nov 17, 2016.

Thread Status:
Not open for further replies.
  1. johnbrunsden

    Joined:
    Nov 17, 2016
    Messages:
    4
    Likes Received:
    0
    Hi,

    We have just ran through the setup for enabling PUSH notifications on the Android client.

    Google API's looks okay and we have removed and re-added. Firewalls rules are also correct.

    PUSH is showing Enabled on the lock screen, but we are not getting calls/messages through whilst the phone is locked.

    Does anyone have any advice as to what to look for/change to get this to work?

    Thanks
     
  2. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,349
    Likes Received:
    274
  3. johnbrunsden

    Joined:
    Nov 17, 2016
    Messages:
    4
    Likes Received:
    0
    Hi,

    Thanks for the reply.

    We have tried creating a new Google API project, following those steps, but still the same issue.

    Our 3CX system is not actually public facing, but we do have a valid connection to both the 3CX phone server using internal Wi-fI so we can ping the Google API address and our phones can connect out on port 443 to the Google API addresses as well.

    Does the Google API need to be able to contact the 3CX phone server? Or is it just Outbound only from the phones and the 3CX phone system?
     
  4. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,349
    Likes Received:
    274
    Excuse me but i did not understand if your 3cx server can access the internet. Can you ping the google API server from there?
    The google API requires the public IP address the PBX is behind to authenticate you and push can work.
    The PBX sends the push request to the Google API servers so without and active internet connection it will fail.
    If you have a active internet connection from the PBX server have you re-provisioned the android clients after the new project was made? (send a new welcome email).
    Also have you tried push using 3g/4g or only wifi?

    The connection required is outbound as stated in the guide
     
  5. johnbrunsden

    Joined:
    Nov 17, 2016
    Messages:
    4
    Likes Received:
    0
    Thanks for your advice.

    We can ping the Google API's from both the 3CX and the Android phones themselves.

    We connect to an internal Wi-Fi on the phones, so cannot test using 3G/4G.

    Have also tried to re-provision after and also tested V15 BETA but still the same issues.

    The phone itself is reporting PUSH is enabled but I can only answer calls when the App is open and "in focus" so to speak.
     
  6. johnbrunsden

    Joined:
    Nov 17, 2016
    Messages:
    4
    Likes Received:
    0
    This can now be marked as resolved.

    We have now added a public IP for the PBX and all is now working!

    We have also managed to use the new Firebase Cloud Messaging, which appears to have superseded GCM as the new platform for Cloud Messaging at Google. The interface is slightly different, not sure how long Google will keep GCM running but might be worth noting so that the instructions can get re-written should you have to set up a Project purely through Firebase.

    Thanks for all the help on this one.
     
  7. Ernesto D Casas

    Joined:
    Jun 26, 2017
    Messages:
    1
    Likes Received:
    0
    I´m having the same problem, but i detect that is a phone problem, with ASUS... because my wife mobile it´s working perfectly.! Any one have another ideas!????
     
  8. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,349
    Likes Received:
    274
    I am not familiar with the Asus software but make sure that notifications are allowed for the 3CX client. You should also exclude the 3CX client from any power saving options that might prevent the client from waking when a push message arrives
     
Thread Status:
Not open for further replies.