Is there some reason that calls to an Android Connect Client are not ringing unless the app is in the foreground?
Any suggestions as to how to fix this issue or other folks with same issue? Newest version of platform and connect.
Doug
It doesn't work either way if
It doesn't work either way if in the Background on my mobile Android. This may be a bug, surprising at the age and number of updates. Does anyone use Mobile connect sucessfully?
I have been not telling customers about it due to flakiness but now that covid 19 and mobile working is desired. Connect would be perfect IF IT WORKED.
Doug
I gave up on mobile connect
I gave up on mobile connect and just recommend customers remaining on Thirdlane use their favorite SIP client. The downside to this is either you need to force reregister the handset when you return to the office or setup 2 extensions for the users and set them up to use the multi-extension script.
I got a report that the MAC
I got a report that the MAC version works pretty well, not sure if it works in a ring group or not.
I have had to tell folks to use MizuDroid SIP phone, which works great, although it is a bit challenging to setup.
More work needed on the Droid version of Thirdlane Connect, Clearly.
I haven't used a recent version of Thirdlane Connect in a while, however, I remember on older versions, one of my bigger complaints was that "push" calls to the Connect client only worked on calls dialed directly to an extension and not on hunt list calls. I am not sure if this is your problem. However, I thought this was changed and fixed in a release at some point.
IE...If your extension was 100 that you connected with Connect, an incoming call when the caller dialed extension 100 would "wake" the connect client via a push notification and ring even if Connect was running in the background, but if a call was directed to a huntlist that was configured to ring extension 100, it wouldn't ring to the connect client if the connect client was running in the background.