Associate and Disassociate Devices to Application Users#
High level admins can make available a utility to associate and disassociate devices to CUCM application users so that it displays on administrator menus on the GUI.
Important
The utility is available only at site level, so that only devices and device profiles at that level are available for management.
The utility simplifies the association and disassociation of a large number of
Phones, CTI Route Points, or Device Profiles to app users (device/cucm/AppUser
).
This would for example be in the case of large contact center deployments.
The model to expose on the administrator menu layout is view/AddRemoveDeviceAppUser
.
Access Profile updates are needed for the default administrator access profiles.
Select an Application User to manage.
The list of application users are those at and above the current site hierarchy.
You can associate Devices and Device Profiles with the same application user by means of side-by-side transfer boxes.
Choose the Action: either to associate or disassociate devices or device profiles.
When associating, only devices or device profiles not associated to the user at the current hierarchy are shown in the Available transfer box.
When disassociating, only devices or device profiles associated to the user at the current hierarchy are shown in the Available transfer box.
Optionally, add a substring filter in the Filter Devices or Filter Device Profiles.
Manage the items in the Available and Selected transfer boxes.
Note
Since the transfer boxes can only list 200 items, filters should be chosen to manage more items. The filter uses the “contains” case insensitive method. A notification is however displayed showing the total number of items.
In the Admin Portal, a filter is available within the transfer boxes. This filter only applies to the 200 items (or less) within the transfer box.
Save your changes.
Inspect the transaction log to verify the action. The Detail message includes the username of the app user.
Note
A database lock is used in the resulting transaction in order to ensure parallel transactions do not conflict.
Related Topics
For details on customizing menu layouts, see Create a Menu Layout.