Looking at Hotdesking examples in this forum, I’ve only seen examples using some sort of IVR: the end-user dials some extension number, some extension or PIN code and the IP phone (s)he used is now binded to a new extension.
Looking at some IP phone’s documentation (for example Yealink doc), I see the end-user can use phone’s screen and keys to identify itself and trigger hot desking.
In this second case (the first one being the one involving an IVR), I fail to see how Asterisk could be directly or indirectly, be notified of any change.
In this case, is there some HTTP/API/whatever dialog that takes between IP phone and some server to listen to such HotDesking events and reconfigure whatever is needed to implement HostDesking ?
When talking about the seconde case, where you assume there is some HTTP/API/whatever dialog between the IP phone and some server, maybe ask this question in the forum of the phones or that server…?
If you want to ask a question related to Asterisk and hotdesking, maybe ask a clear question.
Because to me it looks like you have not asked a question related to Asterisk.
Unfortunately, this Yealink support topic seems to have been written by someone whose first language is not English, and probably is a technical author, rather than an implementer.
As such it would need some testing to confirm what it really means, but I think register_name is the AOR, and it is simply using the ability of physical devices to register under different names at different times, that it implicit in the SIP REGISTER system. If so, Asterisk does not need to be aware that each user doesn’t have a personal phone that they plug in at their desk.
In practice, Asterisk might require the user name and password to be changed at the same time as the register name, as the alternative would probably be to have every AOR that could be used, for the phone, listed for each phone.
In fact, if you don’t change both AOR and From User, unless the Yealink sends the AOR as a custom header, you would need dialplan to test on which endpoints the AOR was currently contactable. A custom header would allow the endpoint to be keyed on that header, rather than the, default, From user.
Before writing my original post, I read the mentioned Yealink document.
The way I understood it at the time is it allows an administrator to define the form displayed on phone’s screen after pressing a dedicated HotDesking key. Then I wondered what the expected username or password values could be.
Now thanks to your explanations, I think these expected username or password are simply the ones a phone must use to complete a registration dialog.
This implies that using this phone key-based method, either end users must know the password that match their own extension, or you must use the same password for a given extension group.