Controlled phones and profiles of a user

What it is for

In the CUCM every user has a list of controlled devices. Only these devices can the user control remotely with Jabber or a CTI application, see in the Self Care Portal and manage in the EasyUC enduser portal. A phone can carry a number of the user and still not belong to this list, for example after it was created directly in the CUCM.

The user profile therefore shows all devices that carry a line of the user and separates them into controlled and not controlled. Devices that are not controlled carry the Not controlled badge. With one click you add the device to the controlled devices. Existing assignments of other users are kept.

For device profiles EasyUC sets three assignments at once: controlled device, controlled profile for Extension Mobility and CTI controlled device profile. Only with all three is a profile considered fully assigned.

Prerequisites

Licence module cucm.
Access to the user profile (ROLE_APP_VIEW_ENDUSER_PROFILE) and to the device list (ROLE_APP_VIEW_ENDUSER_PROFILE_DEVICE or ROLE_APP_VIEW_ENDUSER_PROFILE_DP_LOGIN).
For assigning: ROLE_APP_UPDATE_ENDUSER_CONTROLLED_DEVICE or ROLE_APP_UPDATE_ENDUSER. Accounts with ROLE_APP_READ_ONLY do not see the button unless they have an administrator role.
The phone is in a location that your account may access.
The device carries a line of the user. Only then does it appear in the profile among the devices that are not controlled.

Step by step: define a phone as controlled

Open EasyUC Cisco → Users → Users and click the card of the user.
Switch to the Phones & Phone numbers tab in the profile.
Find the phone in the group Other phones with numbers of this user. Devices that were found only through a shared line are in the collapsed group Phones with shared lines. Expand the group with a click on the heading.
In the row of the phone, check the entries Controlled by and Owner. If another user is named there, clarify whether both should control the phone.
Click Assign to this user.
Read the prompt Add phone to controlled devices?. It names the phone with its model, the users who control it so far and the consequences for Jabber, enduser portal and busy trigger.
Confirm with Assign to this user. With Cancel everything remains unchanged.
Wait for the message that the phone is now controlled by the user. The phone moves to the group Controlled phones.

Step by step: define a device profile as controlled

Open the Phones & Phone numbers tab in the profile of the user.
Find the device profile. Profiles carry the Device Profile badge and three indicators: Controlled Device, Controlled Profile and CTI Controlled Device Profile.
If at least one of the three indicators is missing, click Define as controlled profile.
Read the prompt. For profiles it additionally contains the note that the profile is also assigned as EM and CTI profile.
Confirm with Define as controlled profile.
Check that all three indicators now show a green tick.

Fields and options

Fields and options
Field / action	Meaning and use
Controlled phones	First group of the device list. Contains controlled phones, the user's own remote destination profiles, Teams devices of the user and the user's own device profiles. If the group also contains profiles, it is called Phones and profiles of this user.
Other phones with numbers of this user	Devices that are not controlled and carry the primary number or the phone number of the user.
Phones with shared lines	Devices that are not controlled and were found only through a shared line of a controlled device. Collapsed initially.
Not controlled	Badge on devices that are not assigned to the user as a controlled device in the CUCM.
Controlled by	Users who currently control the device. nobody means that no user is assigned.
Owner	Owner User ID of the device in the CUCM. Control and ownership are separate attributes.
Assign to this user	Adds a phone to the controlled devices of the user (assignment as controlled device).
Define as controlled profile	Sets all three assignments for a device profile: controlled device, controlled profile and CTI controlled device profile.
Logged in on	For device profiles: the phone on which the user is logged in with this profile via Extension Mobility.
Outside your locations	Replaces the device name if the device is in a location that your account cannot access. Actions are then not possible.
Consequences of the assignment	The user can control the phone via Jabber/CTI and Self Care. The phone appears in the user's enduser portal. The user's busy trigger will in future set all lines of this phone. On the user card of the overview the device appears as a tile.
Jabber device of another user	Additional note in the prompt if a softphone belongs to another owner. The assignment can interfere with that owner's device selection in the client.

Check the result and troubleshoot

Success: the message names phone and user, the Not controlled badge disappears and the device is in the first group. In the CUCM the device is listed among the controlled devices of the user.
Remote destination profiles are assigned via the owner: there is no button for remote destination profiles. Set the user as owner of the profile.
Gateway ports cannot be controlled: analogue ports of a gateway cannot be assigned as a controlled device.
Device profile of another user: the profile already belongs to another user and cannot be assigned additionally.
The phone is outside your locations: your account has no access to the location of the device. An administrator with access must make the assignment.
The phone no longer exists on the CUCM or The end user no longer exists on the CUCM: the object has been deleted in the meantime. EasyUC reloads the list.
The CUCM rejected the change: the error message of the CUCM follows. Check the AXL permission and the state of the device.
Invalid request: reload the profile with Refresh and repeat the operation.
The button is missing although Not controlled is displayed: the role is missing, the account is read-only, or the row shows one of the blocking reasons named above.
After the assignment the Delete button for the user is missing in the profile. A user with controlled devices is considered configured.
This view has no button for removing the assignment. If required, remove an assignment directly in the CUCM on the user.