Reference:Configuration/Registration/Function-Keys/Hot-Desking: Difference between revisions
Jump to navigation
Jump to search
(New page: == 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 reg...) |
m (→Hot Desking) |
||
Line 2: | Line 2: | ||
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. With transition to state 0, the user is deregistered again. | 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. With transition to state 0, the user is deregistered again. | ||
===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. |
Revision as of 14:22, 30 August 2010
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. With transition to state 0, the user is deregistered again.
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.