- Joined
- Feb 11, 2019
- Messages
- 68
- Reaction score
- 6
-=setup=-
PBX Debian 18.0.1863 & 16.0.8.9 & 16.0.655
3cx mobile 16.7.8.121 & 16.6.2.89
-=Settings=-
Battery Optimizer is off.
3cx set to "Not Optimized".
Data is set to unrestricted.
Phone Bluetooth is on.
3CX - Car Connect / Bluetooth settings are disabled.
-=Devices=-
Phone 1
Brand: Ulefone
Model: Armor 8 Pro
OS: Android 11
Phone 2
Brand: Doogee
Model: S58 Pro
OS Android 10
-=Background=-
We are demoing some new phones for our manufacturing plant and have run into trouble with call notifications appearing properly. These are WIFI only devices and will never have a SIM card. I have seen several threads with similar topics but I haven't found a solution that works for us. Many threads do no include a solution and end in a 3CX support person working things out with the poster in private, others say to update to Version X, or disable this setting and that solves the issue. So far I have tried all the setting suggestions and i have updated to and past the suggested versions on both the PBX and mobile version.
I started testing with our current active server but then I built a brand new test server with a free license to make sure that it wasn't something in our PBX settings and to try different versions. I listed the versions I test on. I joined the Beta program and it says I have the latest version installed for both server and mobile.
-=Problems Phone 1=-
3CX will loose connection, say reconnecting, WIFI and Bluetooth turn off then back on, and 3CX will reconnect. This doesn't happen with any other app on the phone that runs in the background or uses wifi. Its not very common but its a lengthy refresh and it shouldn't happen.
Upon opening 3cx or after unlocking the screen, barring total app disconnect as mentioned above, incoming calls will audibly ring but will only show the incoming call if the screen is not locked. If the screen is locked the phone rings, the screen wakes, but displays no method of answering except for in the notifications pull down menu. This happens regardless of whether the app is open in the background or has been cleared and is just running cached. If the screen is on it always shows a pop up at the top to Drop or answer. Side note why is there no longer a send to voicemail options here?
-=Problems Phone 2=-
3CX always displays the incoming call notifications when the screen is locked, but sometimes the pop up doesn't show when the screen is unlocked regardless of app open or cached.
When making a call a new app window opens and blocks the normal call interface. There is a contact head picture for the person you are calling and a red button to end the call but pushing either does nothing. Pressing back button or using task view to go back to 3cx will return to the normal call interface and the new windows will disappear. Closing the window with the task view has no affect on the call. This is mostly annoying and has given users that already don't like the app more reasons to not like the app and complain.
-=Other Notes=-
I have tried to test this with an older Android phone running 3cx 16.0.0.35 and these issues do not happen. doesn't matter much because its the legacy version and it doesn't work on Android 10 or 11.
I tested on iPhone and it didn't have any of the above issues.
PBX Debian 18.0.1863 & 16.0.8.9 & 16.0.655
3cx mobile 16.7.8.121 & 16.6.2.89
-=Settings=-
Battery Optimizer is off.
3cx set to "Not Optimized".
Data is set to unrestricted.
Phone Bluetooth is on.
3CX - Car Connect / Bluetooth settings are disabled.
-=Devices=-
Phone 1
Brand: Ulefone
Model: Armor 8 Pro
OS: Android 11
Phone 2
Brand: Doogee
Model: S58 Pro
OS Android 10
-=Background=-
We are demoing some new phones for our manufacturing plant and have run into trouble with call notifications appearing properly. These are WIFI only devices and will never have a SIM card. I have seen several threads with similar topics but I haven't found a solution that works for us. Many threads do no include a solution and end in a 3CX support person working things out with the poster in private, others say to update to Version X, or disable this setting and that solves the issue. So far I have tried all the setting suggestions and i have updated to and past the suggested versions on both the PBX and mobile version.
I started testing with our current active server but then I built a brand new test server with a free license to make sure that it wasn't something in our PBX settings and to try different versions. I listed the versions I test on. I joined the Beta program and it says I have the latest version installed for both server and mobile.
-=Problems Phone 1=-
3CX will loose connection, say reconnecting, WIFI and Bluetooth turn off then back on, and 3CX will reconnect. This doesn't happen with any other app on the phone that runs in the background or uses wifi. Its not very common but its a lengthy refresh and it shouldn't happen.
Upon opening 3cx or after unlocking the screen, barring total app disconnect as mentioned above, incoming calls will audibly ring but will only show the incoming call if the screen is not locked. If the screen is locked the phone rings, the screen wakes, but displays no method of answering except for in the notifications pull down menu. This happens regardless of whether the app is open in the background or has been cleared and is just running cached. If the screen is on it always shows a pop up at the top to Drop or answer. Side note why is there no longer a send to voicemail options here?
-=Problems Phone 2=-
3CX always displays the incoming call notifications when the screen is locked, but sometimes the pop up doesn't show when the screen is unlocked regardless of app open or cached.
When making a call a new app window opens and blocks the normal call interface. There is a contact head picture for the person you are calling and a red button to end the call but pushing either does nothing. Pressing back button or using task view to go back to 3cx will return to the normal call interface and the new windows will disappear. Closing the window with the task view has no affect on the call. This is mostly annoying and has given users that already don't like the app more reasons to not like the app and complain.
-=Other Notes=-
I have tried to test this with an older Android phone running 3cx 16.0.0.35 and these issues do not happen. doesn't matter much because its the legacy version and it doesn't work on Android 10 or 11.
I tested on iPhone and it didn't have any of the above issues.