Desktop app disconnecting and having to manually provision again

[CybertronIT]

Hi all,

I recently upgraded one of my clients to Version 20 on a on-premises machine, hosting the 3cx system as a Debian Linux VM on Hyper-V.

We noticed that before the upgrade and after the upgrade the new V20 desktop application from the Microsoft Store will disconnect and not reconnect until you manually provision it from the webclient.

Anyone facing a similar issue? Wondering why the client will disconnect and not reconnect as the 3cx phone system has been working fine so far in terms of general usage / calls, issues only with the desktop application itself. My client has a high preference for the old V16 desktop application due to some missing features but I note to them that the older versions will no longer work in due time, so I'm trying to figure out what is the issue with the new client.

 

[Ibby-WaveLengths]

@CybertronIT - we have had this issue with a user at one of our clients just today, where the Windows SoftPhone lost connection after a receiving a call and making a call (max of 2 calls, then "Disconnected, check your connection." will show); but the internet connection itself was still functional.

Turns out that there was a custom DNS server in the IP configuration settings - for the laptop's docking station network adapter - being applied. Changed it back to automatic and had to restart the device for the changes to take effect.

Hopefully this helps

 

[SteveITS]

@CybertronIT There’s this thread but your symptoms sound different: https://www.3cx.com/community/threads/3cx-windows-app-sometimes-in-semi-live-state.131363/