Default Call Control in Desktop App

[123doE8]

We have recently rolled our 3CX in our school and have come across an issue with the default call control preference in the desktop app.

Some of our users have Yealink T46U handsets alongside using the desktop app. Where a user has an IP phone assigned to them, the desktop app appears to default call control to the IP phone. In our environment i need everyone's default to be set to desktop app and they can choose to change it if they wish. People have already raised the issue that their IP phone initiates the call even if they are not in the room. This means the callee may overhear unintended private conversations that are happening in the same room as the IP phone. (Not good in a school).

I have ensured call control preferences are set to softphone in each user's extension information. I can see the client config.json change "UseCTI": to True or False but the desktop app doesn't seem to honour the setting. I know the app and phone no longer use CTI but CSTA instead but i have thought it would still honour the default device setting from the management console?

This issue also appears in the web client.

Is this expected behaviour or should the desktop app honour the call control preference setting from the management console?

Thanks

 

[Evolute IT]

UseCTI was used in the old Windows Client.

In my experience, the new app will choose an IP Phone first, then revert to Softphone/App mode.

 

[123doE8]

UseCTI was used in the old Windows Client.

In my experience, the new app will choose an IP Phone first, then revert to Softphone/App mode.

Ye that's exactly what's happening.
@Nick Galea is this something that can be addressed in the next updates? Would be beneficial for us if the call control preference default would work on the new windows desktop app.

Apart from this, our school wide roll out has gone brilliantly. Really happy with 3CX overall.

Many thanks