...
Display will show the migrating sites under the Load Sites heading, select Re-Validate Migration. This will perform a final validation pre loading of objects into the target WxC-MT checking that objects ready and in the correct sequence
| Note |
|---|
Note, in 2.6.5 and lower versions, that wrangler_ will load Workspaces, a Workspace will be created for each supported phone device without owner Id in CUCM, it will not create and load associated phones. This needs to be done manually. Process here |
...
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
...
On rectification of issues and restart all objects loads OK
...
Workspace Device Load
As of yarn_man version 2.6.5, wrangler_ loads Workspaces but not Workspace devices into Webex Calling Control Hub. A workspace is created for every CUCM phone device of valid phone device type. The Workspace/s are named using the device name from CUCM and includes the phone number and or extension.
To load the required associated Workspace devices, from BAT phone export or such, extract Device Name, Directory Number (Extension), Device Type and Device Name, then creating a CSV file formatted as per below including header
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
...
Check under devices and Workspaces that all loaded OK
...
