Move Subscriber¶
A customer administrator (or higher) can move a subscriber:
from provider level to a site (must be logged in as provider administrator)
from customer level to a site
from one site to a different site under the same customer
from one site to another site, for example, on a different Unified CM cluster and CUCxn cluster.
This is done using (default menus Subscriber Management > Move Subscriber).
Subscriber Configuration¶
When moving a subscriber, the subscriber, phones, device profiles, SNR, voicemail, and VOSS Automate data are processed in the move.
When moving a subscriber to a different Unified CM cluster, you need to select a New CUC User Template.
The subscriber will be updated with a new primary extension where appropriate. The services associated to the selected subscriber that will be moved with the subscriber are shown on the Existing Services card (see below).
The subscriber role at the ‘move to’ hierarchy is selectable via a drop-down.
A device pool at the hierarchy is mandatory. You can select either the default device pool at the ‘move to’ hierarchy or choose a different device pool from a drop-down list.
An optional user template
MoveUpdateUserCustom_CFTcan be selected to make custom subscriber updates. You can clone and customize this template if required. The available user templates are listed on the Configuration Templates form (default menu Customizations > Configuration Templates).
Desk Phone Configuration¶
Desk phones can either remain at the old site or move with the subscriber. Existing softphone devices, such as Jabber or Dual Mode devices will always be moved, but can be configured by the Jabber/Dual Mode configuration templates (see Jabber/Dual-Mode Device Configuration).
The default operation is to move all phones, i.e. Move Desk Phones check box = Selected. If the desk phones are not moved, they remain at the original site and are disassociated from the subscriber.
A new phone can be created at the ‘move to’ hierarchy by selecting the Create New Phone check box.
When also selecting Use Existing Phone Configuration, the existing phone configuration can be used as a template, and the Phone Configuration Source, Desk Phone Profile and Phone Name can be selected from drop-down lists.
The Phone Configuration Source drop-down displays a list of the subscriber’s existing phones. If an existing phone is selected, the new phone will be created using the configuration of the existing phone.
The Desk Phone Profile, which defines the phone type (and associated configurations), and the Phone Name available in the drop-downs are those displayed on the Phone Configuration Mapping form (default menu Customizations > Phone Configuration Mapping).
Default phone configuration mappings are available per hierarchy and are used at the selected hierarchy and below.
See “Configuration Mapping Files” in the Core Feature Guide for more details.
For new phones, when not selecting Use Existing Phone Configuration, the user should choose:
The Desk Phone Profile, which defines the phone type (and associated configurations),and the Phone Name available in the drop-downs are those displayed on the Phone Configuration Mapping form (default menu Customizations > Phone Configuration Mapping).
The Desk Phone Feature Template is available for the selection of a template from the first Phone Mapping Configuration found up the hierarchy tree.
The Move Subscriber process applies the newly created phone with the desk phone profile and then on top of it the details from the chosen Feature Template.
Jabber/Dual-Mode Device Configuration¶
Jabber and Dual Mode devices are automatically moved with the Subscriber.
The device configuration is derived from the device profile selected in the associated Profile drop-down, i.e. Android, CSF, Tablet, iPhone, Carrier Integrated Mobile and CTI Remote Device. The default device profiles are found on the Phone Mapping [Default] form (default menu Customizations > Phone Configuration Mapping).
You can clone and save a profile if required, and customize the relevant settings, e.g. Basic Phone CFT in order to apply different settings to the device.
See “Configuration Mapping Files” in the Core Feature Guide for more details.
Line Configuration¶
Creating Lines¶
When moving to another Unified CM cluster, new lines must be defined.
When a new line is defined, a Line Template can be selected for the new line. One line template may apply to all lines.
The CSS’s for the new lines can be defined, and a configuration template MoveUpdateLineCustom_CFT
is available to make custom line updates.
The system performs a check to ensure that the first line across devices is common. All new lines created (or existing lines moved) in the move, will be assigned to SNR. For example, if a Subscriber with 3 lines and a Phone, SoftPhone, DeviceProfile, SNR is moved, all these services will be associated with the 3 lines. The only exception to this is for Voicemail, where the first line is always selected as the Voicemail line.
Moving Lines¶
Important
Moving of lines functionality is neither exposed nor supported by VOSS Automate. If you want to assume the risk of moving lines, contact VOSS support to expose the move line functionality.
Lines can only be moved if your system is using a type 4 dial plan, and only if the move is on the same cluster. Make sure that the customer dial plan supports moving of lines between sites before attempting to move the line.
SLC based dial plans (types 1, 2 and 3) do not support moving of lines between sites.
If the move is between sites hosted on the same Unified CM cluster, the subscriber data is moved to the new hierarchy and updated as above. It is assumed that the CUCxn (if used) will remain.
If the move is between different Unified CM clusters, the specific move data as defined above is re-provisioned on the new cluster and deleted on the original cluster, except for the Unified CM subscriber. When the Unified CM subscriber is local, the old subscriber is removed.
In the case of an LDAP user, the VOSS Automate subscriber is purged.
The user is removed from the device/cucm/User model of the source Unified CM
in VOSS Automate. The home cluster flag is maintained such that it is only set to
true on the Unified CM cluster hosting the subscriber, even if the subscriber
exists on other Unified CM clusters.
When moving between clusters, the CUCxn server can be retained. In this case, the model instances are moved. In the case that the CUCxn server changes, a new CUCxn subscriber is created against a chosen subscriber template. This will not copy custom settings for the CUCxn subscriber or any recorded prompts and messages.
Caveats¶
The first line on all devices must be common prior to the move. Replacing lines creates the same line layout on all devices.
When moving cross cluster, the Unified CM cluster is changed. The CUCxn cluster may be retained or changed, based on the new site NDL. If the CUCxn cluster is changed, only basic voicemail is created - user customized configuration, as well as prompts and messages are not moved to the new CUCxn cluster.
CUCxn cluster moves are only supported where the Unified CM cluster changes.
Existing Services¶
The following existing services associated to a subscriber will also be moved:
phones (and associated lines)
devices
device profiles
single number reach
voicemail
webex
webex teams
contact center