[Index]

Model: view/UserPhoneMoveUsers_VIEW

Move Subscriber

This feature provides a customer administrator (or higher) with the ability to move a subscriber from customer level to a site, as well as from one site to a different site under the same customer. Moving the subscriber from one site to another site on a different Unified CM cluster and CUCxn cluster is also supported.

This is done using the Move Subscriber form.

Subscriber Data

When moving a subscriber, the subscriber, phones, device profiles, SNR, voicemail and VOSS-4-UC data are processed. The subscriber will be updated with a new primary extension where appropriate.

The subscriber role at the destination hierarchy is selectable and an optional configuration template MoveUpdateUserCustom_CFT is available to make custom subscriber updates.

A device pool at the destination hierarchy is mandatory. You can select either the default device pool at the destination hierarchy or choose a different device pool from a drop-down list.

Phone Data

Desk phones can either remain at the old site or move with the subscriber. Other softphone devices, e.g. Jabber devices are always moved.

The default operation is to move all phones to the destination hierarchy, i.e. Move Desk Phones to Destination Hierarchy check box = Selected.

If the desk phones are not moved, i.e. check box = Cleared, desk phones remain at the original site and are disassociated from the subscriber.

An option is provided to create a new desk phone at the destination hierarchy. An existing phone is used as a template, and the model and phone button template can be selected from drop-down lists. An optional configuration template MoveUpdatePhoneCustom_CFT for the new phone can be chosen to make custom device settings available.

Line Data

Lines can be moved to the destination hierarchy if the move is on the same cluster. To enable moving of lines to the destination hierarchy, the UserMove_AllowLineMove_MCR macro must be cloned to the applicable hierarchy level and the value set to {{ fn.true }}.

Note that moving lines may not be supported by the customer dial plan; SLC based dial plans (types 1, 2 and 3) do not support moving of lines between sites. Make sure that the customer dial plan supports moving of lines between sites before attempting to move the line.

When moving to another Unified CM cluster, new lines must be defined. The CSS's for the new lines can be defined and a configuration template MoveUpdateLineCustom_CFT is available to make custom line updates.

Note that a check is performed to ensure that the first line across devices is common. This first line is used for SNR and voicemail. If the move is determined to be 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 data 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-4-UC subscriber is purged. The user is removed from the device/cucm/User model of the source Unified CM in VOSS-4-UC. 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.

Existing Services

Existing services associated to the subscriber such as phones and lines, device profiles, single number reach and Voicemail, which will be moved with the subscriber, are displayed on this tab.

Caveats

• Lines cannot be moved during cross cluster subscriber move, only within a Cisco Unified CM cluster.
• 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 customised 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.

Model Details