Moving Users from Site to Site (provider deployment)¶
As an administrator, you can move users from one site to another with their assigned devices and services intact. Certain conditions must be met for a site-to-site move to succeed. These conditions differ slightly for users in non-SLC dial plans and users in SLC plans.
Non-SLC Dial Plans
When moving a user with their devices and services between sites with a non-SLC dial plan configured, VOSS Automate checks the following conditions:
The sites are not configured with an SLC dial plan.
Both sites use the same NDL.
Both sites are in the same country.
The SyncTo hierarchy is a parent of both sites.
The target site data/SiteDefaultsDoc contains the needed default settings (that is, they are not empty nor null).
The role is valid at the move-to site.
Models and Relations Moved
When a user is moved from one site to another, the following models and relations move with them:
relation/Userrelation/Voicemailrelation/Subscriberrelation/SparkUserrelation/LineRelationrelation/HcsCucmCcTagRELdata/InternalNumberInventory
Fields Updated by Destination Site’s Defaults
Various fields from the destination site’s defaults update the models that are moved, such as (but not limited to):
Voicemail Pilot Numbers
Unified CM Device Pool
Unified CM Location
Unified CM Region, and others
For the device/cucm/Line model, these fields are updated:
Calling Search Space Name
Route Partition Name
Share Line Appearance Css Name
Within relation/Subscriber, three models are updated:
Device Profile
Remote Destination Profile
Phones
Each of these models contains a Lines field, which in turn can contain individual lines. In a site-to-site move, the E164 Mask and Route Partition Name fields are updated for each line contained in these models.
In addition, the move updates some fields within these individual models:
Remote Destination Profile
Device Pool Name
Route Partition Name within the Line Associations
Phones
Device Pool Name
Location Name
Updating these values is also necessary if you want to use the Overbuild feature with your existing Unified CM data in the future.
The following models trigger a warning message when you attempt to move them from one site to another. While VOSS Automate does not prevent you from moving these models, it displays a message to notify you of the possible implications of moving them:
E.164 associations
Call pickup groups
Hunt lists
Note
If you use an API for a version prior to VOSS Automate 11.5.1, the Move Users function has the previous behavior. Devices and services do not move with a user.
For the procedure to move users between sites, see Move Users (provider deployment).
Moving Users Between Non-SLC Sites with a DNR Configured
For moves between non-SLC sites with directory number routing (DNR) configured at either site, a warning appears stating that any lines associated to the user being moved may not work correctly unless you take one of the recommended actions provided. See the Advanced Configuration Guide to perform the first recommended action.
SLC Dial Plans
When you move a user between sites with an SLC dial plan configured, the required conditions are the same as with non-SLC plans. The only difference is that no error is triggered when the system check detects an SLC dial plan configuration for the customer.
Note
When user are moved from a dial plan site to a non-dial plan site the users are set to a default CSS.
Models and Relations Moved
When you move a user from one SLC site to another, the models and relations moved are the same as with non-SLC dial plans, with these exceptions:
When moving relation/Subscriber -> Lines:
Lines are disassociated from all phones and the relation.
Removing the line from Subscriber Management > Phones should remove the primary line from the relation.
These models are not handled when moving SLC dial plans, because the line does not move:
Internal Number Inventory (INI)
E.164 Association
E164 Inventory
Call Pickup Group
Hunt List
The following models trigger a warning message when you attempt to move them from one site to another. While VOSS Automate does not prevent you from moving these models, it displays a message to notify you of the possible implications of moving them:
Agent line associations
Lines associated to a subscriber’s phones, device profile, or RDP
Voicemail