CUCDM

10.6.3OverBuild: Day
2 User/Subscriber
Management TOI
Mohammad Al-taraireh

Over Build (OverBuild)

OverBuild
198.18.133.251
198.18.133.254
198.18.133.13

98.18.133.250
198.18.133.15

198.18.133.252

198.18.133.14
198.18.133.253

Durable Energy

Liquid Financial

Over Build (OverBuild)

OverBuild Overview
OverBuild Deployment Steps
Shell Schema Group
HCS Overbuild
Run Overbuild
Overview Tool
Relation Move Operation
Directory Number Inventory Audit Tool
Device Model Menu
Day 2 Post Overbuild
Self care post overbuild procedures
New Sites Procedure
Class of Service Tagging
Purging of Customer Data
MISC Caveats & Notes

What is Over Build ?

A feature in CUCDM that allows the HCS partners leverage the CUCM
existing configuration, and all CUCM customer provisioning, including
the CUCM configured dial plan and use that data on CUCDM to allow
Day 2 operations from CUCDM.

What is Over Build ?

CUCDM

Provider/
cache

CustomerA/
CUCM
cache

CustomerB/

CUCM

CUCM
cache
cache

CustomerB

CustomerA

AXL

DevicePool = Site1/location/dialplan/
DevicePool = Site2/location/dialplan/
DevicePool = Site3/location/dialplan/

CustomerC/

AXL

AXL

CustomerC

DevicePool = Site1/location/dialplan/

DevicePool = Site1/location/dialplan/

DevicePool = Site2/location/dialplan/

DevicePool = Site2/location/dialplan/

What is Over Build ?

CUCDM

Provider/

cache

CustomerA/

CustomerC/

CustomerB/

CUCM

CUCM

CUCM

cache
cache

cache

Site1

Site1
cache

cache

Site1

cache
Site2

cache

Site2
cache

Site2
cache

Site3
cache

CustomerB

CustomerA

AXL

DevicePool = Site1/location/dialplan/
DevicePool = Site2/location/dialplan/
DevicePool = Site3/location/dialplan/

AXL

AXL

CustomerC

DevicePool = Site1/location/dialplan/

DevicePool = Site1/location/dialplan/

DevicePool = Site2/location/dialplan/

DevicePool = Site2/location/dialplan/

OverBuild Introduction
Manage Customers Existing Data with CUCDM
Previously, this concept was referred to as : brownfield, migration, overbuild and bring your
own dial plan (BYODP)

OverBuild has been divided into 3 categories:

OverBuild: Day 2 Subscriber Management -CUCDM management of MACD for subscribers
and subscriber features for existing customer configurations. All day 0 and day 1 configuration is still done on
CUCM/CUC directly or using existing tools. 10.6(2)

OverBuild: Day 1 Voice Mail - CUCDM management of existing customer day 1 voice mail
configuration. Day 1 voice mail includes routing and dial plan configuration between CUCM and CUC to
enable voice mail.

OverBuild: Day 1 Dial Plan - CUCDM management of the customers dial plan from CUCDM. This
includes the ability to create a dial plan template in CUCDM that matches the customers existing dial plan,
and use this template to deploy new dial plan elements (e.g. for new sites).

OverBuild Deployment Steps

1)
2)
3)
4)
5)
6)

Understand the UC existing implementation and dial plan

Create Business Customer/NDL/Site Hierarchy in CUCDM
Associate Shell Schema Group and Add a Custom Dial Plan
Provision UC Applications and Sync Data
Move HCS Users / Devices/ .. to the correct site based on filters.
Manage Number Inventory: Both DN inventory and E164 Inventory may
need to be Manageable.
7) Post Move Operations & validation.
8) Manage Class of Service: Tagging Calling Search Spaces as Class of Service.
9) Cutover to CUCDM 10.x: Start using Day 2 Configuration from the Admin
and Self-Service Interfaces. *Self-service can be used as soon as data is
synced to Customer HN. The Admin Interface can be used for Subscriber
updates/deletes while Data is at the Customer HN. Subscriber Adds must
be at the Site HN.

Step 1:Understand the UC existing

