3CX Desktop App v18 not registering as phone in webclient

[RobertGijsen]

Hi. I've looked all the way back up to july posts, but can't find anything related, yet I can't believe no-one is having this issue. Either that, or we are missing something trivial but crucial.

We and our customers use RDS environments. Mapping audio through RDS works, but there will be annoying delays. For that reason we always used either the Chrome extension within RDS sessions (my god we miss that...) or we installed the 3CX Phone V16 locally, and access it from the RDS session with either the Chrome extension or in V18 just the webinterface:



This is a screenshot from the webinterface where the LOCALLY running 3CX app V16 is selected as 'output device' (CTI?) and that works perfectly.

However, when I use the V18 3CX Desktop App, it doesn't register as such. Probably it registeres under 'Browser' as this uses the Electron framework. If that's the case, it correlates to a previous thread of mine at https://www.3cx.com/community/threa...-to-select-the-correct-one.78563/#post-360823, which I never got a proper answer or solution on. Browser is already registered because of we logged in to the webgui in the first place, so the second 'browser' is nowhere to be found.
Anyway, with V18 installed, this is what we see:




The desktop app is nowhere to be found. How to get this to work? How do other RDS or Citrix users work with this? We can't be the only one?

[offtopic]
Apart from that, while I like the V18 app GUI over the V16 one, I really don't understand the move to Electron. It's probably more cost effective to develop for multiple OS'es, but just like Teams and other Electron apps, 3CX got way more resource intensive.
Also, we're not (without any hacks that is) able to install the app in program files anymore, like a proper Win32 app should. In stead, in stead this became one of those dreaded apps that install in appdata\local, which just hogs the user profiles. Imagine you have 20.000 users all requiring at least 250MB of additional space in their profile opposed to just a proper 'program files' installation with only the config in the users profile. Let alone if you use old-skool roaming profiles for simplicity reasons. Why?

 

[VasilisV_3CX]

Hi @RobertGijsen,

There's no reason why you can't continue to use the 3CX Windows Client, it hasn't been deprecated or replaced by the Desktop App, therefore you can continue as you did before.

 

[RobertGijsen]

That was not an answer to my question. Our own 3CX server has been upgraded to V18, and hence (?) it now servers the 3CX app v18, rather than the v16 one. While usually we deploy the client for customers (using whatever deployment method) sometimes customers install it themselves, especially when they work from home. And the V18 client does not work anyway in the way we worked for several years now.

So apart from workarounds, will the V18 app behaviour OR webGUI behaviour change so V18 app can be used from the webconsole? Or is there some possibility to have the V18 app show up there as expected?

 

[VasilisV_3CX]

Hi @RobertGijsen,

will the V18 app behaviour OR webGUI behaviour change so V18 app can be used from the webconsole? Or is there some possibility to have the V18 app show up there as expected?

No, as far as I'm aware this is not something that is in our immediate plans.

 

[RobertGijsen]

Ok, then how can we get V16 served with V18 server again? As this is simply a huge way back in functionality.

 

[VasilisV_3CX]

Hi @RobertGijsen

Our own 3CX server has been upgraded to V18, and hence (?) it now servers the 3CX app v18, rather than the v16 one

There are a few different apps at play here. Let me define them so hopefully this makes more sense.

1. Desktop App - new to v18 PBXs. Only usable by v18 PBXs.
2. Windows Client - This is the same client as you used to use. You can still use this one by downloading the provisioning file sent in the Welcome Email by a v18 PBX.

 

[RobertGijsen]

Ok, that's a terrible solotion to an issue that shouldn't have to be there. In addition, as a backtrack to https://www.3cx.com/community/threa...-to-select-the-correct-one.78563/#post-360823 and the issue in this thread as well that multiple devices register with the same name and hence can't be selected. That's a major issue for us. This means if we have 3cx app v16 installed within RDS, we can't use 3cx app V16 on the local client. We can only connect to a deskphone, as the 3CX app registers under the same name. Now, with V18 app locally installed, we can't select THAT when customers use the webinterface as it registers under the same name.

Why can't it be made so it registers twice with some identifier like hostname or something unique to the system it runs on? There's quite some combinations of clients now that simply don't work when using Citrix or RDS. For 'the most versatile' solution, I think that's rather limiting. As a part-time programmer I feel this could be a very simple fix.