Push service not working

Discussion in 'Android' started by JST, Jan 24, 2017.

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

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    I installed the Google API key for the push service before I have created the config file for my phone. My expectation was that the push service would wake up the phone once it goes to sleep (unregistered), but this never happens.

    How can I fix that? Thank you!
     
  2. Marios Neophytou

    Marios Neophytou Support Team
    Staff Member 3CX Support

    Joined:
    Mar 1, 2016
    Messages:
    241
    Likes Received:
    12
    Hello,

    1. Make sure that you've made the right configuration for push by following this guide : https://www.3cx.com/docs/configuring-google-push/ .
    2. Make sure that you public IP did not change for any reason
    3. Check your 3CXDialer.logs for any Unauthorized response from the GCM (GCM response: Unauthorized Unauthorized) under : C:\ProgramData\3CX\Instance1\Data\Logs\3CXDialer.log


    Thank you
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. JST

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    Thank you for getting back to me!

    Do you know where I can find this log on Debian Linux? I found some logs in the following folder: /var/lib/3cxpbx/Data/Logs

    However, I don't see the 3CXDialer.log folder in that directory.

    I have followed all steps in the guide, but no luck. Hopefully, I can find some clues in the log once I can locate it.
     
  4. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,443
    Likes Received:
    282
    The logs are located at /var/lib/3cxpbx/Instance1/Data/Logs
     
  5. JST

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    The 3CXDialer.log shows has the following entries:

    17/01/25 19:25:07.978|100000| Inf|30|0001|: ** Dialer: Plugin initialization St$
    17/01/25 19:25:08.025|100019| Inf|50|0001|: Update PUSH client for Extn.1020: A$
    17/01/25 19:25:08.030|100020| Inf|50|0001|: PUSH client for Extn.1020: Register$
    17/01/25 19:25:08.030|100019| Inf|50|0001|: Update PUSH client for Extn.1010: A$
    17/01/25 19:25:08.030|100020| Inf|50|0001|: PUSH client for Extn.1010: Register$
    17/01/25 19:25:08.032|100001| Inf|30|0001|: ** Dialer: Plugin Started **
    17/01/25 19:31:44.913|200003| Trc|50|0009|: DBG: Contact for b14f8209 is active$
    17/01/25 19:31:44.917|100019| Inf|50|0009|: Update PUSH client for Extn.1010: A$
    17/01/25 19:32:03.970|100019| Inf|50|0009|: Update PUSH client for Extn.1010: A$


    I am guessing that this means that the initial push is successful. The time shown is the time when I rebooted the system. There are no other entries. The extensions show consist of a desk phone and the 3CX Android mobile client. Extension 1010 is also using the Windows Client from time to time.

    Should this log also show the actual push for an incoming call?
     
  6. TLA

    TLA

    Joined:
    Jan 21, 2017
    Messages:
    12
    Likes Received:
    2
    Hi,

    Does incoming call work when the phone is awake?

    I had this issue when the phone was asleep and I resolved it by deleting the sip account on the phone and sending the registration mail to it.
    I opened the file attached to this mail and the Push worked with this newly created sip account.

    Hope this help.
     
    #6 TLA, Jan 27, 2017
    Last edited: Jan 28, 2017
  7. JST

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    Thank you for your reply.

    Yes, it does.

    I also have an update. While working on fixing another issue, I discovered that some of my configuration options use an incorrect, local IP address. This issue has prevented me from connecting through the external network. My best guess is that the push issue will go away once I have re-installed the system.

    I will report back next week.
     
  8. sleepless

    Joined:
    Feb 17, 2017
    Messages:
    2
    Likes Received:
    0
    I have found this in my logs. how can i solved?

    I have a dynamic IP and can't restrict the api key to one IP adress but all other steps i followed excatly...
     
  9. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,443
    Likes Received:
    282
    If you do not use your public IP address then google will not authorise you and push will fail. I am afraid every time that your IP changes you will need to update your Push project.
     
  10. JST

    JST New Member

    Joined:
    Jan 8, 2017
    Messages:
    107
    Likes Received:
    1
    If you haven't restricted your Google API project with an IP address (or range), then it should always work. So, you shouldn't see the error message in the log. It normally works fine for me using a dynamic address. Are you using your own dynamic DNS provider or are you using the one from 3CX? I found that the 3CX service is sometimes unavailable or needs extra time to update to a new IP address.

    I am guessing that this might never work perfectly with a dynamic IP.
     
  11. sleepless

    Joined:
    Feb 17, 2017
    Messages:
    2
    Likes Received:
    0
    Why, if the Key is open? so it's not restricted and everybody can...
    This is the only option for a dynamic address.

    But i don't care in the future -> i use the 3CX Pushaccount and now it works fine...
     
Thread Status:
Not open for further replies.