implementation and CUCM dial plan
The Over Build does not do data TRANSFORMATION. The same data and configuration
that is on CUCM will Be synced to the hierarchy Node on CUCDM (the Hierarchy Node is
where the CUCM is configured)
Provider/

CustomerA
cache

CustomerA/
CUCM

device/cucm
DevicePools
DevicePools
Users
Users
Users

Locations
Locations
Lines
Lines

Translations
Translations

Phones
Phones

Partitions

Phones

Partitions
Partitions

CSS
CSS

CUCM Data SYNC (AXL)

DevicePools

Translations

Phones

DevicePools

Translations

Phones

Users
Users
Users

Locations
Locations
Lines
Lines

Partitions

Phones

Partitions

CSS
CSS

Partitions

Unified API Gateway Simplified Northbound

Integration
SOAP/axl

axl

CUCM APIs

Auto Generated
Device Models

REST/JSON
CUC APIs

LDAP APIs

REST/JSON
WebEXAPI
s

Device
Model
Generator

CUCDM Core

CUC Device Models

Work Flows

LDAP Device Models

Templates

CC-API

.....

device/type/model

CTX/TMS Device
Models

device/cucm/model
device/cuc/model
device/hcmf/model
device/ldap/model

REST/JS
ON

RBAC

CUCM Device Models

WebEx Device
Models

HCM-F

JSON

Bulk Load
capabilities

Display
Policies
Generic
Script
interface

End to End code generation for

Device Drivers, an API, GUI
screens, and Bulk Loaders

CUCDM APIs

LDAP

Consume API
definitions and
generates Device
Models

JSON

CUCDM
GUI

Steps 2-4: Create CUCDM Customer/Site

Hierarchy, Associate Shell Group and Sync
Data
To sync the Customers existing data to CUCDM 10.x, the following
provisioning is required:
1.

Create The required CUCDM Hierarchy: manually provision the customer/site CUCDM

2.

Associate Shell Schema Group : associate a Shell Schema Group with the Overbuild

3.

Add a Custom Dial Plan: add a Custom Dial Plan to the Overbuild Customer. *Refer to the

4.

Create UC App Devices, NDLs and NDLRs: provision the UC Application Devices and

5.

Sync Data: after the UC Application Devices (CUCM,CUC, etc.) are provisioned, a sync is scheduled

business .*Refer to the HCS Customer On Boarding Guide

Customer. *Refer to the Shell Schema Group topic
Shell Schema Group topic

Network Device Lists at the Customer Hierarchy Node. Configure Network Device List References
during Site Hierarchy Node(s) creation. *Refer to the HCS Customer On Boarding Guide
and executed. *Refer to the HCS Customer On Boarding Guide

Step 2- 4 Create Business Hierarchies/Sync

Provider/
cache

CustomerA

Cisco Shell
dial plan

CustomerA/

CUCM
Site1

DevicePools
DevicePools
Users
Users
Users

Locations
Locations
Lines
Lines

Translations
Translations

Phones
Phones

Partitions

Phones

Partitions
Partitions

CSS
CSS

CUCM
Data SYNC
(AXL)

device/cucm
DevicePools Translations
Translations
DevicePools
Locations
Partitions
Users
Users Locations Partitions
Partitions
Users
Lines
Lines

cache
Phones
Phones
Phones
Site2

CSS
CSS
cache

Site3

cache

Step 5: Move Data

After the sync of the Customers Data to a CUCDM 10.x
From CUCM at the Customer Hierarchy Node (HN), the Day
2 data will need to be moved to a Site.
1.

Overbuild (OBT )Tool : moves day 2 device models based on device pools. *Refer to
the Run Overbuild Topic

2.

Subscriber Management Model Moves: Admin have the option of manually

3.

Overbuild->Device Models Menu : Admins have the option of manually moving

4.

Device Models Moved by OBT: . *See the Models Moved by OBT Slide

5.

Device Models Not Moved by OBT: . *See the Models Not Moved by OBT

6.

Overview Tool: provides a list of device model counts at the current hierarchy and

moving: Lines, Phones, Subscribers, Voicemail, Hunt Groups and Call Pickup Groups.
*Refer to the Relation Move Operation topic
device models from the Overbuild Device Model Menu .

