Closing webclient browser without using WebClient Logout leaves extension status Online

[AlecM]

Version 20.0 Update 2 (Build 715 Release).

When a user closes their web browser while using the WebClient and doesn't use the WebClient Logout function from the WebClient account menu, this leaves their extension status as online (e.g. as Available), when they are not.

Is there an admin setting required to be enabled to detect this type of disconnection and force the extension back to "unregistered" status? Haven't seen anything obvious relating to this in my hunting around the admin pages...

 

[NikolasA_3CX]

Hi @AlecM

The user needs to logout for the extension to show as unregistered.
Click the status icon and click logout.

 

[AlecM]

Hi @NikolasA_3CX ,

Yes, we know that, thanks. The concern is when users don't follow this simple process and just close their browser, because that's what they're habituated to doing, no matter how many times we tell them to use the supplied logout or sign out functions on all web apps they use (not just 3CX).

I guess the point I'm making is that I'm wondering if there isn't some underlying "ping" type mechanism (perhaps not constant, but 10 sec intervals or whatever to cope with patchy internet connections) from the browser to the 3CX server that says that client is online - and if it stops, and no other device for that extension is online, the extension should drop to unregistered.

I thought it might just be a setting I was missing seeing in the admin console.

 

[NicholasP_3CX]

The Web Client is considered an end point, so it is treated as such. The client would be able to receive calls through its notifications.

It is not intended to be like a banking application for example where you close the browser it just dumps the sessions. It's just the nature of the application as such