[Index]

Model: data/ReassignServicesProfile

Reassign User Services

Reassign Services simplifies and automates the transfer of existing Subscriber services from a Source User to a Target User.

This utility is for example useful when an employee left the company and a new employee now starts the same role. Therefore, instead removing the old subscriber and configuring a new subscriber with the same settings and standards, the services and settings can be moved from the old subscriber to the new subscriber.

These services can include:

• Phone(s), which can be dual-mode with associated Remote Destination and/or Mobile Identity
• Device Profile(s)
• Remote Destination Profile(s) with associated Remote Destinations
• Voicemail User with related services including Alternate Extension and Message Handler (Action).

Custom settings can be applied to these services during the reassignment. A Reassign Services Profile setting is available to choose the configuration templates that will be used to update services during reassignment. These allow you to customize most settings on any of the above devices, including Line Alerting Name, Line Label, DisplayASCII values, and so on.

Example templates are provided that contain macro variables for fields that are likely to differ between subscribers. The field values then resolve with input from existing target user details. In this way the templates are not limited by for example a Site and Phone Model.

When reassigning services from existing source users to existing target users, the latter are moved to the same site as the source user, if these differ.

An option is also available to create a new target user as part of the Reassign Services process, instead of selecting an existing user without services. This user will be created at the same site as the source user.

Other features included are:

• Change User Details (modified Reassign Services) that updates the services of an existing subscriber using custom templates referenced in a Reassign Services Profile.

Topics:

• Reassign Services
• Reassign Services Update
• Reassign Services Profile

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.

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.

doc

Model Details