Solved Hotdesking - STUN / Remote from Cloud PBX

[pact]

Why is the Hotdesking feature not available to remote/cloud extensions?

It works via Local or via SBC..

It's just dial codes and re-provisioning is it not?

 

[eddv123]

Hi pact,

The only reason I can think (other than security) is the way in which a STUN extension is provisioned the SBC and local provisioning use plug & play where a STUN extension requires the RPS method with additional username and password login which will be taken from an existing extension.

 

[pact]

Well we've just given it a shot via an SBC and the dial codes work, but the config does not push out to the phone.

So we end up with a handset which thinks its logged out, but in 3CX is showing as unprovisioned and you cannot login or logout with it.

So it again appears we cannot run hotdesking from a cloud instance.

 

[YiannisH_3CX]

Hello @pact

For HotDesking to work you need to provision the phone through Plug and play, so you need the phones to be local or behind an SBC and assign them to an extension. If the phones are not assigned through Plug and play then HotDesking will not work.

 

[pact]

So you are suggesting Plug and Play adoption does something different to the phone getting it's config via DHCP Option 66?

 

[YiannisH_3CX]

So you are suggesting Plug and Play adoption does something different to the phone getting it's config via DHCP Option 66?

Exactly: https://www.3cx.com/docs/hot-desking/

 

[bbaker73]

I understand the different provisioning and why it wouldn't work with remote STUN phones, but if I change theses remote phones to SBC for hot desking, why are CTI features only possible with the web client and not the 3CX client for Windows? The web client does not yet provide the overview in one screen and ease of managing the calls, queues and extensions like the client for windows does, so it is not yet a replacement.

 

[bbaker73]

Also, just my 2 cents, but more and more installs are going cloud and SBC is not always a viable option in all locations. Hopefully you guys will be looking at the future of how clients are going to installing more in the cloud and use remote STUN extensions, and adapt these features to work in those scenarios.

 

[StefanW]

We did and the pitfalls currently are to big to get a phone into a state where is it "lost" without admin recover action. From ext roaming onto a device which can not login from WAN to a device failing to optain the config. Hotdesking only makes sense if there is more then 5 devices in one location (in terms what HD should solve). And in this case an SBC is viable.