Model: device/webex/User

1. Initial setup

Step 1 involves the initial setup and configuration on VOSS Automate; the provisioning of the business hierarchy.

Identify the business information of the existing, deployed system, and add these details to VOSS Automate. This can be done manually, or via bulk load.

• Create the hierarchy, with customers, sites, and site codes to generate the initial configuration data, such as site dial plan (Provider deployment only), and site defaults data.

• Modify the data, if required, according to CUCM data, so that overbuild processing can move the data to required sites.

  For example, the default, generated VOSS Automate Site Defaults for a site have the site name as the device pool name. Since the Site Defaults are used in the overbuild, this name should be modified to match the device pool name on the imported phones before the overbuild is run.

  VOSS Automate allows Provider and Reseller Administrators to modify Site Defaults update the configuration of an overbuild.

  While customers and sites have access to the Site Defaults under the Site Management menu, the Overbuild Defaults tab in Site Defaults is only visible to Provider and Reseller Administrators.

2. Create shell dial plan schema

Provider deployment only.

Associate a shell schema group with the customer, then add a custom dial plan under Advanced Configuration (Optional at the site hierarchy).

In this step, you will need to create a shell dial plan schema group at the Customer hierarchy. The shell schema group enables Partners, Resellers, and Provider Administrators to access customers that have existing or deployed dial plans without having to use the pre-packaged type 1-4 dial plans.

The shell schema groups only contain two default values:

• Device Pool
• CUCM Group

The rest of the fields are blank for customization. This enables administrators to "over-build" VOSS Automate operations on top of customers' existing dial plans. See "Provider HCS Dial Plan Management Support Guide".

3. Configure network device connections

Identify and create network device connections, associate these with a Network Device List (NDL) and import. This includes CUCM and CUCX clusters.

This step involves provisioning Cisco UC applications, NDLs, and NDL references. Once the UC applications are configured, the sync from CUCM is scheduled and executed.

Caution: Whenever this data is synced in, it becomes managed by VOSS Automate and, as a result, would be deleted by any hierarchy delete.

One CUCM typically belongs to a customer and resides in a cluster, so this device import takes place at the created customer hierarchy. The device can also be associated with a NDL on VOSS Automate that is mapped to a created hierarchy.

4. Choose device pools and devices

5. Run overbuild

Run the overbuild to move the imported UC applications data into the site hierarchy that corresponds with the existing deployed site.

• Select User on Run Overbuild to move users exposed in User Management to the site of their associated phones (as specified in the Site Defaults Doc Device Pools). Users without phones are not moved and can be moved separately. Note that the user's role is not changed when moving to the site.

  The following model instances are moved from customer level to the site level:

  • data/User
  • device/cucm/User

• If the Lines checkbox is selected on Run Overbuild, lines are moved to the relevant site, and marked as in use in the Directory Number (DN) inventory. If a matching DN inventory entry does not exist then one is created. DN entries are created at site by default unless the Create Internal Number Inventory at Customer option is selected (in Site Defaults > Overbuild Defaults tab).

  Note: Adding Directory Number inventory at Customer level is only possible if the dial plan is non-SLC, if no dial plan is in use.

The Run Overbuild tool selects which data to move based on device pool configurations. You can run the tool for all sites, or a particular site.

The existing system's provisioned phones that have been imported should have their device pools matched with Site Default data values on each specific site.

Imported elements are moved according to overbuild Move workflows, which are triggered by the Run Overbuild tool. These workflows identify imported network device data and move it to the site hierarchy that corresponds to the existing deployed site.

6. Verify data

Use Overbuild > Overview Tool to verify the number of UC elements at the selected hierarchy and below.

You can manually validate and modify the overbuild run by reviewing the moved items, using the Overview Tool. Use Device Models and/or Relations to move, update, delete, and in a few limited cases, add instances of device types for the selected hierarchy.

Optionally, review the device model types listed with hierarchy in the Device Models or Subscriber Management menu.

7. Post-move

• Move any users who were not moved during the overbuild
• Add your E.164 inventory (optional). See Add an Inventory of E164 Numbers in the Core Feature Guide.
• Filter calling search spaces and assign a class of service (optional). See Filter Calling Search Spaces and Assign a Class of Service in the Core Feature Guide.
• Perform Self-service authentication provisioning steps for non-LDAP, LDAP, and SSO-enabled scenarios. See User Authentication in the Core Feature Guide.
• Add additional internal number inventory for future lines. See Number Management.