Document References

Document	Document Reference
Yarnman Installation & Setup	yarnlab legacy documentation - v2.5.x
Yarnman Administration	Yarnman Administration
Wrangler UCMC	Wrangler Webex Calling (WxC) MT + DI
Wrangler Map MOP	Wrangler WxC-DI MAP Migration MOP

Prerequisites

Item	Details
Connectivity	Firewall configured for access Yarnman to Source CUCM: port TCP 8443/443 Yarnman to Target CUCM: port TCP 8443/443 Kurmi to Target CUCM: Engineer to Yarnman: port HTTP/HTTPS/SSH
Access Credentials Source CUCM
Access Credentials Target WxC DI
Access Credentials Target Kurmi

Customer details

Item	Details	Notes
Customer Name and Code
Number of Sites
Sites to be migrated
Device Counts per site
User counts per site
Yarnman/ Wrangler Server	Hostname, IP Addresses
Source CUCM, IM&P Details	Hostname, IP Addresses
LDAP Integration	Yes/No
Kurmi

Migration Process Step by Step Guide

Migrate CUCM to WxC-DI using Wrangler Map

Complete Process here Wrangler WxC-DI MAP Migration MOP

Set Up Wrangler Application and Interfaces

No	Component	Item	Complete (YES/NO)
1	Wrangler	Build Yarnman server - process here yarnlab legacy documentation - v2.5.x
2	Wrangler	Initiate Wrangler service Wrangler WxC Service Setup
3	Wrangler	Create source CUCM and target WxC-DI interfaces Yarnman Administration \| Interfaces

Prepare Wrangler/ WxC-DI for Migration

No

Component

Item

Complete (YES/NO)

1

WxC-DI

Prepare Target WxC-Di for migration as per below and as required

Items that should be configured in target WxC-DI cluster prior to migration

Call Manager Servers
- These are created automatically with each CUCM node being installed
Call Manager Group (CMG)
- The call manager groups need to be created to suit the target cluster layout, if the number of subscribers is changing between source and target clusters care must be taken to ensure each subscriber has the approriate number of registrations based on OVA size
Media Resource Group Lists (MRGL)
- Media services, Media groups and Media Resource Group Lists need to be configured on the target cluster
Custom SIP Normalization Scripts
IP Phone Services
- Such as Extension Mobility
UC Service Profiles
User Profiles
VPN Profiles and VPN Groups
CUCM Native Dialplans loaded other than NANP
- Custom Dial Plan Tags
Any User Locales other than default (ENG-US) loaded
Custom Roles and Access Control Groups Note required from v2.5.15
Mobile Smart Client Profiles

Additionally if the cluster is LDAP integrated the following needs to be added

LDAP configuration in target cluster configured
LDAP Directory users to be synchronized prior to migration

Wrangler UCMC will update LDAP synchronized user configuration in the UCMC target but cannot add them

Unity Connection

Unity Connection Voice Port Group
Unity Connection Call Handler Templates *

*Special note for Unity Connection Call Handler Templates. If any Unity Connection System Call Handlers use Message Recipient as User with Mailbox, a System Call Handler Template with this setting must be created in target for mapping of these Templates

Version 2.5.16 note

Unity Connection Default Dialplan objects, Search Space and Partition, are “Default Matched” to target Defaults and renamed as per the source objects, this is to accommodate when the system default Unity Partition and Class Of Service has been updated

Additionally if the cluster is LDAP integrated the following needs to be added

LDAP configuration in target cluster configured
LDAP Directory users to be synchronized prior to migration

Wrangler UCMC will update LDAP synchronized user configuration in the UCMC target but cannot add them

2

Wrangler

Prepare/ Verify Mappings for Site Suggestions ensuring regexes match Device Pool Naming conventions. More on that here

wrangler_ WxC-DI Migration User Guide | Site Suggestions and here

wrangler_ WxC-DI Migration User Guide | Site Suggestion Examples

Wrangler Discovery

No	Component	Item	Complete (YES/NO)
1	Wrangler	Perform Initial Discovery process Wrangler WxC-DI MAP Migration MOP \| Wrangler Discovery and Initial Issue Review
2	Wrangler	On Completion of Discovery - Select ‘Site Suggestions’ Create required sites Then ‘Re-Allocate Migration’
3	Wrangler	Identify Sites and Number ranges to be used by Kurmi for Dialplan push to target WxC-DI from ‘Number Ranges->DN’ and 'Number Ranges->E164'

Kurmi Sunrise Configuration and Dialplan Push

No	Component	Item	Complete (YES/NO)
1	Kurmi	Login to Kurmi.
2	Kurmi	Create Tenant by selecting ‘Quick Tenant’ ,Create a new tenant.
3	Kurmi	Select the created tenant
4	Kurmi	Select ‘Scenarios → HCS - 10 Customer Initialization’ then Play Button on ‘10.05 - Customer Information’ Populate Required Information, then ‘Next>>’ Add Cluster Data Collection Info - ‘+ Add New Item’ Select Cluster as required Populate Cluster Information Cisco Unified Communication Manager (Publisher) populate as required + subscribers as required When all Pub’s and Sub’s populated - ‘Next>>’
5	Kurmi	Create Sites, Select ‘Scenarios → HCS - 35 Add Sites' Add Site Information, Site Dial Plan and Number Ranges, then Next When Site Info Loaded OK - repeat this step for next site until all sites loaded
6	WxC-DI	Log in to WxC-DI cluster to confirm that sites + Dial Plan objects loaded as required Device Pools Locations Regions Route Partitions CSS’s Translation Patterns Continue to Wrangler migration

Wrangler Map Migration

No	Component	Item	Complete (YES/NO)
1	Wrangler	Return to Wrangler migration to perform a Re-Discovery ‘Fast Re-Sync All' option On Completion of the resync, select ‘Issues’ from menu, followed by ‘Re-Allocate Migration’
2	Wrangler	Resolve Issues under ‘Issues & Resolutions’ and ‘Warnings’ Tabs Guide how to resolve these before progressing migration here Issues & Resolutions wrangler_ WxC-DI Migration User Guide \| Issues& Resolutions (below description and samples apply to single cluster migr... Warnings wrangler_ WxC-DI Migration User Guide \| Warnings When All Issues are Resolved, ‘Re-Validate Migration’
3	Wrangler	Proceed to Site selection and Prepare step - process here Wrangler WxC-DI MAP Migration MOP \| Prepare Sites Step
4	Wrangler	Next continue to Load Step - Follow Process In Load Sites Stage chapter Wrangler WxC-DI MAP Migration MOP \| Load Sites Stage
6	Wrangler	This completes the Wrangler Migration Component - proceed to Kurmi Inference process below

Kurmi Discovery/ Inference

No	Component	Item	Complete (YES/NO)	Notes
1a	Kurmi	Log In to Kurmi, select ‘Substitutions’ Select Tenant created
1b	Kurmi	Under Dictionary & Resources Extract Dictionary With All Values
1c	Kurmi	Under Packages select Extract With All Values
2	Kurmi	Select Advanced ‘Resources - > Users Lines/Devices’
3	Kurmi	Select ‘Lines → Discover → <Cluster Name>’ Then Repeat above for Devices and Users
4	Kurmi	All Users Lines Devices now imported