Content Comparison

...

Ticket:

...

1. Log in ssh to yarnman server

2. at prompt, type sudo nano /opt/yarnlab/yarnman/workflow-service/helpers/migration/cucmtype sudo nano /assert-cucm-number-ranges.js

3. Line 90 needs to change from if (siteId == 'undefined') { to if (siteId == 'undefined' || !siteLookup[siteId]) {

4. When change done Ctrl O to write, then Ctrl X to exit editor

5. Then type sudo pm2 restart all

6. Log in to Wrangler and restart execution

...

1. Log in ssh to yarnman server

2. at prompt, type sudo nano /opt/yarnlab/yarnman/workflow-service/helpers/migration/cucmtype sudo nano /fast-cucm-syncer.js

3. Line 310 needs to change from

   await this.task.logError('unable-to-remove', `Object "${uuid}" of type "${sourceType}" had an unexpected error while trying to mark removed.`, { err });

...

Copy uuid (highlighted in sample belowabove) from error code in Wrangler as per sample below then paste this (converted into lower case) into CUCM GUI as https://<CUCM IP Address>/ccmadmin/phoneEdit.do?key=32b2f3dd-c406-5e36-8198-e503f0c44990

...

Solution: Hotfix , contact support for hotfix from ticket

UCMC/WxC-DI - Error Setting “A” of CUCM Line During Discovery Allocation Process

Version Seen : Yarnman Version 2.5.X and CUCM 14su3 or newer

This issue occur because an AXL change for getLine from CUCM version 14su3

Image Added

Image Added

Solution: Hotfix , contact support for hotfix from ticket [YMN-5574] UCMC - Discovery Error target CTI RP Line Error Setting A of CUCM-LINE must be string try set Object - JIRA (atlassian.net)