3CXPhone for Android 15.1.41, goes offline as soon as it goes out of focus

[Dalibor]

Hello,

I've set up a new 3CX server recently (debian).
I'm working thru several problems with it, but this one is most annoying:

As soon as the 3CX Phone application goes out of focus, or screen turns off, the application disconnects.
And since it is running trough the tunnel, other SIP applications (zoiper, ekiga) won't even connect to the server.

This is not limited to a certain phone, but all android devices I tried it on.

Just to follow the rules, here is the phone information:

APP_VERSION:150141
PACKAGE_NAME:com.tcx.sipphone14
PHONE_MODEL6603
ANDROID_VERSION:6.0.1
BRAND:Sony
PRODUCT6603


The server version is the latest one, and fully updated.
3CX Phone System Standard Edition
Version Number: 15.5.5
It has a static public IP address.

The server sits behind a mikrotik router, and has all the rules created according to the instructions.
The firewall check comes up as "Firewall test OK".
The only difference from the vanilla setup is the SIP port moved from 5060 - all firewall / nat rules are changed accordingly.

The Push service is set, but it is not working. I've tried with the "own" account (followed the instructions), and later on switched back to "3CX Account".

I've re-provisioned the phones after every change made.

While running in the foreground, it can call out and receive calls.

Help ?

 

[Nam Tran]

Same problem here. 50% of the call logs is categorized as unanswered. Many people believe that they have not received any call. 3CX client on my Nokia 5 gets disconnected right after the screen turns off. Waking up the phone does not help at all. I have to manually close the app and re-launch it. So annoying experiences.

 

[Marios Neophytou]

Hello @Dalibor ,

Can you send another welcome email and provision you device again? It should not be a problem with PUSH if it is right configured.
Also, can you check your 3CXDieler logs under /var/lib/3cxpbx/Instance1/Data/Logs to see if the responses are ok?

Thank you

 

[Dalibor]

Update - looks like my problem is resolved: updated system to 15.5.3849.1, and the push magically started working !

It started working without re-provisioning the clients ...