below . *Refer to the Overview Tool Topic

Slide

Step 5: Move Data

Provider/

NO TRANSFORMATION
Just moving data under the right
CUCDM hierarchy

cache

CustomerA/
Cisco Shell dial plan

Move Filter site1

Move Filter Site2
CUCM

Move Filter Site3

Site1

DevicePool=site1
DP for site1

device/cucm

Local CUCM cache

DevicePools
DevicePools
Users
Users
Users

Translations
Translations

Locations loooooo
Partitions
Locations
Lines
Lines

cache

Users/phones/lines
for site1

Phones
Phones

Partitions

CSS

Partitions

CSS

Move Data Based

On Device Pool

DevicePool=site2

Site2

DP for site2
Users/phones/lines
for site2

cache

DevicePool=site3
Site3

DP for site3
Users/phones/lines
for site3

cache

Models Moved By the Overbuild Tool

device/cucm/Phone

device/cuc/SmsDevice

device/cucm/RemoteDestinationProfile

device/cuc/SmtpDevice

device/cucm/RemoteDestination

device/cuc/PhoneDevice

device/cucm/User

device/cuc/PagerDevice

device/cucm/DeviceProfile

device/cuc/HtmlDevice

device/cucm/Line

device/cuc/User

device/cuc/Callhandler

device/cuc/UserPassword

device/cuc/AlternateExtension

device/cuc/UserPin

device/cuc/CallhandlerTransferOption

device/cuc/CallhandlerMenuEntry

device/cuc/Greeting

Step 5: Move Data

NO TRANSFORMATION
Just moving data under the right
CUCDM hierarchy

Provider/
cache

CustomerA/
Cisco Shell dial plan

CUCM

device/cucm

Local CUCM cache

DevicePools
DevicePools
Users
Users
Users

Translations
Translations

Locations loooooo
Partitions
Locations
Lines

Phones
Phones

device/cucm/DevicePool
device/cucm/Region
device/cucm/Location
device/cucm/VoiceMailPilot
device/cucm/VoiceMailProfile
device/cucm/Css
device/cucm/RoutePartition
device/cucm/HuntList
device/cucm/HuntPilot
device/cucm/LineGroup
device/cucm/CallPickupGroup
device/cucm/DirectedCallPark
device/cucm/CallPark
device/cucm/CtiRoutePoint

Site1

device/cucm/Phone
device/cucm/RemoteDestinationProfile
device/cucm/RemoteDestination
device/cucm/User
device/cucm/DeviceProfile
device/cucm/Line

cache

Site2

device/cucm/Phone
device/cucm/RemoteDestinationProfile
device/cucm/RemoteDestination
device/cucm/User
device/cucm/DeviceProfile
device/cucm/Line

cache

Partitions

CSS

Partitions

CSS

Lines
Site3
cache

device/cucm/Phone
device/cucm/RemoteDestinationProfile
device/cucm/RemoteDestination
device/cucm/User
device/cucm/DeviceProfile
device/cucm/Line

Day 2 Models Not Moved By the Overbuild

Tool (stay at the customer level)

device/cucm/DevicePool

device/cucm/HuntList

device/cucm/Region

device/cucm/HuntPilot

device/cucm/Location

device/cucm/LineGroup

device/cucm/VoiceMailPilot

device/cucm/CallPickupGroup

device/cucm/VoiceMailProfile

device/cucm/DirectedCallPark

device/cucm/Css

device/cucm/CallPark

device/cucm/RoutePartition

device/cucm/CtiRoutePoint

Shell Schema Group

Mohammad Al-taraireh

HCS Schema Groups

Cisco Shell Schema Group

This feature allows a partner, reseller, or provider admin to access CUCDM Day 2
Provisioning functionality for Over Build customers with existing/deployed dial
plans, without having to use any of the Cisco pre-packaged Dial Plans (Type 1-4)
The will enable over-build operations on top of the customers existing dial
plans
The Cisco Shell Schema Group is a shell or straw-man schema with only 2
site default values for Device Pool and CUCM Group. Rest of the site default
Schema Group fields are blank out-of-the box, and open to customization
By default, no Dial Plan elements will be pushed down to CUCM
Once a Cisco Shell Schema Group is associated to a Customer and they have
created a Customer Dial Plan (no Site Dial Plan is required), the following
Custom Workflows become available:

