Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

...

Info

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

...

image-20241022-034822.pngImage Added

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

...

When all issues are resolved, select Re-Validate Migration

Info

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.

...

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

...

Workspace Device Load

...

...

Username

...

Type

...

Extension

...

Device Type

...

Model

...

MAC Address

...

<CUCM Device Name>

...

WORKSPACE

...

<CUCM Directory Number>

...

WEBEX_CALLING

...

<CUCM Device Type>

...

<MAC Address, last 12 from CUCM Device Name>

...

<CUCM Device Name>

...

WORKSPACE

...

<CUCM Directory Number>

...

IP

...

<CUCM Device Type>

...

<MAC Address, last 12 from CUCM Device Name>

...

Sample

...

SEP777777555555

...

WORKSPACE

...

35105

...

WEBEX_CALLING

...

Cisco 7841

...

77777655555A

After getting required info from CUCM, log in to Control Hub → Select Workspaces to confirm that they have been created

...

Then select Devices → Add Device

...

Select Multiple Cisco IP Phones - Next

...

Select the csv file created to upload - then Submit

...

image-20240214-034551.pngImage Removed

Check under devices and Workspaces that all loaded OK

...

image-20240214-034826.pngImage Removed

Advanced Features

Number mapping and Normalisation

...

This feature was added for WxC-MT migration to automatically normalise numbers - this can be reviewed in Discovered Numbers - Number Mappings

image-20240520-083700.png

image-20240530-043241.pngImage Added

Supported infra source transformation

...

CUCM Directory Number

...

External Number Mask

...

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

5633 / +16152535633

Source DN Type

Source e164 Number Mask type

Example Country

Example source Source DN

Example source mask

Example source infra

Extn

FNN

extension / e.164

USA

5633

61525356XX
+16152535633

extn / e164 / external-cli

Extn

e.164

extension / e.164

USA

35111

+121299851XX
+12129985111

 35111 / +12129985111 / null

Extn

null

extension

null

22123

22123 / null / null

Extn

FNN

USA

5633

61525356XX
+16152535633

5633 / +16152535633 / null

Extn

invalid

extension

null

22124

22124 FNN/ null / null

FNN

FNN / e.164

35113

+121299851XX
+12129985113

 35113 / +12129985113 / null

FNNe.164

FNN / e.164

USA

6152535643

+16152535600

 6152535643 / +16152535643 / +16152535600

FNN

null

FNN / e.164

USA

615253562216152535622

null

 6152535622 / +16152535622 / null

FNN

invalid

FNN / e.164

USA

6152535622

0000000000
+16152535622

 6152535622 / +16152535622 e.164/ 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

...

Info

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

...

Select and edit Schema Templates

 

...

image-20240529-114342.pngImage Added

 

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

...

Scrool down to phoneNumbers

...

Edit to null, then Save Changes

image-20231220-045136.pngImage Removedimage-20231220-045152.pngImage Removed

 Repeat as needed forFor 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

  • wxc-virtual-line

  • wxc-auto-attendant
    • wxcCallQueueNumbers.suggestedExtensionNullWhenNationalNumberElseTrimmed6CharsOrLess

...

image-20240529-115057.pngImage Added

Modification of other fields in transformation template

...

once imported a report of the changes will be provided

image-20240520-073333.png

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