Reference9:Phone/User/Function-Keys/Hot-Desking: Difference between revisions
Line 3: | Line 3: | ||
If different subscribers often register with a particular telephone, this fast registration function can be used, whereby the access data is queried again with every registration. The access data consist on the subscriber Name, Number and Password, only Name or Number is required plus Password if defined on the User Object, if user insert the Number this must be the complete Number of the User Object including the Node Prefixes. | If different subscribers often register with a particular telephone, this fast registration function can be used, whereby the access data is queried again with every registration. The access data consist on the subscriber Name, Number and Password, only Name or Number is required plus Password if defined on the User Object, if user insert the Number this must be the complete Number of the User Object including the Node Prefixes. | ||
With transition to state 0 (using the same function key after registered), the user is deregistered again. | With transition to state 0 (using the same function key after registered), the user is deregistered again. | ||
When using this function the Telephone will try to subscribe at the PBX, first search for GK-IP Address on the DHCP Lease, if no GK-IP found it will search on local User-1 configuration and finally try to use Gatekeeper Discovery method. | When using this function the Telephone will try to subscribe at the PBX, first search for GK-IP Address on the DHCP Lease, if no GK-IP found it will search on local User-1 configuration and finally try to use Gatekeeper Discovery method. | ||
===User Config Stored at PBX=== | ===User Config Stored at PBX=== |
Revision as of 17:59, 26 January 2012
Hot Desking
If different subscribers often register with a particular telephone, this fast registration function can be used, whereby the access data is queried again with every registration. The access data consist on the subscriber Name, Number and Password, only Name or Number is required plus Password if defined on the User Object, if user insert the Number this must be the complete Number of the User Object including the Node Prefixes.
With transition to state 0 (using the same function key after registered), the user is deregistered again.
When using this function the Telephone will try to subscribe at the PBX, first search for GK-IP Address on the DHCP Lease, if no GK-IP found it will search on local User-1 configuration and finally try to use Gatekeeper Discovery method.
User Config Stored at PBX
The function "User Config stored at PBX" should be used if the registration that activates the hotdesking, stores its config in the PBX. Without this button the configuration of the second user(user executing the hotdesking) is modified and a 'Delete Registration' button is inserted at the position of the previous hotdesking button.
To prevent this, you must set the "User Config stored at PBX" option and configure manually an additional 'Delete Registration' button at the user executing the hotdesking. If the stored config contains itself a 'Hot Desking' key with 'User Config Stored at PBX' checked this key works as a 'Delete Registration' key in a hot desking registration.