Cisco Shell Schema Group (Continued)

addDnInventory - allows customer to create DN inventory without enforcing any rules

or constraints on the DN numbers
addE164Inventory - allows customer to create E164 inventory without enforcing any
rules or constraints on the E164 number other than enforcing the country code prefix
for a given site
associateE164ToDn - allows E164 to DN number association (N to N) on Cisco Unified
Communications Domain Manager 10.6(2) without configuring anything on Cisco
Unified Communications Manager
unassociateE164ToDn - removes E164 to DN number association (N to N) from Cisco
Unified Communications Domain Manager 10.6(2) without removing anything on
Cisco Unified Communications Manager
associateE164ToSingleDn - allows E164 to DN number association (N to 1) on Cisco
Unified Communications Domain Manager 10.6(2) without configuring anything on
Cisco Unified Communications Manager
unassociateE164ToSingleDn - removes E164 to DN number association (N to 1) on
Cisco Unified Communications Domain Manager 10.6(2) without removing anything
on Cisco Unified Communications Manager

Cisco Shell Schema Group - Configuration

Log in to CUCDM As Provider Admin:

1. First create a customer, then Bread Crumb to that customer hierarchy node
2. Under Dial Plan Management -> Advance Configuration -> Associate Custom Dial Plan
Schema Group
Click on Add and select Cisco Shell Schema group for Dial Plan Schema Group.
Click on Save
3. Add a Customer Dial Plan:
Under Dial Plan Management -> Customer -> Dial Plan click Add . Youll see the
Customer ID pre-populated. You can select two additional fields
Site Location-based (SLC) based Dial Plan (typically left disabled for OverBuild
deployments)
Enable CSS Filtering Enabling this will allow CSS filtering on Day 2 Subscriber
Management operations from the GUI
Click on Save
4. Now you can manage DN and E.164 inventory under Dial Plan Management -> Number
Management

HCS Overbuild
Mohammad Al-taraireh

The Overbuild Menu

Available from Provider and Reseller Administrator Accounts Only*

Overbuild Menu Items

Move Users : Move HCS Users based on filters, usernames or a username. The Overbuild Tool does not

Site Defaults : Provisioning on the Overbuild Defaults tab determines if and how imported data is moved to a site

Run Overbuild : The Overbuild Tool which moves device model data to site hierarchies based on device
pools. *See the Run Overbuild Topic for more information.

Overview Tool: Counts of device models (organized by device model type) that exist at the current hierarchy and

Directory Number Inventory : Lists Internal Number Inventory (INI) data Models at or below the current

Directory Number Audit Tool: Create New and Update Existing INI Models at a Customer hierarchy and

Log Messages :

automatically move HCS Users. This must be done manually using move filters. *See the User Management Guide for
more information.
hierarchy when the Overbuild Tool is run.*See the Run Overbuild Topic for more information.

the hierarchy below. *See Overview Tool Topic for more information

hierarchy. Read, Delete and Move operations supported per INI instance. *See Directory Number Inventory Audit Tool
Topic for more information.
below. *See Directory Number Inventory Audit Tool Topic for more information.

Directory Number Inventory Logs: Info and Warning Messages generated from the Directory Number Audit Tool
User Management Logs: Info and Warning Messages generated from User Management Operations

Device Models: List of device models which can be manually updated, moved, deleted. *See Device Model
Menu

Runing Overbuild
Mohammad Al-taraireh

Site Defaults: Overbuild Defaults Provisioning

1. Configuration of Site Defaults is REQUIRED before executing the Run Overbuild
tool

Only Provider and Reseller Administrators have access to the Overbuild Defaults
configuration on the Site Defaults

2. Site Defaults configuration determines which models are moved to the site
where the defaults are defined

Run Overbuild uses the Device Pool configuration on the Overbuild and the General
Defaults Tabs to determine the models to move and where to move them
Additional Device Pools can be added, so that more than one Device Pool from
those of the imported phones can be moved to the same site
The names of the Additional Device Pools can be renamed to the Default Device
Pool name as entered on the General Defaults tab if the Replace with Default Device
Pool box is checked

