...
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 |
...
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
...