Push messages not always working

Discussion in 'Android' started by Bart Meuris, Aug 29, 2017.

Thread Status:
Not open for further replies.
  1. Bart Meuris

    Joined:
    Aug 29, 2017
    Messages:
    2
    Likes Received:
    0
    We installed v15.5.5 on Debian and configured a Firebase app in Google, and followed this guide: https://www.3cx.com/docs/firebase-android-client/

    However, Android phones do not always seem to receive push notifications. I checked the log in `/var/lib/3cxpbx/Instance1/Data/Logs/3CXDialer.log` and I only sometimes see a message like this:

    17/08/29 14:03:04.519|100017| Inf|50|0016|: Call(TDHVCJNHYFGP): sent push request:
    {"registration_ids":["..."],"priority":"high","time_to_live":60,"data":{"replaces":"...","callerid":"031","callername":"Bart Meuris","inst":"d85ba528","reason":1,"ver":1}}
    GCM response: OK OK

    When such a message pops up in the log, the push messages work perfectly. The problem however is that about 50% of the time, no such message appears in the log, as if no push message is being sent - and the Android phones do not wake up for incoming calls.

    We tried reprovisioning and re-registering devices, but nothing seems to resolve the issue.

    On iOS devices, we don't seem to have these problems. Any ideas what this might be?
     
    #1 Bart Meuris, Aug 29, 2017
    Last edited: Aug 29, 2017
  2. Marios Neophytou

    Marios Neophytou Support Team
    Staff Member 3CX Support

    Joined:
    Mar 1, 2016
    Messages:
    245
    Likes Received:
    12
    Hello @Bart Meuris,

    What version of Android Client are you using? What is your mobile phone brand?

    Thank you
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Bart Meuris

    Joined:
    Aug 29, 2017
    Messages:
    2
    Likes Received:
    0
    This was happening with multiple phones/brands (Samsung, HTC, One+) we're testing with, with the most recent version available (only installed in the last week from the google play store).

    The main source seemed to be a problem with the provisioning of the phones. Our 3CX server is hosted behind a 1:1 NAT, and some extensions/3cx clients were configured to be provisioned using the local IP network interface of the machine, which resulted in weird behavior. Changing the accounts and reprovisioning the phones solved the issues it seems.

    I'm not sure why the local IP is even listed in the "Network interface for registration and provisioning". It currently lists both the internal and external DNS entry, and the IP of the local interface. Is there a way to remove this to prevent this from being configured like this accedentally?
     
Thread Status:
Not open for further replies.