Separate names with a comma.
Discussion in 'Clients' started by Bianca, Dec 12, 2017.
Continue reading the Original Blog Post.
Installed the December 14th Android client release on a Samsung S8, it could not initialize, sent it the install file via email, cant load it. Uninstalled and re-installed, same. Have no client now.
Please do the following:
1) Use QR Provisioning to provision your device via the QR code provided in your WebClient.
2) If you really want to provision using the configuration file, some manual work is required. You'l need to install a file manager like "Total Commander", find the config file, tap it and select "Open with 3CX".
The config file cannot be loaded by your native Android file manager as it doesn't know that this file must be opened using the 3CX app. In the end this more of an Android OS issue which doesn't allow associating our 3CX configuration file with the 3CX app.
We're hoping that will be possible/allowed for Android developers one day.
Let me know if you need further help on this.
Was finally able to get the phone provisioned using only the QR code but only while on WiFi on our local network. It still will not work at all on the cellular network like it did before this December 14th update. It's now useless to all our sales people.
Before the December 14th update it worked fine, why change it?
We changed nothing in terms of provisioning. We only added QR provisioning. Nothing more.
What are you referring to? There's 3 replies all with different questions. Please clarify what you're asking exactly.
Is it also possible to bring back or make CTI work in the windows app when using hotdesking? And use the onboard mic and speakers when using the webclient?
Because that's how android works, it say the update and auto updated.
Well not sure what happened then, before that update it worked wonderful on WiFi and Cellular networks. After that update it would not accept the config file sent from the welcome message and when configured using the QR code it no longer works on the cellular network making it useless for us. I don't see why you needed to remove the config file from the welcome message as a configuration item, that worked well for people (we don't use the web interface at all because everyone needs to remember yet another password and they prefer the app... or did)
Does we have an update when 3cx Windows Client can schedule a conference call instead of logging on 3cx WebClient with user extension?
Having to logon twice is confusing and waste of time and most user does not what their web client login password.