Using two 3CX Windows clients - unable to select the correct one

[RobertGijsen]

Hi, this is related to https://www.3cx.com/community/threads/challenge-with-tapi-vs-rds.78240/ butI got no answer at all there.

We do RDS service for a variety of customers.Some of them want Outlook integration and / or CRM integration which in this situation is an on-premise (on the RDS) installed CRM application that works with TAPI. So we installed the MultiLine TAPI driver on the RDS, which works (ish) but it requires the 3CX Windows client to be installed. However, the customer wants to use the 3CX Windows Client installed on their local PC for the actual calls. The issue is that in the Windows Softphone, you cannot select WHICH softphone you want to use for calls. In the Chrome Webextension though, multiple Windows Softphones show up and that works perfectly fine.

We would make some customers very happy if the Windows client got that ability as well.

Even better might be if we were able to select the Chrome Extension in the 3CX Windows client, so users can start the webextension whereever they are, and use that from the RDS. Way less cumbersome than installing the 3CX client on their home pc's, especially in these lockdown times...

Would that be a feasible feature request?

[edit]
It now occurs to me that the 3CX software installed on smartphones is also not selectable in the Windows client, EXCEPT when I use a third party SIP softphone, like Zoiper. That shows up and works fine in the Windows client, but the 3CX Smartphone client does not.

 

[NickD_3CX]

Hi there!

Another way I could thing is, in the RDS environment, set the 3CX Windows Client to CTI mode.

This means that any calls made by the Windows App, will trigger an incoming "MakeCall" towards any other clients that are registered to this extension.
Once answered, the call will be connected to the destination number you dialed.

This means that if your in the RDS on the Windows app you have Ext 100 in CTI mode, and the users have their WebClient open and logged in with Ext 100 on their local PC, whenever a call is triggered from the Windows App, they will see an incoming call on the WebClient from "MakeCall". Once they answer, they will be connected to the dialed number.

 

[RobertGijsen]

How? When I switch the Windows client to CTI, I MUST select a phone - and the webclient is not one of them (it was active while the screenshot was made). When I select one, the webclient does not respond when I make a call, only the selected phone does.

:

[edit]
btw it translates to: 'there are multiple CTI IP phones registered with extension number 002. Select the device you want to use in the list below'

 

[NickD_3CX]

I see, in that case, why not select on of the devices? If users have registered IP Phones, why not use them for this purpose?

 

[RobertGijsen]

hmm rather than editing my previous post I post a new one - it turns out regardless of which CTI phone I select, indeed the Chrome extension shows the make-call message as well. Even when no deskphones are registered and the Windows app reports: No phones connected, the Webclient still received the call.

BUT! It does NOT make any sound, at least on my test systems and sometimes the screen doesn't pop up in front of all the rest on screen. Can notification sounds be enabled for that?

Thanks, this is at least a step in the good direction and I can't believe I never ever noticed the makecall from actually being picked up by the webclient.

I tested with a locally installed Windows client as well, actually 2 deskphones, 2 Chrome extensions and 2 Windows clients, and all receive the make-call message. I have tested this hours and hours before and it just would NOT work. However, a few days ago I received v16.3.0.198 of the Windows client. I hadn't tried it with that new version yet. I'm pretty positive it just didn't work before. It's just enabling whatever client actually, and setting the Windows client to CTI. Which is what we did in the first place, as we don't want to use the Softclient anyway...

Anyway, for now it seems to be usable. Thanks for the heads up!

 

[RobertGijsen]

I see, in that case, why not select on of the devices? If users have registered IP Phones, why not use them for this purpose?

apart from the message above (seems to be fixed in Windows Client 16.3.0.198) this is my test-setup, where I have two deskphones connected. But the customer I'm working this out for wants to get rid of ALL deskphones save the receptionist one.

 

[NickD_3CX]

BUT! It does NOT make any sound, at least on my test systems and sometimes the screen doesn't pop up in front of all the rest on screen. Can notification sounds be enabled for that?

I think you may want to check the Audio Settings of your WebClient and check that "Ringer" is set to the correct output device. I tested it locally just now and I did hear sound.

apart from the message above (seems to be fixed in Windows Client 16.3.0.198) this is my test-setup, where I have two deskphones connected. But the customer I'm working this out for wants to get rid of ALL deskphones save the receptionist one.

When this happens, when the Windows Client lanches, it will not prompt at all the user to select a device, so it should be much more straight forward for the user to switch to CTI.