Hi. My previous question just got deleted, as it contained a request. But another question in that post still stands so I'll distill that.
All our customers use RDS. In the past, we installed 3CX client v16 locally on their desktop where their headset is connected, which they could control from the webclient in their remote session. However, the V16 client is starting to lack, for example no real proper support for the Yealink headsets (yes I know there is some sort of plugin). The V18 app has better support for headsets, but the huge issue here is that it registers itself as 'Browser', probably because it's an electron app now. And then the same issue occurs as when you would start a webclient within an remote session and another webclient locally where your headset is connected - the webclient can't distinguish between the local and remote browser, both are called 'Browser' and you can't select a specific one. This means within an RDS environment it's not possible to use the webclient to call locally using the locally running V18 client, or another browser for that matter, as they both register under the name 'Browser'.
I've seen several people with similar issues on RDS on the forum, and the answer was 'the V16 app is not deprecated yet'. And while that might be true, there is no real future in that as its lacking support the new client has, and obviously the way forward is V18 (else why was it released). And I don't see an eventual V19 version being moved away from Electron again. This makes it harder and harder for us to see 3CX as a proper solution in RDS environments.
I quote from https://www.3cx.com/blog/releases/v16-update8a-beta/:
Both are not really viable. staying on v16 will sooner or later be unsupported obviously, and using V18 breaks the ability to control your locally running client from an RDS or Citrix setup.
So, my question here is, in the light of the future of V18 and upwards, how do people use 3CX in conjunction with RDS or maybe Citrix?
All our customers use RDS. In the past, we installed 3CX client v16 locally on their desktop where their headset is connected, which they could control from the webclient in their remote session. However, the V16 client is starting to lack, for example no real proper support for the Yealink headsets (yes I know there is some sort of plugin). The V18 app has better support for headsets, but the huge issue here is that it registers itself as 'Browser', probably because it's an electron app now. And then the same issue occurs as when you would start a webclient within an remote session and another webclient locally where your headset is connected - the webclient can't distinguish between the local and remote browser, both are called 'Browser' and you can't select a specific one. This means within an RDS environment it's not possible to use the webclient to call locally using the locally running V18 client, or another browser for that matter, as they both register under the name 'Browser'.
I've seen several people with similar issues on RDS on the forum, and the answer was 'the V16 app is not deprecated yet'. And while that might be true, there is no real future in that as its lacking support the new client has, and obviously the way forward is V18 (else why was it released). And I don't see an eventual V19 version being moved away from Electron again. This makes it harder and harder for us to see 3CX as a proper solution in RDS environments.
I quote from https://www.3cx.com/blog/releases/v16-update8a-beta/:
Both are not really viable. staying on v16 will sooner or later be unsupported obviously, and using V18 breaks the ability to control your locally running client from an RDS or Citrix setup.
So, my question here is, in the light of the future of V18 and upwards, how do people use 3CX in conjunction with RDS or maybe Citrix?
Last edited:
