Reference9:Phone/User/Function-Keys/Hot-Desking: Difference between revisions

From innovaphone wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
== Hot Desking ==
== 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.
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 consists of the Name and/or Number and the Password (if any) defined in the User Object of the subscriber.
With transition to state 0 (using the same function key after registered), the user is deregistered again.
When the Number is used it must be the complete Number of the User Object including the Node Prefixes.
The registration is tried first with the GK-IP Address provided via a DHCP Lease, second with the GK-IP configured for User 1 and finally via Gatekeeper Discovery.


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.
How hot desking can be used depends on "Store Phone Config" checkmark in the user objects of the intended subscribers.
If it is not checked the user specifig configuration is stored locally on the phone, otherwise it is stored on the PBX.


===User Config Stored at PBX===
==="Store Phone Config" NOT checked===
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.
Pressing the "Hot Desking" key creates a new local user configuration with a "Delete Registration" key at the same position as the "Hot Desking" key.
The "Delete Registration" key inherits the Text/Icon/LED setting as defined under "Active State" of the "Hot Desking" key.
Pressing this key will end the hot desking session.
 
==="Store Phone Config" checked===
 
In this case "User Config stored at PBX" must be checked for the function key to prevent changes of the configuration stored on the PBX.
The "Hot Desking" key will be functional only in the primary registration.
Pressing the key creates a new registration without any modifications of the configuration stored on the PBX.
To delete a registration created this way a "Delete Registration" key should be provided in the stored configuration,
otherwise the registration can be deleted only via the phone menu.  
If the stored configuration contains itself a "Hot Desking" key with "User Config Stored at PBX" checked,
the key works as a "Delete Registration" key in a registration created via hot desking.

Revision as of 12:08, 28 March 2013

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 consists of the Name and/or Number and the Password (if any) defined in the User Object of the subscriber. When the Number is used it must be the complete Number of the User Object including the Node Prefixes. The registration is tried first with the GK-IP Address provided via a DHCP Lease, second with the GK-IP configured for User 1 and finally via Gatekeeper Discovery.

How hot desking can be used depends on "Store Phone Config" checkmark in the user objects of the intended subscribers. If it is not checked the user specifig configuration is stored locally on the phone, otherwise it is stored on the PBX.

"Store Phone Config" NOT checked

Pressing the "Hot Desking" key creates a new local user configuration with a "Delete Registration" key at the same position as the "Hot Desking" key. The "Delete Registration" key inherits the Text/Icon/LED setting as defined under "Active State" of the "Hot Desking" key. Pressing this key will end the hot desking session.

"Store Phone Config" checked

In this case "User Config stored at PBX" must be checked for the function key to prevent changes of the configuration stored on the PBX. The "Hot Desking" key will be functional only in the primary registration. Pressing the key creates a new registration without any modifications of the configuration stored on the PBX. To delete a registration created this way a "Delete Registration" key should be provided in the stored configuration, otherwise the registration can be deleted only via the phone menu. If the stored configuration contains itself a "Hot Desking" key with "User Config Stored at PBX" checked, the key works as a "Delete Registration" key in a registration created via hot desking.