Overview
This guide documents the process to migrate CUCM to WxC-MT using wrangler_. This new feature is available from Yarnman version from 2.6.3 and complements the existing CUCM to WxC-DI functionality.
Prerequisites
The following are prerequisites for the migration
Yarnman Server Installed. Process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2916941825/Yarnman+Photon+Powered+YM-PH+-+Deployment+and+Installation#Yarnman-Deployment
wrangler_ service installed. Process here Wrangler WxC Service Setup
Interface to wrangler_ API integration with Webex cloud. Process Here. Yarnman (YM-PH) Interfaces
Interface configured to source CUCM. Process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2730393636/Yarnman+Administration#Interfaces
Migration Process
Link to demo of a CUCM to WxC-MT migration here
https://app.vidcast.io/share/f4285d8a-6ff0-43ad-a293-f0029c2879e3
Define Migration
To initiate the migration. From wrangler_ application select
Populate migration details including
Source Interface
Target Cloud Webex Account and Interface and Webex Org
Target Customer Name (Name the migration)
Then select ‘Save Migration & Start Discovery’ to initiate the discovery of source and target
Post Initial Discovery Tasks
On completion of the initial discovery/allocation/validation, a Summary page is displayed. From here, Sites need to be defined and validation issues/ warnings resolved
Site Creation from Site Suggestions
Selecting Site Suggestions Tab will display suggested sites. New Webex Locations can be created from the source by selecting ‘+MT Site Template “Webex Location”’ adjacent to the source siteID or the source sites can be mapped to existing Webex Locations sites by selecting ‘+MT Site Existing LOC’ followed by selecting the Webex Location to be mapped. When site selections have been completed, select the !Warnings tab
On Sites and how Site Suggestions are created can be found here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Sites and here https://yarnlab.atlassian.net/wiki/x/AQDGr
Warnings
The Warnings tab displays items that have triggered the rules but are information warnings only that may be attended to as required. Items that are highlighted under warnings can be missing e164 numbers, Intercom partitions and CSS's, Devices without Lines, Lines without Devices etc. If these require updating, select the blue button which will take you to the item in question. If no action is required for the individual item, the Red Button + Disable Rule and Clear Issue may be selected to clear the issue. When Warnings have been attended to, continue by selecting the Issues & Resolutions Tab
Issues & Resolutions
The Issues and Resolutions tab displays items that must be resolved before proceeding, sample screenshot below. These items will include items such as required licenses, numbers that can not be migrated to WxC-MT, required Mappings of object types etc. A complete list of validation rules and suggested resolutions of these can be found here https://yarnlab.atlassian.net/wiki/x/D4BWp . Once these issues have been resolved - select Re-Allocate Migration to proceed
After the Reallocation has been completed, there will be a number of new issues that need to be resolved under the Issues & Resolutions Tab. Resolve these , then select Re-Validate Migration
From sample migration, worth noting are the flagged Site objects missing addressing details, these may be solved individually by selecting the blue Manually Resolve In Site button, which will take you to the site object where the required address details may be completed, or all sites details may be resolved in bulk by selecting Sites (ver <2.6.5) or Allocation->Sites (ver =>2.6.5) from the main menu and from there export CSV of the sites. These addressing details may then be added to the CSV using Excel or such, then CSV uploaded to wrangler_ using Import option. More on this here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Sites
There may also be objects that must be mapped such as with the CUCM-CSS’s in screenshot below. These may be mapped by selecting the Manually Resolve Unmapped button or by selecting menu option Target Mappings and resolve from there. More on Target Mappings here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2756444161/Wrangler+UCMC+Administration+Guide#Target-Mappings-WxC-MT
When all issues are resolved, select Re-Validate Migration
Tip: If you receive many errors for invalid numbers, you may need to add country to the site where errors are or default country not added. The default country may be added under Dialplan->Configuration- Numbers Tab. Individual site country can be added under Allocation->Sites, then select the relevant country from Country field, in override column + Save, then perform reallocation
Prepare Sites stage
On resolving issues and revalidation successfully completed, the ‘three migration step’ screen is displayed. To progress from here, we now need to select what sites should migrate.
To do this, select Sites (ver <2.6.5) or (Allocate->Sites (ver =>2.6.5) from menu, then select sites to migrate from the Select column or all sites may be selected by using Bulk Select. When completed, select Ready
from menu
Selected sites will display under Prepare Sites heading, select Re-Validate Migration to progress migration.
On successful validation, select Preview Prepare, then Start Migration. This will transform all objects within wrangler_ database ready for load in to WxC-MT
On successful prepare of objects , select Continue Migration to proceed to the load stage
Load Stage
Display will show the migrating sites under the Load Sites heading, select Re-Validate Migration. This will perform a final validation pre the loading of objects into the target WxC-MT, verifying that objects are ready and in the correct sequence
Note, in 2.6.5 and lower versions, that wrangler_ will load Workspaces (a Workspace will be created in WxC MT for each supported phone device without owner Id in source CUCM), but it will not create and load associated phones. This needs to be done manually. Process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2917793858/wrangler+WxC-MT+Migration+User+Guide#Workspace-Device-Load
Resolve any issue flagged pre load - in sample migration, we need to add Timezone for the Toronto Location and Add the correct state code for London Location. Once resolved, Re-Validate Migration
Ready to Load objects into target, Select Preview Load followed by Start Migration
Objects Loading
On completion of load, check for any errors during load by selecting the Events Tab and Errors box which will display the errors. Selecting the error will display the error detail and which object failed. In sample migration, 2 phone devices failed to load as they were duplicates of existing MAC addresses. To resolve - there will be a link within the error detail linking to object detail (can also be accessed using Object->Browse from menu then finding the detail of the offending object) where the error can be corrected and load process restarted by selecting Restart Execution Process
On rectification of issues and restart all objects loads OK
Advanced Features
Number mapping and Normalisation
added in v2.6.6
Webex Calling Multi Tenant (WxC-MT) requires Telephone number to be valid and outside the US to be in e.164 format - wrangler_ will automatically validate all number and if valid generate the source-infra-number object
If numbers are not valid validation issues will be raise
This feature was added for WxC-MT migration to automatically normalise numbers - this can be reviewed in Discovered Numbers - Number Mappings
Supported infra source transformation
External CLI will only be automatically populated if the CUCM-LINE pattern is in Full National Number (FNN) format and either the default country or site country is set
The infra-source will need to be updated to included the external CLI if there is asymetrical CLI - inbound number is different to outbound CLI if the CUCM-LINE pattern is an extension
Source DN Type | Source e164 Number Mask type | Example Country | Example Source DN | Example source mask | Example source infra extn / e164 / external-cli |
|---|---|---|---|---|---|
Extn | e.164 | USA | 35111 | +121299851XX | 35111 / +12129985111 / null |
Extn | null | null | 22123 | 22123 / null / null | |
Extn | FNN | USA | 5633 | 61525356XX | 5633 / +16152535633 / null |
Extn | invalid | null | 22124 | 22124 / null / null | |
FNN | FNN | 35113 | +121299851XX | 35113 / +12129985113 / null | |
FNN | e.164 | USA | 6152535643 | +16152535600 | 6152535643 / +16152535643 / +16152535600 |
FNN | null | USA | 16152535622 | null | 6152535622 / +16152535622 / null |
FNN | invalid | USA | 6152535622 | 0000000000 | 6152535622 / +16152535622 / null |
e.164 | USA | \+61292205129 | null / +61292205129 / null |
Unsupported infra source transformation
CUCM Directory Number | External Number Mask | Source Infra | Example Country | Example source DN | Example source mask | Example source infra | Notes |
|---|---|---|---|---|---|---|---|
Extn | US 7digt | USA | 5633 | 25356XX | No supported |
Acronyms
Extn - Extension
FNN - Full National number
Device-Lines - the mapping on devices to lines
If the line is in FNN format and has a leading 0 (e.g. AUS/GBR) this will be stripped from the source infra extension
DN 02071236000 + Mask +442071236000 - Source Infra 2071236000 / +442071236000
DN 02071236001 + Mask XXXXXXXXXXX- Source Infra 2071236001 / +442071236001
Masking is supported with X’s but not patterns i.e. [1-3]XX
Normalisation using FNN requires that sites are created with the country set and re-allocation to be run
Number mappings - Bulk Change
Added in wrangler_ 2.6.8
Bulk change was added to the number mappings view to enable bulk skipping / reset / force and map to existing number
This may be used if you need to clear the number mappings to infra-source if the countries were not correctly set initally or to force invalid FNN/e164 numbers that are used for non-DID services
Number mappings - Export Numbers
Added in wrangler_ 2.6.8
This provide an excel export of the number mapping view
Transformation template modifiction - edit user numbers
Process to load WxC-Persons without phone numbers but with Extensions
Select and edit Schema Templates
Transformation template modifiction - edit user numbers
Process to load WxC-Persons without phone numbers but with Extensions
Select and edit Schema Templates
Find and Open Webex Calling Person xform template
Select Override Template
Scrool down to phoneNumbers
For example edit the template to trim the extension field from FNN to 6 digits use the following macros
wxc-person
cucmUserNumbersForWxCPersonV1.suggestedExtensionNullWhenNationalNumberElseTrimmed6CharsOrLess
wxc-workspace
cucmPhoneNumbersForWorkspace.suggestedExtensionNullWhenNationalNumberElseTrimmed6CharsOrLess
wxc-virtual-line
wxcVirtualLine.suggestedExtensionNullWhenNationalNumberElseTrimmed6CharsOrLess
wxc-hunt-group
wxcHuntGroupNumbers.suggestedExtensionNullWhenNationalNumberElseTrimmed6CharsOrLess
wxc-call-queue
wxcCallQueueNumbers.suggestedExtensionNullWhenNationalNumberElseTrimmed6CharsOrLess
Modification of other fields in transformation template
The Preview template can be used to find all the availible fields for that template
Virtual Line Transformation
added in v2.6.6
Virtual lines are detected by looking at the appearances of a CUCM-LINE and then running a check to see if that line is a primary line and if it is not a primary line and meets the conditions of the virtual line it is set to transform - this is done on the INFRA-SOURCE-Number object
Primary Lines (PL) and Virtual Lines can also be seen in Discovered Numbers - Number mappings PL/VL will show when linked to a CUCM-LINE in the target column
In 2.6.6 virtual lines will only transform if Phone line label & display, line alerting name and description are populated - this will be behaviour will change in a future release so that mandatory missing data after prepare and validated
If there is missing data wrangler_ will pause with issues during the prepare step
If you wish to skip the virtual lines with issue in bulk use target mappings for infra-source-number 🡆 wxc-virtual-line and perform
filter by “Only Issues”
Update using “Skip as Source / Not Used?”
Update again using “Skip Template Binding”
Then remove the breakpoint where the prepare process paused and restart
Bulk Changes Workbook
added in v2.6.6
This is was added for Webex Calling objects with limited fields in 2.6.6 additional fields will be added in a future release as will CUCM objects
The bulk changes workbook feature allows you to review data in an excel workbook format - typical use cases are
Review and update data after prepare
Correct data during load
It is found under Bulk Changes - Workbook
Object types can be selectedwith filters to refine data returned
The excel report can then be downloaded and edited
Some possible chages are listed below make the appropriate changes in excel and save
Description | Error | Original | Updated |
|---|---|---|---|
WXC-HUNT-GROUP and WXC-CALL-QUEUE name lengh is a max of 30 chars |
| name 0298985190 - Syd Sales Hunt Group | name 0298985190 - Syd Sales |
name and firstname must not start with special chars Generic error does not include \ or + |
| name or firstName \+61298985194 - Syd Sales Hunt Group | name or firstName 61298985194 |
change phone number or extension | work:+12129985302 | work:+12129985355 |
Create an import by workbook task
once imported a report of the changes will be provided
Workspace Device Load
In wrangler 2.6.5, wrangler_ loaded Workspaces but not Workspace devices into Webex Calling Control Hub. A workspace is created for every CUCM phone device of valid phone device type with no owner UserId. This was resolved in 2.6.6