3. Sites that have enabled the Include Site for Overbuild checkbox will be
included in the Overbuild for a particular Customer

Site Defaults: Overbuild Defaults Provisioning

Move All Devices

Site Defaults: General Defaults Provisioning

Site Defaults: Overbuild Defaults Provisioning

Replace With Default Device Pool

Site Defaults: Overbuild Device Controls

Move All Devices

All matching and related imported devices are moved to the site
Run Overbuild supported when Overbuild Action type is :
Use Site Defaults Doc Overbuild Settings

Limit Moved Devices

Select devices to move with the check boxes
Run Overbuild will move selected devices when:
Overbuild Action type is : Use Site Defaults Doc Overbuild Settings
Availability of device check boxes depends on the status of other device check
boxes
Dual-Mode Remote Destinations, Users, and Lines check boxes are only
available if the Phones box is checked
Device Profiles, Remote Destination Profiles, and CUC Users check boxes are
only available if the Users box is checked
Remote Destinations check boxes are only available if the Remote
Destination Profiles box is checked

Site Defaults: Overbuild Defaults Provisioning

Limit Moved Devices

Run Overbuild
Run Overbuild only executes at the Customer Level

The order the sites are processed can not be

guaranteed
If order matters, turn all sites off except the one you
want to move
Run Overbuild only supports a single dedicated cluster configured at the
Customer level

Multiple clusters on a single Customer is not supported

for Overbuild
Shared clusters configured above the Customer
hierarchy are not supported

Run Overbuild : Overbuild Actions Options

1. All Sites Included

Overbuild will include all Run Overbuild selected Devices

Devices selected on the Overbuild Defaults Tab with the

Limit Move Devices Option are ignored
2. Use Site Defaults Doc Overbuild Settings

Devices selected on the Overbuild Defaults Tab with the Limit Move
Devices Option are included in the Overbuild

Run Overbuild selected Devices are ignored

3. Common to both Overbuild Actions
Sites are included in the Overbuild if the site defaults Include Site for
Overbuild option is checked
Run Overbuild uses the configured Device Pools on the General Defaults
Tab and the Additional Device Pools on the Overbuild Defaults Tabs to
determine the models to move and where to move them

Run Overbuild : All Sites Included

Run Overbuild :

Use Site Defaults Doc Overbuild Setting

Run Overbuild : All Sites Included

Device Selection : Availability of device check boxes depends on the status of
other device check boxes

a. Dual-Mode Remote Destinations, Users, and Lines check

boxes are only available if the Phones box is checked

b. Device Profiles, Remote Destination Profiles, and CUC Users

check boxes are only available if the Users box is checked
c.

Remote Destinations check boxes are only available if the

Remote Destination Profiles box is checked

Run Overbuild : All Sites Included

Phone Disabled No Choices

Run Overbuild : All Sites Included

Phone Enabled Only Choices

Run Overbuild : All Sites Included

Users Enabled Choices

Run Overbuild : All Sites Included

Remote Destination Profiles Enabled Choices

Limitation and Recommendations

Limitation:
Run Overbuild Tool DOES NOT rollback data from failed move operations.

Recommendation:
Verify that Run Overbuild Transaction completed from the Administration
Tools->Transaction Menu
If there are failures, identify models that were not moved using the Overview
Tool, Overbuild->Device Model Menu and the Subscriber Management Menu.
Manually move individual device models from the Overbuild->Device Model
Menu. See the Device Models Topic
Manually move individual relation models from the Subscriber Management
Menu. See the Relation Move Operation Topic

Limitation and Recommendations: Delete / Purge of

Managed Service Data
When CUCM and CUCxn data is synced into CUCDM, CUCDM assumes
management of that data.
As a result, data will be deleted by any hierarchy delete in CUCDM.

To prevent delete failures from happening

Work with a Cisco System Integrator to update your
HcsCucmWrapperCascadeDelPWF workflow to handle dependencies in
your existing dial plan
Perform a purge operation on the device before deleting the hierarchy
Purging will delete all users, subscribers, phone, profiles, and devices
from CUCDM, while leaving them intact on the CUCM and CUCxn
devices
Purges can also be create/executed on a particular hierarchy if you only
want to purge a portion of the data

