Reassign Services Profile

The Reassign Services Profile input form allows for a set of configuration settings and additional settings to apply when the Reassign Services functionality is used. The configuration templates (CFTs) that are selected in the profile determine how many of the detailed settings of the various services are updated as part of the reassign. This is essentially to allow you to re-align settings to your baseline service deployment logic and update any settings that incorporate the user’s name - for example descriptions, alerting/display names, labels, and so on.

If no CFT is defined for a service, it is still moved to the new user. However, existing settings will be left in place. There are a few cases where the feature will make updates to specific service settings regardless of the CFT (i.e. when these settings are required to associate the user and service - owner of a phone, associated devices on the UCM user, etc). If the source user does not have a given service (e.g voicemail) then any CFT in the profile is ignored as the feature does not add new services that did not exist on the source user.

There is a set of example CFTs in the system by default - prefixed RS - that provides some examples of common settings and logic that might be used.

This profile and templates for configuration settings can be maintained per hierarchy as needed. The context for the reassign services feature is fairly similar to Quick Add Subscriber and this is to allow the reuse of macros/logic from your quick add group CFTs in the reassign services profiles. In many cases you could even use the same CFT to ease maintaining multiple sets of CFTs that define the baseline user and service configuration.

Note

At least one Reassign Services Profile must be created in order to use the feature.

Field	Description
Profile Name	Name for the Profile - recommended to make it meaningful to the user’s that will be using the feature if you need more than one profile.
Profile Description	Description for the profile
Remove Source User	If selected the feature will fully remove the source user after moving all the services. If not selected then the base user and subscriber will be left when the feature completes however no services will be enabled.
User CFT	This CFT defines VOSS User settings to apply to the target user - e.g. role
CUCM User CFT	This CFT defines the UCM User settings to apply for the target user - e.g Department, Service Profile, etc.
Line CFT	This CFT defines the UCM Line settings to apply for the target user - e.g. Description, Alerting Name, Pickup Group, Call Forwarding, etc
Phone CFT	This CFT defines the Phone settings to apply to the devices being moved - e.g. Line Label, display name, device pool, CSS, etc. This same CFT applies to all phones (hardphones, soft-clients, etc) so typically relate to line appearance settings or other non-phone type specific settings. ownerID, mobility user (for soft clients) as set via the workflow irrespective of the CFT.
Device Profile CFT	This CFT defines the Device Profile (extension mobility) service for the user - e.g Line label, display name, etc. As with the Phone this is typically for line appearance settings on the device profile.
Remote Destination Profile CFT	This CFT defines the Remote Destination Profile (Single Number Reach - SNR) settings to apply to the service being moved - e.g line label, display name, CSSs, etc. Again typically for updating line appearance settings but can also edit other base RDP settings.
CUC User CFT	This CFT defines the CUC User (Voicemail) settings to apply when setting up voicemail for the user.
Add CUC User Alternate Extension	This setting determines if the feature will add a voicemail alternate extension for the user if voicemail exists on the source user. This can be used to add a standard alternate extension (e.g short extension version of the user’s number) if needed as part of your standard deployment.

Field	Description
CUC Alternate Extension CFT	This setting is visible if the add alternate extension setting above is true. This CFT determines the settings for the alternate extension that will be added. This is where you would define the alternate extension to be added as standard.
Update CUC User Message Handler (Action)	This setting determines if the feature will configure the message handler settings for voicemail (form of single inbox).
CUC Message Handler (Action) CFT	This setting is visible if the message handler setting above is true. This CFT determines the settings that will be configured for the message handler. So this will need to include the email address for example of the user as well as the message actions.
Update shared lines (for unassociated Phones, Device profiles, RDP)	This setting determines if the feature will update line appearances of the source user’s lines on other user’s devices. This can be used to update the display names or labels for instance on those remote devices to reflect the new user’s details. These CFTs only apply to line appearance settings on those devices (not general phone settings) and only for the line appearances that are shared with the source user. Other line appearances on the devices will not be updated. For example, the other user’s phone had 3 lines, only 1 of which was shared with the source user. Only that 1 line appearance will be updated and the other 2 will be left untouched.
Shared Line (unassociated Phone) CFT	This setting is visible if the Update Shared Line setting is true. This CFT determines the settings on the other users’ Phones that have the line appearance.
Shared Line (unassociated Profile) CFT	This setting is visible if the Update Shared Line setting is true. This CFT determines the settings on the other users’ Device Profiles that have the line appearance.
Shared Line (unassociated RDP) CFT	This setting is visible if the Update Shared Line setting is true. This CFT determines the settings on the other users’ RDP that have the line appearance.

Typically, Configuration Templates similar to your current Quick Add Subscriber templates can be used. Example Configuration Templates are also available for each drop-down, with naming convention RS Example <service> CFT. The templates shown on the Configuration Templates menu can be cloned, renamed and modified per hierarchy as required.

Configuration examples:

• Template Name: RS Example CUCMPhone CFT

  Field: Line > Display Ascii

  Value:

  ((input.firstName == fn.null ))
  <{{input.lastName}}>
  <{{input.firstName}} {{input.lastName}}>
  

• Template Name: RS Example CUCMLine CFT

  Field: ASCII Alerting Name

  Value:

  {{fn.sub_string input.lastName, 0, 30}}
  

Additional optional settings available:

• Add CUC User Alternate Extension:

  If checked, a drop-down is enabled to select a template that updates the alternate extension.

  Example template: RS Example CUCAlternateExtension CFT

  Field: DisplayName

  Value:

  {{ input.firstName }} {{ input.lastName }} Alt
  

• Update CUC User Message Handler (Action):

  If checked, a drop-down is enabled to select a template that updates the email address for single inbox.

  Example template: RS Example CUCMessageHandler CFT

  Field: RelayAddres

  Value: if no input email address is available, a dummy address is added

• Update shared lines (for unassociated Phones, Device profiles, RDP):

  If checked, a drop-down is enabled to select a template so that for any shared line instances from the source user, line label details can optionally be updated with those of the target user. The Line CFT template updates do not apply to shared lines.