no push at all with android Client V15.5.342.392?

[nobody]

I have two phones: one Samsung Note8 with Oreo and one Blackberry KeyOne with Nougat.
On both calling using the 3cx client works fine, including receiving calls as long as the app is in the foreground, but no push at all.
Strange, I thought it used to work with the previous version.
I use my own push account.
In the dialler log appears (example):

18.06.01 16:03:17.709|100017| Inf|50|0008|: Call(NNNNNNNNNNNNN): sent push request:
{"registration_ids":["verylongalphanumericnumber"],"priority":"high","time_to_live":60,"data":{"replaces":"longalphanumericnumber..;from-tag=hexnumber;to-tag=hexnumber","callerid":"+49XXXXXXXXXXX","callername":"49XXXXXXXXXXX:B:NAME NAME","inst":"hexnumber","reason":0,"ver":1}}
GCM response: OK OK
18.06.01 16:07:17.581|100019| Inf|50|0015|: Update PUSH client for Extn.NN: Allowed, regid = FCM#verylongalphanumericnumber,A,hexnumber

i thought I use firebase, but the first line talks about "GCM response: OK OK".
The second line has a text fragment "FCM" in it.

I disabled the firewall on the phones, I changed from WiFi the Mobile network. No change.

How can I further debug why this is not working? If Google or firebird send nothing the phone will not receive anything. Is there any handshake - I guess not. You send a message in the cloud, and hope it will be delivered.

 

[nobody]

ok,
I did the following in addition:
Went to the Firebase console and accepted new terms of service - no change
Cleared the Firebase key, and restarted the services (there is a post in the forum which suggests it is one option to use the 3cx built in key) - no change
provisioned the phone with an account from a different 3cx system but still version 15.5.8801.3 - no change
Tried 3cx client version 15.5.240 - no change

I checked again when an incoming calling works or not:
works not when choosing "exit" in the menu
works not when choosing "exit - ignore push" in the menu
works not when pressing the android menu button then close the app or close all apps

Now i am unsure if it really worked before, because most of the time guess I just dismiss the app and not exit it or close it.
For me it looks still like push is not working at all.

How should it behave, and how does it behave at other phones?

 

[nobody]

next:
tried a test program if firebase notification could work - yes test ok.
deleted firebase project, created new project
put project data in 3cx pbx
rebooted pbx
Now it works again!

Question remaining: I reprovisioned the phone at any new attempt to fix the problem. But in the last attempt which was successful I rebooted the pbx (the manual says: restart service).
Either the tip to use the built in Firebase key is wrong or a restart is necessary before reprovisioning the phone?
Why is it nearly always that hard to fix a problem with the 3cx android client? I am a support guy and finally my customers will benefit, but If I imagine a paying customer, which depends on working phones,....
This is not a toy, People pay real money for it. If an Android client is delivered, the basics must work.At the very least picking up a call, calling a party by dialing a number should be possible. If the sound quality is not optimal, ok, fine, this is a problem which can be dealt with, If all missed calls are shown multiple times, ok, I wait for an update. But missing calls because of some cloud service not under my control acting up - no.
Why is there not an option to keep that program just running, regardless of the energy it consumes? Using less energy is a good thing, but only if I still get my calls. Like having a car only using 1l/100km but with a maximum speed of 2km/h i will never make it to the destination, walking would have been a better option.

 

[nobody]

my previously "working again" is no true.
Turns out, push notification still is not working properly.
On the Note8, if I close the (samsung branded) cover, an incoming call via 3cx will never ring. A gsm call will. If I open the cover again, the call will ring. How can this be fixed?

Now it gets a little more complicated:
Those two phones (the note8 and the keyone), they are both provisioned for the same extension, and, if the 3cx client is in front and both phones are awake, both will ring and can answer the call. Note8 is using mobile network, the Keyone WiFi.
But, if one of the phones will go to sleep by closing the cover or powering down the display, only one of the phones will receive a call via 3cx.
So, if i close the cover of the note8 and the Keyone is still availiable the Keyone wakes up. But, after this, the note8 will never get a call even If I open the cover and unlock the system. Only if I open the 3cx App on the note8. If I do this, the Keyone is dead and will not ring.

That does not make sense. It should be possible to have more then one device active. If one device goes down or is unavailable, it should resume operation after it is available again. Also, more then one device should ring if logged in, regardless of the status of the screen/cover or network location etc. Or it should be forbidden to login with more then one Android device at a time. You have a phone, a mobile, a tablet, all should ring concurrently. Changing the status of the device should not influence the function of another device.

Can anyone else try this out - using more then one android client on one extension? For me this looks like a bug or problem with the Google Firebase.

 

[Vali_3CX]

The current implementation of the PBX allows only one 3CX mobile device to be push-notified - the most recent registered one.

P.S This limitation will be addressed most probably in upcoming SP6.

 

[nobody]

It is quite normal that people in forums post because they have problems. Seldom you see a topic starting with a praise of new features.
And to stay on topic: if this is a feature by design, its something which makes the android client not safe to use, unless you disable the multiple login option, or. tell the users what happens if they do use it.
Call it a bug or a limitation by design. The previous client which worked without GCM/Firebase did not have this problem.
Creating a page with releasenotes and known problems will not hurt. Most people will appreciate it I guess. Of course I will submit this in the ideas section.

 

[craigreilly]

Is it common for folks to carry 2 devices that both will have 3cx on? I have some that have a personal cell and a business cell - and 3cx is only on the business device.

I agree a listing of limitations and known bugs would be beneficial for all releases of 3cx distributed software.