Reassign Services¶
The Reassign Service feature directs you to the Customer hierarchy (if you are not already there) because it supports target users that are on a different site as the source user.
Field Name |
Comment |
|---|---|
Reassign Service Profile |
This field will pre-populate with the first profile. You can select a different profile if required. If no profile option is available, then a reassign service profile needs to be added in the system. |
Source User |
Choose the subscriber to be reassigned. This provides a list of usernames of Subscribers in the system. It will list local or CUCM-LDAP Synced Subscribers only (not VOSS-LDAP Synced). Once a subscriber is selected, the Source User Services tab is updated to show services currently assigned and that will be reassigned to the target user. This is a good way to validate that all the services are shown or that there are not services that you do not want reassigned. |
Source User Hierarchy |
Once a subscriber is selected the Source User Hierarchy will be populated - this is a read-only informational field. |
Add A New Target User |
Select this option if you need to add a new local user to the system as the target user. Once selected, the form updates to reflect this choice. |
Target User |
To reassign to an existing user: select the username from the dropdown. This will show local or CUCM-LDAP synced users at the customer level or lower. Once a user is selected, the Target User Services tab is updated to reflect any services currently assigned to the user. If the user has any entries on this tab then the transaction will be blocked. So this provides an option to check before submitting. To create a new target user: enter the username for the new user to be created. The user will be added to the same hierarchy as the source user. |
Target User Hierarchy |
Shown only if add new target user is not selected - read-only informational field. Shows the hierarchy of the selected target user. Can be different to the source user and the feature will move the target user to the same hierarchy as the selected source user. |
First Name |
First Name of the Target user. Will be read only if the target user is a LDAP synced user. |
Last Name |
Last Name of the Target user. Will be read only if the target user is a LDAP synced user. |
Email Address |
Email Address of the Target user. Will be read only if the target user is a LDAP synced user. |
Password |
Visible if the target user is not a LDAP synced user. Enter the password for the target user. |
Pin |
Enter the PIN for the target user (used for device profile and voicemail). |
Notes:
The feature requires that source user services should all be at the same site hierarchy.
Target user and hierarchy:
New target user - will be added to the hierarchy of the source user.
Existing target user - If the target user is in a different hierarchy to the source user, the target user will be moved to the same hierarchy as the source user as part of the reassign of services.
Note
It is not possible to reassign services to a user who is on a different Unified CM Cluster than the source user. The target user dropdown will currently not show users on a different cluster.
The Source User Services tab will populate once a source user has been selected. This shows the services currently assigned to that user and the services that will be reassigned. This is a good way to validate the services that will be reassigned and to check if there are any services missing or that should not be reassigned. This can then be corrected as needed before reassigning the services.
The Target User Services tabs will populate once a target user is populated. This is a good way to validate that the target user does not currently have any services assigned, as this will cause the transaction to fail with an error message indicating the target user has services. This can be resolved by choosing a different target user or by removing the services currently configured for the target user.
Based on the setting in the reassign profile, the source user will either be left in the system (without any services) or removed from the system entirely.
Most of the services are updated to be associated to the target user and have settings updated according to the Configuration Templates (CFTs) in the reassign profiles.
There are some considerations:
Single Number Reach (SNR) - Any existing remote destinations configured for the source user are deleted. The Remote Destination Profile (RDP) is then associated to the target user and updated per the CFT in the reassign services profile.
Voicemail - the existing voicemail service for the source user is deleted to ensure a clean voicemail service. The voicemail service is then rebuilt for the target user based on the CFT in the reassign service profile. This means that any personalized settings, messages, greetings, and so on are cleared.
Shared lines - Shared lines associated to the source user will only be updated if the shared line is the source user’s primary extension.
The feature includes the optional ability to update shared line appearances of the source user’s lines on other users’ phones to reflect the destination user’s details. For example:
Bob.Smith has a phone with the following:
Line1: 55210 - Label: Bob Smith 55210
Mary Smith has a phone with the following:
Line 1: 55220 - Label: Mary Smith 55220
Line 2: 55210 (shared line appear of Bob) - Label: Bob Smith 55210
In this case, when Bob’s service is reassigned to a new user, Mary’s Line 2 appearance will need to be updated to reflect the new user (e.g display name, label, etc.). This is supported for line appearances on Phones, Device Profiles, and Remote Destination Profiles. See the reassign services profiles section for more details on the controls.