To program Hot Desking, you must:
Program a cluster ID (for nodal hot desking only)
Enable Hot Desking on supported multiline IP sets
Program the Hot desk users including phone keys
Program feature access codes (FACs) for login, logout, and remote logout (Optional)
Enable sets for remote logout (Optional)
Set a default device type for the Desktop Tool (Optional)
Hot Desking is supported on single nodes and on network clusters. To program Hot Desking on a single node, use the System Administration Tool. To program on a cluster, use OPS Manager.
IMPORTANT: If the host ICP is not part of a cluster (that is, it is a standalone system), you must assign it a PBX Number with the local IP address of the controller in the ICP/PBX Assignment form. Then, assign this PBX Number as the CEID in the Cluster Element Assignment form.
Hot desk sets are typically shared phones intended for hot desk users. When no user is logged in, it is recommended that the set provide only basic service such as emergency and operator calls. Supported IP sets are provisioned for Hot Desking by assigning the phone a COS that allows hot desk login and logout.
Hot desk users are assigned DNs and PINs through the Multiline
IP Set Configuration form. When programming feature keys for hot desk
users, keep in mind that hot desk user profiles support 13 programmable
keys. If a user logs in to a hot desk set that supports fewer than 13
feature keys
If one of these "inaccessible" keys is programmed as a line appearance, calls for the line appearance will still ring at the phone. To avoid "phantom" ringing on hidden line appearances, do one of the following:
Program only sets with 13 or more programmable keys as hot desk sets (5005 IP Phone, 5020 IP Phone, 5205 IP Phone, 5207 IP Phone, 5235 IP Phone, 5220 IP Phone and 5220 IP Phone (Dual Mode), 5224 IP Phone, 5324 IP Phone, and Navigator).
Restrict line appearances to Personal Keys 2 to 7. These keys are displayed on all supported phones.
Enable "ringing line select" in the COS for the hot desk user. This feature allows the user to answer any ringing non-prime line appearance (including those hidden) by simply going off-hook. If the user is already on a call, hidden line appearances are not accessible.
Note: To avoid confusion, it is recommended that you choose one device type supporting 13 programmable keys, program a consistent layout for the buttons, and provide printed button templates for each hot desk phone.
Remote logout is intended to allow administrators, attendants, or help desk personnel to log users out remotely. Remote logout is enabled on any device supporting feature access codes by assigning the phone a COS that allows remote logout.
Hot desk login is invoked by entering a feature access code or pressing a softkey. To allow login and logout on hot desk phones without softkeys, program feature access codes (FACs) for hot desk login, logout, and remote logout. To ensure that users can access all hot desk phones on a cluster, program the same FACs on each node in the cluster.
Resilient Hot Desking follows the existing licensing rules for Hot Desking and resiliency. The licensing and hardware requirements for a single user and a single phone are summarized in the following table:
|
|
Host (Primary) ICP |
Secondary ICP (Resiliency) | |
|
Hot Desk Set |
Device license |
1 |
1 |
|
User license |
1 |
0 | |
|
PLID |
1 |
1 | |
|
Hot Desk User |
Device license |
0 |
0 |
|
User license |
1 |
0 | |
|
PLID |
1 |
1 | |
For example, to program 350 hot desk sets and 350 hot desk users, you would require 350 device licenses and 700 user licenses on the host or primary ICP. However, to program 700 hot desk users on a secondary ICP, you would not require any user or device licenses. See About IP User and Device Licenses for more information.