Overview Tool
Mohammad Al-taraireh

Overview Tool

Runs at Customer or Site Hierarchy Nodes Only

Overview Tool : From Customer Hierarchy

Count from Customer HN / Count below Customer

Overview Tool : From Site Hierarchy

Count from Site HN / Count below Site HN

Relation Move Operation

Mohammad Al-taraireh

Enable Move Operation for Day 2

Subscriber Management Models
Administrators now have privileges to manually move the following Subscriber
Management Menu models:

Lines - relation/LineRelation

Phones - relation/SubscriberPhone

Subscribers - relation/Subscriber
Note: HCS User Relations Must be moved independently

Voicemail - relation/Voicemail

Webex - device/webex/User

Hunt Groups - relation/HuntGroupRelation

Call Pickup Groups - relation/CallPickupGroups

Move Line Relation

Select Move to Hierarchy

Caveats and Recommendations

Caveat:
Moving Subscriber Relations does not move the HCS
User Relations (HcsUserREL).
Recommendation:
Move HCS User Relations prior to moving the
Subscriber Relation.

Directory Number Inventory

Audit Tool
Mohammad Al-taraireh

Directory Number (DN)Inventory Audit

Tool
Create New or Update Existing Internal Number Inventory instances for a selected
Customer Hierarchy

Directory Number Inventory Audit Tool Access

Provider and Reseller Administrator Account Access Only
Dial Plan Management Menu:
Dial Plan Management >> Number Management >> Directory Number
Audit Tool
Dial Plan Management >> Number Management >>Log Messages
Overbuild Menu :
Overbuild >> Directory Number Audit Tool
Overbuild >> Log Messages->Directory Number Inventory logs Action

DN Inventory Audit Tool Runs at Customer

Hierarchies Only

DN Inventory Audit Tool Creation Policy Choices for

Non-SLC based Dial Plans

DN Inventory Audit Tool Creation Policy Choices for

SLC based Dial Plans

DN Inventory Instance

DN Inventory Audit Tool - Creation Policies

Creation Policies: All Creation Policies are applied to the selected Customer Hierarchy
Customer Create

Creates DN Inventory at the Customer level

Updates all existing DN Inventory Instances
Available for non-SLC dial plans (e.g. Type 4 or 5)

Site Create

Creates DN Inventory at the first site the line is encountered if:

Line exists with a unique pattern

More than one line exists with the same pattern but different partitions
DN Inventory is created for the first line encountered with that pattern

Creates a Warning Log Message and will not create DN Inventory if:

Line exists at the customer level

Updates all existing DN Inventory Instances

Available for all types of dial plans

DN Inventory Audit Tool Smart Create Creation

Policy
A Line is Shared Across Sites if the line is referenced by one or more phones in other sites

Smart Create

Creates new DN inventory at customer level if:

Line exists at a site

Line is Shared Across Sites
The dial plan type is non-SLC (e.g. type 4 or 5)

Creates new DN Inventory at the site where the line exists if:

Line exists at a site

Line is not Shared Across Sites
Line is Shared Across Sites and the dial plan type is SLC (e.g. type 1-3)

Creates a Warning Log Message and will not create DN Inventory if:

Line exists at a Customer Level

Updates all existing DN Inventory Instances
Available for all types of dial plans

Troubleshooting
Mohammad Al-taraireh

DN Inventory Audit Tool Trouble Shooting

DN Inventory Log Messages
Info Logs

Generated when new DN Inventory Instances are

created or updated
Warning Logs

Generated when the DN Inventory Audit Tool is unable

to create DN Inventory Instances for a line
Generated when the DN Inventory Audit Tool creates
new DN Inventory Instances at the customer level and
the line exists at a site level.

DN Inventory Audit Tool Log Messages

DN Inventory Audit Tool Warning Log Message

DN Inventory Audit Tool Info Log Message

Device Models
Mohammad Al-taraireh

Overbuild Device Models Menu

Move Device CUCM Line

Move Device Model Hierarchy Choices

Move CUCM Line Up to Customer HN

