Version 20.0 Update 3 Hot Desking

[VBS]

We recently upgraded our 3CX system from V18 to Version 20.0 U3 remotely. Post-upgrade, we tested all functionality successfully, except for Hotdesking.


When testing Hotdesking onsite, users encountered an "Access Denied" message when dialing the feature access code to log in. Despite attempts at troubleshooting—including a full reset, reboot, and remote provisioning of the handset—the issue persisted. The handset appeared correctly in the admin panel, and we could configure it via the Web GUI. However, this approach isn't practical for us, as staff frequently move between desks.

Has anyone else experienced a similar issue?

For now, we have reverted to V18 using our backups to restore functionality for staff. That said, we’re keen to get V20 implemented before the end of the year.

We're running 3CX on a Windows Server and using DHCP to distribute the provisioning template: http:/PBX/provisioning/AUTH and using Yealink T42S handsets on Firmware 66.83.0.55

Any insights would be greatly appreciated.


Thanks,

 

[Alphabetic]

You would have to check the event log realistically. Check your dial codes for hotdesking in case you're using a custom one and also check the user has hotdesking enabled, IPs arent blacklisted.

 

[VBS]

Thanks for getting back so quick as we had to start for the day, I needed to get us up and running. We had the code set to the usual *77* and the user was enabled for Hotdesking and couldn't see the device blacklisted I'll have to arrange another change window and try again.

 

[VoIPTools]

Try changing to a different dial code. There have been other reports that changing the dial code fixes the issue.