Hot desking users can not log in or log out

[Lee Cramman]

V18 on GCE, 2 sites each with with SBC's currently on the 18.0.30 beta.

Since this morning none of our hot desking users from either site can either log on or off, they get the "Access denied" message.

Users currently logged in can still use their phones fine. Extensions directly assigned to a user work fine. Manually logging a user off from the admin portal means they no longer show as logged in on the portal but still appear to be logged in on the phone (although their phone no longer works at that point).

I'm scratching my head a bit here as to where to even start troubleshooting this as I've never come across the problem before.

There have been no recent changes to our overall setup or networking other than an update of the SBC's but we have been running for several days without issue since that update.

 

[Lee Cramman]

Did a complete server rebuild as advised by support.

Yealink T41P and T21 E2 phones are still unable to provision despite being on the correct firmware as advised by 3CX.

If affected phones are rebooted they show up (upnp) via the SBC in the list of phones but you can't go any further than that in terms of provisioning.

Where on earth do I go from here?

Against my better judgement and out of sheer desperation I'm considering editing the hot desking template manually but I don't know where it's located (although I can locate the 'normal' templates). Even then, it's going to mean manually changing the settings on each phone to enable the initial provisioning .

 

[Charles_3CX]

This may still be an issue as mentioned the phones are currently not accepting the new root certificate from let’s encrypt, we are still looking in to this but as far as the error is concerned when accessing the webclients and management console, has this now resolved after reinstalling?

 

[Lee Cramman]

This may still be an issue as mentioned the phones are currently not accepting the new root certificate from let’s encrypt, we are still looking in to this but as far as the error is concerned when accessing the webclients and management console, has this now resolved after reinstalling?

Only some PC's were affected which I don't have access to today (working from home).

Any idea if there is an incoming fix and what the timing might be? About 60% of our endpoints are dead in the water.

 

[weimerd]

Same issue here with hotdesking. But with Fanvil X3S. Whole office can't login on hotdesking phones.

Any solution here? We are using Fanvil X3S with latest 3CX firmware. SBC latest. Latest 3CX 18 beta.3CX system runs on Azure.

Fun fact: One phone is logged in but can't logoff anymore.

 

[Charles_3CX]

Please keep an eye on this thread where there will be more updates: https://www.3cx.com/community/threads/certificate-error-yealink.84628/

 

[Lee Cramman]

This may still be an issue as mentioned the phones are currently not accepting the new root certificate from let’s encrypt, we are still looking in to this but as far as the error is concerned when accessing the webclients and management console, has this now resolved after reinstalling?

I can confirm that rebuilding the server did not fix the certificate problem with the web client.

Some research led me to this:

https://docs.certifytheweb.com/docs/kb/kb-202109-letsencrypt/

And if you look at the section under "Windows PCs" you'll find that when this problem occurs simply visiting the website https://valid-isrgrootx1.letsencrypt.org/ without taking any further action updates the browser certificate chain, fixing the problem. I can confirm that this fix worked.

 

[Charles_3CX]

A fix has been released, see here for details:https://www.3cx.com/blog/releases/lets-encrypt-expiration/