Overbuild Device Models Menu List

CUC AlternateExtension : device/cuc/AlternateExtension

CUCM DeviceProfile : device/cucm/DeviceProfile

CUC Callhandler : device/cuc/Callhandler

CUCM DirectedCallPark : device/cucm/DirectedCallPark

CUC CallhandlerMenuEntry : device/cuc/CallhandlerMenuEntry

CUCM HuntList : device/cucm/HuntList

CUC HtmlDevice : device/cuc/HtmlDevice

CUCM HuntPilot : device/cucm/HuntPilot

CUC PagerDevice : device/cuc/PagerDevice

CUCM Line : device/cucm/Line

CUC PhoneDevice : device/cuc/PhoneDevice

CUCM LineGroup : device/cucm/LineGroup

CUC SmsDevice : device/cuc/SmsDevice

CUCM Location : device/cucm/Location

CUC SmtpDevice : device/cuc/SmtpDevice

CUCM Phone : device/cucm/Phone

CUC User : device/cuc/User

CUCM Region : device/cucm/Region

CUC UserPassword : device/cuc/UserPassword

CUCM RemoteDestination : device/cucm/RemoteDestination

CUC UserPin : device/cuc/UserPin

CUCM RemoteDestinationProfile :
device/cucm/RemoteDestinationProfile

CUCM CallPark : device/cucm/CallPark

CUCM RoutePartition : device/cucm/RoutePartition

CUCM CallPickupGroup : device/cucm/CallPickupGroup

CUCM Users : device/cucm/User

CUCM VoiceMailPilot : device/cucm/VoiceMailPilot

CUCM VoiceMailProfile : device/cucm/VoiceMailProfile

Webex User : device/webex/User

CUCM Css : device/cucm/Css

CUCM CtiRoutePoint : device/cucm/CtiRoutePoint

CUCM DevicePool : device/cucm/DevicePool

Day 2 Post Overbuild

Mohammad Al-taraireh

Self Care Use Case 1:

Brown Field Customer not LDAP Integrated

CUCDM does not get password information from CUCM.

Self care users cannot login unless their passwords are reset
Need to perform initial password reset of all users after brownfield import of
users from CUCM

Provider can use a bulk loader sheet for this operation.

Steps:
In Subscriber Management menu - > Subscribers select all users displayed(maximum possible is 200)
Action -> Export select Excel(formatted)
Open the Excel sheet, and populate modify in Action column, userid:<userid> in Search Field
column, and default password in Password column , save the bulk loader sheet.
Use Administrator Tools > Bulk Load to import the bulk load sheet
Give users initial login password and instruct them to login to self care and update their password

Self Care Use Case 2:

Brown field customer is LDAP integrated.
Move LDAP sync from CUCM/CUC to CUCDM when customer is LDAP integrated as follows.
a) Turn Off Dir Sync Service at CUCM and CUCxn by going to Serviceability
b) At CUCDM select Customer Hierarchy and enter the LDAP Server config and LDAP User Sync
config
c) At CUCDM select Customer Hierarchy and perform LDAP Users Sync under USER Management->
Sync&Purge. This step is advised to run after CUCM and CUCxn Data Import are completed
d) Move Users to respective sites and run Easy Overbuild
Steps a), b) and c) can be done after Overbuild run too.

Self care will work with users LDAP password for all users now.
Need some tweaks for voicemail to work for new users added after migration to HCS which are
addressed below

Turnoff DirSync at CUCM and CUCXn

Configuring LDAP server in CUCDM

Configuration requirements for QAS

when CUCxn is LDAP integrated.
Take the following steps to use the Quick Add Subscriber method

a) Select Customer hierarchy and navigate to Role Management > Configuration Templates.
b) Click Default CUC User Template.
c) Click Action > Clone.
d) Rename the cloned template.
e) In the Ldap Type field, select Integrate with LDAP directory.
f) Click Save.
g) Navigate to Subscriber Management > Quick Add Subscriber Groups.
h) Select the default group(or clone the default group).
i) In the Default CUC User Template field, select the template you cloned in step d and save it.

CUC USER Template change for QAS

Configuration requirements for

Advanced Subscriber add when Unity
Connection is LDAP integrated.
Take the following steps to use the Advanced Subscriber method.

a) Select Customer hierarchy and navigate to Role Management > Field Display Policies.
b) Click the SubscriberAdvancedDefault policy.
c) Click Action > Clone.
d) In the Voicemail section, move CUCUser.LdapType from the Available column to the Selected
column.
e) When Voicemail is added to a Subscriber, set Integrate with LDAP directory for the field,
CUCUser.LdapType,

FDP SubscriberAdvancedDefault

New Sites Procedure

Mohammad Al-taraireh

Post-Overbuild Tasks for New Sites

Customer configures and manages dial plan related configurations on CUCM.

Import and sync new sites dial plan data in CUCM with CUCDM.
Create new sites hierarchy on CUCDM for the new locations created on CUCM.
Configure Site Defaults Doc with the corresponding site specific defaults for the
following.
General Defaults
Device Defaults
Line Defaults
User Defaults
CUC Defaults
HotDial Defaults
Day 2 MACD configurations for the new sites are prepopulated on GUI with the
defaults configured in Site Defaults Doc.

Post-Overbuild Tasks for New Sites

Configure new internal number inventory for the site.

Configure class of service tagging if desired
Configure E.164 number inventory and E.164 mapping to internal number inventory
This does not push down any new dial plan data to CUCM
This is for tracking equivalent E.164 dial plan data already configured on CUCM

Class of Service Tagging

Mohammad Al-taraireh

Class of Service Tagging

BYODP by default does not filter Calling Search Spaces (CSS) which are
used in various line and device drop down fields
The operator may desire to filter the CSS(s) that are presented for a
site line or device
A CUCDM dial plan class of service element can be configured to map
to/tag an existing CUCM CSS
CoS is site specific and can only tag CUCM CSSs that are moved into
the site hierarchy
Caveat: The tagging feature does not work for CSS(s) that are shared
between sites

CoS Tagging Step: Enable CSS Filtering

No CSSs will be available in drop downs after enable

CoS Tagging Step:

Create a Class Of Service Element

that maps to/tags an existing CUCM CSS

CoS Tagging: Verify CSS is Available on Line/Device

Purging of Customer Data

Mohammad Al-taraireh

Purging of customer brownfield data in

CUCDM (optional)
There may be a need to start a migration over and wipe all of the
existing customer imported data from the CUCDM (while leaving the
CUCM/CUC data intact)
Use the following procedure to clear the synced data in CUCDM

Login with reseller or above privilege and select the desired customer hierarchy
Go to the Data Sync menu under Administration Tools.
Click on the appropriate HcsPurge data sync item for the Unity connection publisher of the
customer
Ensure Sync Type = Purge Local Resorces. Purge Local Resources will delete synced data in
CUCDM only
Keep the default values for the data sync fields
Execute the Purge by clicking on the Execute button on the data sync page for the purge
data sync
After the CUCxn Purge is completed, perform the purge for the CUCM
Partner can then re-attempt the sync at this time by Executing the appropriate HcsPull
data sync from the same menu for CUCM and CUCxn
Partner can then re execute the HCS users move and overbuild procedures

Execute Purge For CUCxn data example

MISC Caveats & Notes

Mohammad Al-taraireh

Caveats

Call Pickup and Hunt groups These resources are included in the Day 2
menu but are not moved to a site during the Overbuild. They remain at the
customer hierarchy. They should be managed at either the CUCM or CUCDM,
but not both.

Overbuild/Device Models Menu These device model menu items should

typically be used for the purpose of manually moving device model instances.
Please continue to use the existing relevant menu items within CUCDM for
add, modify, and delete operations to maintain data consistency.

Expected Results

Call Handler device models There are 5 call handler device model instances
that remain at the customer hierarchy:

1.

Goodbye (CUC system default)

2.

Opening Greeting (CUC system default)

3.

Operator (CUC system default)

4.

operator (system user)

5.

undeliverablemessagesmailbox (system user)

CUC system users There are 2 system users that remain at the customer
hierarchy

1.

operator (system user)

2.

undeliverablemessagesmailbox (system user)

All associated CUC device models for these users remain at the customer hierarchy