Støttede telefoner opprettes automatisk og tilordnes brukere i Webex Calling av klargjøringsverktøyet. Telefonene merket "Ja" i kolonnen "Støttes i flyttingsverktøyet for enheten" flyttes også automatisk fra Cisco BroadWorks eller BroadCloud til Webex Calling når flyttingsverktøyet for enheten kjøres. Telefoner merket "Nei" i den kolonnen trenger en manuell inngripen for å endre DMS URL-adressen i Cisco BroadWorks-enhetsmalen eller i selve telefonen.

Den siste kolonnen inneholder tilordningen av telefonmodeller til kolonnen «Enhetstype» i filen transform-tool/input/newphones.csv. (Se delen Transformeringsverktøy i denne artikkelen for mer informasjon om newphones.csv).

Partneradministratorer kjører dette tokengeneratorverktøyet minst én gang før de starter å kjøre overføringsverktøy. Å kjøre dette verktøyet er en engangsaktivitet etter at partnerkontoen blir innlemmet i Wholesale RTM-løsningen. Dette verktøyet gjør det mulig for partneradministratorer å logge på via nettleseren for å få det unike TOKEN som er nødvendig for å oppdatere til partnerkonfigurasjonsfilene for overføringsverktøyene.

Forutsetninger

Etter nedlasting, pakk ut overføringsverktøybinærene.

Angi banen for JRE/JDK-miljøet i token_generator.sh for MAC og token_generator.bat for Windows. Hvis JAVA_HOME-banen allerede finnes, brukes den på nytt av verktøyet.

• mac: JAVA_HOME="/Users/cisco/jdk/zulu@1.8.282/Content/Home/"

• Vinduer: JAVA_HOME=C:\Forbedring~1\Java\jre1.8.0_321

Instruksjoner å kjøre

Kjør følgende kommando i terminalen inne i tokengeneratorkatalogen:

Vinduer:

token_generator.bat

MacOS

./token_generator.sh

Utgang:

Verktøynavn: Token Generator verktøyversjon: 1.13.0 Last inn URL-adressen i nettleseren din: http://localhost:8080 

Åpne URL-adressen i nettleseren på terminalen, logg på med partneradministratorlegitimasjonen for å få TOKENET og kopier det samme for videre bruk.

Illustrasjonene i brukergrensesnittet er gitt nedenfor for referanse:

Figur 3: Logg på med Cisco Webex

Figur 4: Vinduet for legitimasjon

Figur 5: Tokengenerasjon

Konfigurer følgende trinn før du kjører verktøyene for utvinning og flytting av enheter i den sekundære BroadWorks-serveren.

Aktiver OCI-P-tilkobling

Flytteverktøyet for enheten kommuniserer med BroadWorks via OCI-P-kommandoer, for å aktivere OCI-P-tilkobling, bruk trinnene nedenfor:

Trinn 1: Bruk CLI til å konfigurere generelle innstillinger.

Kjør følgende kommando i CLI for å bytte til katalogen GeneralSettings:

AS_CLI> CD /Applications/OpenClientServer/GeneralSettings.

Kjør følgende kommando i CLI for å få gjeldende GeneralSettings:

AS_CLI/Applications/OpenClientServer/GeneralSettings> get clientPort = 2208 clientPortEnabled = true secureClientPort = 2209 secureClientPortEnabled = true systemDomain = <> 

Hvis innstillingene ikke samsvarer med det ovennevnte, bruker du kommandoen set til å konfigurere innstillingene på nytt.

Trinn 2: Bruk CLI til å konfigurere OCI-proxyen.

Endre katalogen til OCI Proxy:

AS_CLI> CD /Applications/OpenClientServer/OCIProxy

Kjør følgende CLI for å få gjeldende innstillinger. Du bør se følgende:

AS_CLI/Applications/OpenClientServer/OCIProxy> get enabled = true enabledLoginNivåScreening = false enableResponsCaching = false responseCacheVarighetTimer = 24 responsCacheRenewPeriodMinutter = 30 meldingKøKapasitet = 50 meldingKøTidsavbruddSekunder = 1800 

Hvis innstillingene ikke samsvarer med det ovennevnte, bruker du kommandoen set til å konfigurere innstillingene på nytt.

Trinn 3: Bruk CLI til å konfigurere OCI-klargjøring.

Endre til klargjøringskatalogen:

AS_CLI> cd /System/NetworkAccessLists/OCI/Provisioning

Kjør følgende kommando for å få de gjeldende OCI-klargjøringsinnstillingene:

AS_CLI/System/NetworkAccessLists/OCI/Provisioning> få adressebeskrivelse ======================== 127.0.0.1 lokal som 

Trinn 4: Kjør kommandoen nedenfor i CLI for å bekrefte at konfigurasjonen er riktig.

 AS_CLI/Maintenance/ManagedObjects> få broad works og sjekk at utdataene ser OK ut. Se nedenfor for prøveutdata: AS_CLI/Maintenance/ManagedObjects> få broadWorks BroadWorks-administrerte objekter ========================== * Server: Identitet..............: AS-versjon...............: Rel_21.sp1_1.551 Administrativ tilstand..: Ulåste * Programmer: Navneversjon Distribuert Administrativ tilstand Effektiv tilstand ========================================================================================= Utførelse og klargjøring 21.sp1_1.551 true Ulåst Ulåst FlashPolicy 21.sp1_1.551 false Ulåst Stopped OpenClientServer 21.sp1_1.551 true Ulåst Ulåst WebContainer 21.sp1_1.551 true Ulåst Ulåst 4 oppføringer funnet. * Vertsbaserte programmer: Navneversjon Context Path Distribuert ================================================================== CommPilot 21.sp1_1.551 / true DeviceManagementFiles 21.sp1_1.551 /DeviceManagement true JWSFiles 21.sp1_1.551 /FileRepos true MediaFiles 21.sp1_1.551 /media true OCIFiles 21.sp1_1.551 /ocifiles true 5 oppføringer funnet. 

Bekreft distribuert og aktiv åpen klientserver

Bruk kommandoene nedenfor til å distribuere og starte Åpne klientserveren på den sekundære programserveren hvis den ikke er distribuert eller ikke allerede har startet.

Trinn 1: Distribuer serveren med følgende CLI-kommando:

AS_CLI/Maintenance/ManagedObjects> distribuer programmet OpenClientServer

Trinn 2: Start serveren med denne kommandoen:

AS_CLI/Maintenance/ManagedObjects> starte programmet OpenClientServer

Aktiver aktivering av numre

Utfør følgende kommandoer i CLI for å aktivere aktivering av numrene:

Trinn 1: Kjør kommandoen for nummeraktivitet:

AS_CLI> cd SubscriberMgmt/NumberActivation

Trinn 2: Kjør aktivert kommando:

AS_CLI> set dnMode groupAndUserActivationEnabled

Trinn 3: Skriv inn Y ved bekreftelsesmeldingen.

For BroadCloud

Utvinningsverktøyet er integrert i BroadCloud-tjenesteleverandørportalen. Administrator for en tjenesteleverandør kan:

1. Send ut forespørsler om utdrag for opptil 50 kunder per forespørsel.
   Utdrag forespørsel kan ikke sendes inn for samme kunde mer enn 10 ganger i løpet av en dag.
2. Last ned den utpakkede datafilen, i ZIP-format, i opptil 28 dager fra datoen for forespørsel.

Tallene nedenfor viser tjenesteleverandørportalen.

Figur 6: Tjenesteleverandørportal

Figur 7: Tjenesteleverandørportal

For Cisco BroadWorks og Webex for BroadWorks

1. Utpakkingsverktøyet kjører på den sekundære Cisco BroadWorks Application Server i partnernettverket og kobles til via OCI-P.
2. Verktøyet henter rå data fra bedrifter, grupper, numre, brukere, tjenester, enheter og myke klienter fra Cisco BroadWorks- eller BroadCloud-plattformen og sender disse dataene til XML-filer som gir inndataene for transformeringsverktøyet.

De neste delene forklarer hvordan du installerer og konfigurerer utvinningsverktøyet.

Forutsetninger

1. SCP utvinningsverktøybinærene til sekundær Cisco BroadWorks Application Server.
2. SSH til den sekundære Cisco BroadWorks Application Server for å konfigurere forutsetningene og kjøre utvinningsverktøyet.
3. Konfigurer tjenesteleverandøren og gruppe-ID-en til å trekke ut fra Cisco BroadWorks i conf/exportTool.yml. Se YAML-utskriften nedenfor:

   Tjenesteleverandør ID-A:      - GroupID-A1 - GroupID-A2 - GroupID-A3 ServiceProviderID-B:                        - alle 

4. Kontroller at den sekundære bruker-ID, passord og vertsnavnet for Cisco BroadWorks-programserveren er riktig i filen conf/partner.cfg:

   BROADWORKS_BRUKER_ID = admin BROADWORKS_PASSORD = admin BROADWORKS_VERT_NAVN = localhost OPPDATERING_TOKEN = partneradministratorens oppdateringstoken kopiert fra tokengeneratorverktøyet. MIGRERINGSMODUS_ = Støttede verdier er webex_for_broadworks_to_wholesale. Standardverdien er broadworks_to_wholesale. Bruk webex_for_broadworks_to_wholesale for Webex for BroadWorks-overføringer. 

   Egenskapen OPPDATER_TOKEN er obligatorisk for en Webex for BroadWorks-migrering.

5. Endre JDK/JRE-miljøbanen i export.sh-filen hvis den sekundære Cisco BroadWorks Application Server JDK/JRE-miljøbanen er forskjellig fra filen:

   JAVA_HOME=/usr/local/java/java_base

Instruksjoner å kjøre

Kjør kommandoen nedenfor i den sekundære Cisco BroadWorks Application Server fra utvinningsverktøykatalogen:

./export.sh

Terminallogger

Følgende logger er tilgjengelige i terminalen ved vellykket eksport: Kjører BroadSoft Data Export Tool:

 Kjører BroadSoft Data Export Tool ************************************************ Starter Export Tool v: 1.15.0 Eksport startet for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg Eksport av brukere for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg Eksport av brukere fullført for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg Eksport fullført for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg Eksport fullført Export Dump Zip Directory : utdata/20221017223452_ExportTool Export Dump Zip-filnavn:extracted_data_1666060500618.zip Zip-fil med navnet extracted_data_1666060500618.zip har blitt opprettet ZIP-filopprettelsesprosessen fullført Eksporterte filer konvertert til ZIP-fil ************************************************** 

Utdata

En utdatafil ZIP (extracted_data_.zip) vil være tilgjengelig i samme utdataverktøykatalog. Bruk kommandoen nedenfor for å vise og bruke ZIP-filen for inndata for transformeringsverktøy:

ls –ltr drwxr-xr-x 2 bwadmin bwadmin 4096 okt  4 11:53 lib/ -rwxr-xr-x 1 bwadmin bwadmin 956719 okt  4 11:53 exportTool.jar -rwxr-xr-x 1 bwadmin bwadmin 2635 okt  4 11:53 export.sh drwxr-xr-x 2 bwadmin bwadmin 4096 okt  5 05:04 konf/ drwxrwxr-x 3 bwadmin bwadmin 4096 oktober 17 22:34 utgang/ drwxrwxr-x 2 bwadmin bwadmin 4096 oktober 17 22:34 logger/ -rw-rw-r-- 1 bwadmin bwadmin 46341 oktober 17 22:35 extracted_data_1666060500618.zip 

Dette transformeringsverktøyet kjøres for alle overføringer. Transformeringsverktøyet kjører på en hvilken som helst datamaskin, inkludert en partnerens administratorbærbare datamaskin, og bruker Webex Public API-er. Den leser ZIP-filen (extracted_data_.zip) som en inndata og konverterer den rå XML til et JSON-format som brukes av klargjøringsverktøyet.

Forutsetninger

Når du har lastet ned og ekstrahert de binære overføringsverktøyene, konfigurerer du følgende forutsetninger:

1. Angi REFRESH_TOKEN (token kopiert fra tokengenereringsverktøyet) og NAVNET_PÅ_HOVEDPLASSERINGEN_ i filen conf/partner.cfg:

   OPPDATERING_TOKEN=MzUwYjljODEtYmQ4MS00NGVhLTgwNGUtZjQ1NTEyZTViNzJkOTdj NAME_OF_MAIN_LOCATION=Main 

2. Angi eventuelt KLARGJØRINGS-ID_ (kopiert fra malen i Partner Hub) i filen conf/partner.cfg:

   KLARGJØRING_ID=YmE4MjFkZGYtYTlkNy00NDdlLWIwODctYmNkOTM2NjUyYWQ1

   For å få mer fullstendig bekreftelse av kundens e-postadresse kan du eventuelt angi KLARGJØRINGS-ID_.
3. Konfigurer manglende informasjon i inndata/customers.csv-filen (se neste avsnitt) hvis den mangler.
4. Legg til sluttbrukerens e-postadresse i inndata/users.csv-filen.
5. Hvis nye telefoner skal klargjøres, legger du til mac-adressen og e-postadressen til brukerens nye telefon i inndata/newphones.csv-filen. Dette er kun nødvendig hvis partneradministratorene ønsker å klargjøre nye telefoner i engrossamtaler.
6. Konverter BroadWorks Call Centers til CxEssentials ved hjelp av input/cxessentials.csv-filen.
7. Du kan også aktivere egenskapen OPPGRADERE_ALLE_SAMTALESENTRE__TIL_CX_ESSENTIALS for å konvertere alle samtalesentre til CxEssentials.
8. Bruk inndata/locations.csv-filen til å støtte den store bedriftsmigreringen som gjør det mulig for administratorer å migrere kundens steder etter sted
9. Du kan også aktivere bruk av MAC-adresser fra User-Agent-toppteksten i SIP REGISTER-meldingen når MAC-adressen ikke er tilgjengelig i Cisco BroadWorks-enhetsprofilen. Fjern kommentaren på linjen «USE_MAC_ADDRESS_FROM_SIP_REGISTER=yes» i filen conf/partner.cfg

Fylling av inndata/customers.csv

Filinndataene/customers.csv inneholder data som kanskje mangler i Cisco BroadWorks eller BroadCloud. Denne filen kan stå tom hvis all obligatorisk informasjon allerede er tilgjengelig. Du trenger ikke å fylle ut alle kolonner, bare den manglende informasjonen er obligatorisk.

Tabellen nedenfor forklarer de viktigste kolonnene i inndata/customers.csv.

Instruksjoner å kjøre

Kjør transformeringsverktøyet i et hvilket som helst operativsystem. Bruk trinnene nedenfor for å kjøre verktøyet i Windows og macOS:

Windows

Utfør kommandoen nedenfor for å kjøre transformeringsverktøyet i Windows:

transform.bat -extract= -customers= -users= -newphones=

macOS

Utfør følgende trinn for å kjøre transformeringsverktøyet på macOS:

1. Opprett et virtuelt miljø og installer avhengigheter for å kjøre transformeringsverktøyet ved hjelp av Python:

   python3 -m venv venv source venv/bin/activate python3 -m pip install requests python3 -m pip install requests-oauthlib 

2. Kjør transformeringsverktøyet:

   ./transform.sh -extract= -customers= -users= -newphones=

Forhåndskontroll av kunde/bruker

Transformeringsverktøyet foretar API-anrop til Webex for å fange opp potensielle klargjøringsproblemer. Som standard vil den validere kundens adresse og primære e-post. Hvis PROVISIONING_ID-verdien er angitt i filen conf/partner.cfg, vil den også validere stedsinformasjon. Resultatene av forhåndskontrollen er inkludert i unntaksrapporten.

Additionally, the following optional parameters can be added when running the transform tool:

precheck

In addition to running the precheck API for the customer information, the Transform Tool will also run the precheck API for the subscriber emails.

precheckinfo

By default, only precheck errors (i.e., issues that will block provisioning) are included in the exception report. Adding this flag will include successful precheck results as well (e.g., if a Webex organization already exists that can be automatically attached).

Terminal logs

The following logs in the terminal on successful transform:

Summary Report BroadWorks enterprises that can be successfully migrated: 1 BroadWorks enterprises that cannot be migrated: 0 BroadWorks users that can be successfully migrated: 4 BroadWorks users that cannot be migrated: 0 Phones that can be successfully migrated: 3 Phones that are not compatible with Webex Calling: 0 

Exception report

Transform Tool generates the exception report inside the output/<timestamp>/exception_report.txt directory. You can use this report to identify the issues that will affect the migration and fix them in the Cisco BroadWorks system.

After modifying the user data to resolve the exception, rerun the Extract and Transform Tools with the new data. The sample exception report file as follows:

Exception Report Tue Oct 18 08:12:09 2022 Enterprises with Communication Barring Feature Recommendation: manually configure the Outgoing Calling Plan in Control Hub ________________________________________________________________________________ collabmigrationtestGRP_engg 

Output

An output JSON (customer.json) file will be available in the output/<timestamp>/<groupid> directory. The sample customer.json file is as follows:

{ "customer": { "provisioningId": "!!!!!!!!!!REPLACE_WITH_PROVISIONINGID!!!!!!!!!!", "packages": [ "webex_calling", "common_area_calling" ], "externalId": "external_id_engg_grp1", "address": { "addressLine1": "100 Main Street", "addressLine2": "", "city": "Gaithersburg", "stateOrProvince": "MD", "zipOrPostalCode": "20877", "country": "US" }, "customerInfo": { "name": "Engineering Group - 1", "primaryEmail": "amareswaranvel+engineeringgroup1@gmail.com" }, "provisioningParameters": { "calling": { "location": { "name": "Main", "address": { "addressLine1": "100 Main Street", "addressLine2": "", "city": "Gaithersburg", "stateOrProvince": "MD", "zipOrPostalCode": "20877", "country": "US" }, "timezone": "America/New_York", "language": "en_us", "numbers": [ "+15205551101", "+15205551102", "+15205551103", "+15205551104", "+15205551105", "+15205551106", "+15205551107", "+15205551108", "+15205551109", "+15205551110" ], "mainNumber": "+15205551101" } } } }, "broadworks_info": { "service_provider_id": "collabmigrationtestSP_engg", "group_id": "collabmigrationtestGRP_engg" }, "subscribers": [ { "amareswaranvel+benjaminjack@gmail.com": { "subscriber": { "customerId": "!!!!!!!!!!REPLACE_WITH_CUSTOMERID!!!!!!!!!!", "email": "amareswaranvel+benjaminjack@gmail.com", "package": "webex_calling", "provisioningParameters": { "firstName": "Benjamin", "lastName": "Jack", "primaryPhoneNumber": "+15205551102", "extension": "1102" } }, "features": [ { "/v1/people/{personId}/features/voicemail": { "enabled": true, "sendBusyCalls": { "enabled": true, "greeting": "DEFAULT" }, "sendUnansweredCalls": { "enabled": true, "greeting": "DEFAULT", "numberOfRings": 3 }, "messageStorage": { "mwiEnabled": true, "storageType": "EXTERNAL", "externalEmail": "engineering17861@mailnator.com" } } } ], "devices": [ { "cisUuid": "!!!!!!!!!!REPLACE_WITH_PERSONID!!!!!!!!!!", "product": "DMS Cisco 7861", "mac": "CC98914EAAD7" } ] } }, { "amareswaranvel+lucasoliver@gmail.com": { "subscriber": { "customerId": "!!!!!!!!!!REPLACE_WITH_CUSTOMERID!!!!!!!!!!", "email": "amareswaranvel+lucasoliver@gmail.com", "package": "webex_calling", "provisioningParameters": { "firstName": "Lucas", "lastName": "Oliver", "primaryPhoneNumber": "+15205551103", "extension": "1103" } }, "features": [ { "/v1/people/{personId}/features/voicemail": { "enabled": true, "sendBusyCalls": { "enabled": true, "greeting": "DEFAULT" }, "sendUnansweredCalls": { "enabled": true, "greeting": "DEFAULT", "numberOfRings": 3 }, "messageStorage": { "mwiEnabled": true, "storageType": "EXTERNAL", "externalEmail": "engineering16821@mailnator.com" } } } ], "devices": [ { "cisUuid": "!!!!!!!!!!REPLACE_WITH_PERSONID!!!!!!!!!!", "product": "DMS Cisco 6821", "mac": "5486BCAE7E45" } ] } }, { "amareswaranvel+leojackson@gmail.com": { "subscriber": { "customerId": "!!!!!!!!!!REPLACE_WITH_CUSTOMERID!!!!!!!!!!", "email": "amareswaranvel+leojackson@gmail.com", "package": "webex_calling", "provisioningParameters": { "firstName": "Leo", "lastName": "Jackson", "primaryPhoneNumber": "+15205551104", "extension": "1104" } }, "features": [ { "/v1/people/{personId}/features/voicemail": { "enabled": true, "sendBusyCalls": { "enabled": true, "greeting": "DEFAULT" }, "sendUnansweredCalls": { "enabled": true, "greeting": "DEFAULT", "numberOfRings": 3 }, "messageStorage": { "mwiEnabled": true, "storageType": "EXTERNAL", "externalEmail": "engineeringmacpc@mailnator.com" } } } ], "devices": [] } }, { "amareswaranvel+owenalex@gmail.com": { "subscriber": { "customerId": "!!!!!!!!!!REPLACE_WITH_CUSTOMERID!!!!!!!!!!", "email": "amareswaranvel+owenalex@gmail.com", "package": "webex_calling", "provisioningParameters": { "firstName": "Owen", "lastName": "Alexander", "primaryPhoneNumber": "+15205551101", "extension": "1101" } }, "features": [ { "/v1/people/{personId}/features/voicemail": { "enabled": true, "sendBusyCalls": { "enabled": true, "greeting": "DEFAULT" }, "sendUnansweredCalls": { "enabled": true, "greeting": "DEFAULT", "numberOfRings": 3 }, "messageStorage": { "mwiEnabled": true, "storageType": "EXTERNAL", "externalEmail": "engineering8811@mailnator.com" } } } ], "devices": [ { "cisUuid": "!!!!!!!!!!REPLACE_WITH_PERSONID!!!!!!!!!!", "product": "DMS Cisco 8811", "mac": "F87B204E4066" } ] } } ], "auto_attendants": [], "call_queues": [], "hunt_groups": [], "schedules": [], "call_parks": [], "call_pickups": [], "paging_groups": [], "voice_portals": [ { "name": "Automated Voice Portal", "firstName": "Automated", "lastName": "Voice Portal", "languageCode": "en_us", "phoneNumber": "+15205551105", "extension": "1105" } ], "shared_call_appearances": [], "business_communicator_desktop_to_upgrade_to_webex_app": [ "PC Comm - Engg Device Profile" ], "connect_client_to_upgrade_to_webex_app": [], "locations": [], "webex_for_broadworks_info": { "users": [ { "id": "Y2lzY29zcGFyazovL3VzL1NVQlNDUklCRVIvY2QzNGViNWYtYTVmMi00OWQ1LTlkNWMtZTg1MDJiMDE4YTQ5" } ], "hydra_orgId": "Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi9jMjJiYTMwNC1mODQ4LTRlOTktYWFmYy0zYWRlMjBmYTgzZTg", "hydra_customer_config_id": "Y2lzY29zcGFyazovL3VzL0VOVEVSUFJJU0UvYmIyMzA1MDEtMTUzMS00MzNiLTllM2QtODExY2FlYTExYmVk" } } 

The provisioning tool can run on any machine usually the (partner's administrator laptop) and uses the Webex Public APIs. It reads the transform tool output JSON (customer.json) file as an input and provisioning the customers, locations, numbers, users, services, and devices in the Webex Wholesale RTM solution.

Prerequisites

Configure the following prerequisites inside the provisioning tool directory:

1. Install Java 8, 11, or 17 on the computer. Java is available from many sources, including:
   • https://learn.microsoft.com/en-us/java/openjdk/download
   • https://aws.amazon.com/corretto/
   • https://download.oracle.com/java/17/latest/jdk-17_macos-x64_bin.dmg
2. After downloading and extracting the Migration tools binaries, set the JAVA_HOME environment variable in the provisioning_tool.sh for MAC and provisioning_tool.bat for Windows.
3. The partner.cfg file:
   • Set the WHOLESALE_PROVISIONING_ID and REFRESH_TOKEN (Token copied from the Token Generator Tool). The partner administrators must contact their account team to get the PROVISIONING_ID:

     WHOLESALE_PROVISIONING_ID = Y2U4YWQxYmQtMWZlNy00NjRiLWExMmItMGJkODMzN2U5NmU0 REFRESH_TOKEN=MzUwYjljODEtYmQ4MS00NGVhLTgwNGUtZjQ1NTEyZTViNzJkOTdj 

   • Set ALLOW_ADMIN_INVITE_EMAILS to false, if partner don’t want to send a welcome email to the users. The default value is true.

4. Use the WEBEX4BWKS_EMAIL_SUBJECT property for Webex for BroadWorks migrations to send the change password request email subject for Webex for BroadWorks subscribers.
5. Use the WEBEX4BWKS_EMAIL_BODY property for Webex for BroadWorks migrations to send the change password request email body for Webex for BroadWorks subscribers.

For BroadCloud migrations same region:

1. The tool skips the numbers, devices, and Shared Call Appearances provisioning.
2. The tool creates users and virtual users with extension and temporary extension.

For BroadCloud migrations another region:

1. The tool will provision numbers, devices, and Shared Call Appearances.
2. The tool creates users and virtual users with actual phone numbers and extension.
   All Europe BroadCloud migrations are to another region.

Instructions to run

Use the following steps to run the tool in Windows and macOS:

Windows

Execute the following steps to run the tool on Windows OS:

To provision single customer: provision.bat -input=<Transform-Tool-Output-Customer-JSON-File-Path> To provision multiple customers: provision.bat -input=<Transform-Tool-Timestamp-Output-Directory-Path> 

macOS

Execute the following steps to run the tool on macOS:

To provision single customer: ./transform.sh -input=<Transform-Tool-Output-Customer-JSON-File-Path> To provision multiple customers: ./transform.sh -input=<Transform-Tool-Timestamp-Output-Directory-Path> 

Prerequisites for Webex for BroadWorks Migration

Partner Administrators must update their BroadWorks onboarding template for Webex for BroadWorks coexistence features. Refer to the following image:

Once the Webex for BroadWorks Onboarding template is updated to support migration, request the Cisco Account Team to enable the "wholesale-partner-blending-enabled" feature toggle at the partner level. This will allow Wholesale packages to be added to existing Webex for BroadWorks customer organizations during provisioning.

Run the provisioning tool with an additional argument.

Preparation phase: is the default phase where Administrators can provision the BroadWorks users as a Wholesale subscriber and continue with the Webex for BroadWorks users.

Maintenance phase: is the second phase where Administrators can assign the Wholesale license to the existing Webex for BroadWorks users. You must run the provisioning tool with an argument maintenance.

Post Migration phase: Is the final phase when Administrators can convert the BroadWorks to Wholesale completely. You must run the provisioning tool with an argument postmigration.

Terminal logs

Following are the logs in the terminal on successful provisioning:

Tool Name: Provisioning Tool Version: 1.15.0 ********** Started Processing File : input/customer.json **************** Provisioning Customer Waiting for customer external_id_engg_grp1 to complete provisioning... Waiting for customer external_id_engg_grp1 to complete provisioning...   Customer external_id_engg_grp1 status : provisioned Provisioning Numbers Provisioning Users Provisioning User Features Provisioning Greetings Provisioning Schedules Provisioning Devices Provisioning Shared Call Appearances Provisioning Auto Attendants Provisioning Call Queues Provisioning Hunt Groups Provisioning Group Pagings Provisioning Call Parks Provisioning Call Pickups Provisioning Voice Portal ********** Completed File : input/customer.json **************** 

A table will be printed with the number of locations created for each run:

Output

Provisioning tool generates success and error reports inside the output/<external_id>/*.success/error files. Review output success and error logs to verify successful provisioning.

Partner administrators can verify the customer provisioning in the Partner Hub and Control Hub portal. Refer to the following illustrations from the Partner Hub and Control Hub portal:

Figure 8: Partner Hub

Figure 9: Control Hub

Figure 10: Devices

Figure 11: Calling

For BroadCloud

For BroadCloud partners, use the Service Provider portal to submit a migration request for numbers, devices, and SCA migrations.

Within the Service Provider portal, a migration request can include up to 50 customers. A maximum of 10 requests can be submitted within a day.

The figures below show the Service Provider portal.

Figure 12: Service Provider portal

Figure 13: Service Provider portal

For Cisco BroadWorks and Webex for BroadWorks

For Cisco BroadWorks and Webex for BroadWorks migrations, the tool runs on the secondary Cisco BroadWorks Application Server within the partner network and connects to the AS through OCI-P. It uses the Transform Tool output JSON (customer.json) file as input and run the OCI-P commands to migrate devices and soft clients.

On successful operation, the device move tool will:

1. Deregister devices from the Cisco BroadWorks and register them in Wholesale.
2. Users using the UC-One client will redirect to the Webex App on first-time sign-in.
3. Deactivate the Phone Numbers from Cisco BroadWorks or remove the phone numbers from BroadCloud.
4. Activate numbers in Wholesale.
5. Create Shared Call Appearances in Wholesale for BroadCloud migrations. [This step is applicable only for BroadCloud migrations].

SCP and SSH

1. SCP the device move tool to the secondary Cisco BroadWorks Application Server.
2. SSH to the secondary Cisco BroadWorks Application Server to configure the prerequisites and run the device move tool.

Prerequisites

1. Set the REFRESH_TOKEN (Token copied from the Token Generator Tool) in the conf/partner.cfg file:

   REFRESH_TOKEN=MzUwYjljODEtYmQ4MS00NGVhLTgwNGUtZjQ1NTEyZTViNzJkOTdj

2. Ensure the secondary Cisco BroadWorks Application Server User ID, Password, and Host Name are correct in the conf/deviceMoveTool.conf file:

   BROADWORKS_USER_ID = admin BROADWORKS_PASSWORD = admin BROADWORKS_HOST_NAME = localhost 

3. To resend activation emails, you need to set RESEND_INVITATION_EMAILS=true in the conf/partner.cfg file.

   If administrators wish to send invitation emails to their users during migration, they should uncomment the "RESEND_INVITATION_EMAILS=true" property in the conf/partner.cfg file. Otherwise, the property should remain unchanged.

4. Verify the JDK/JRE environment path is correct in devicemove.sh

   JAVA_HOME=/usr/local/java/java_base

5. Administrators can use the locations.csv file from the input directory to migrate the specific groups instead of all groups under an enterprise.

Polycom phones

To move Polycom phones from Cisco BroadWorks to Wholesale Calling, a partner administrator must create a new Identity/Device Profile Type File at the System level in Cisco BroadWorks each Polycom device template. Refer to figure 14 and upload the custom file device-move-tool/conf/deviceProfile/{region}/polycom_vvx.cfg. After uploading the new device file, ensure the newly created file exists at the Group level. Also ensure that file migration_%BWMAC ADDRESS%.cfg doesn’t conflict with any existing file in your system).

It’s used internally by the device move tool.

The migration process for Polycom phones:

1. The device move tool replaces the file %BWMACADDRESS%.cfg at the device level with polycom_vvx2.cfg. This file refers to migration_%BWMACADDRESS%.cfg.
2. Rebuild the device profiles at the group level or device level.
   Acting at the group level or device level depends on the configuration of parameter deviceLevelRebuild in the file device-move-tool/conf/partner.cfg.
3. The device move tool asks the Cisco BroadWorks Application Server to reboot phones at the group level or device level.
4. After the reboot request, Polycom phones download and process% BWMACADDRESS%.cfg, which asks the Polycom phones to download and process migration_%BWMACADDRESS%.cfg, which sets the device.prov.serverName to https://plcm.sipflash.com.
   https://plcm.sipflash.com for the US region, other regions have different URLs.
5. The Polycom phone downloads %BWMACADDRESS%.cfg from https://plcm.sipflash.com and will be managed by the Webex Calling DMS.

Figure 14: Identity/device profile type file add

Instructions to run

There are two methods to invoke the DMT, first one is to invoke through a single customer at a time and the other is to run through multiple customers simultaneously.

The device move tool is run from the secondary Cisco BroadWorks Application Server inside the device move tool directory:

For device move single customer: ./devicemove.sh -input=<Transform-Tool-Output-Customer-JSON-File-Path> ./devicemove.sh -input=/tmp/customername.json For device move multiple customers: ./devicemove.sh -input=<Transform-Tool-Timestamp-Output-Directory-Path> ls -l /tmp/directoryofcustomers/ customer1.json customer2.json customer3.json Additionally, the device move tool supports migrate single/specific phone(s) from 1.35.0 release. Use the command below: ./devicemove.sh -integration -input= <Transform-Tool-Output-Customer-JSON-File-Path> -macaddress=4CBC4883A6F8,48256741CBE9 

Terminal logs

Following are the logs in the terminal on successful running the device move tool for device migration:

Tool Name: Device Move Tool Version: 1.15.0 Device Tool Started... Valid Devices for migration : ------------------------------------------------------------------------------------------------------------------- | Device Type | Mac | Version | Email | ------------------------------------------------------------------------------------------------------------------- | DMS Cisco 7861 | CC98914EAAD7 | Cisco-CP-7861-3PCC/11.3.7_cc98914eaad7_ | amareswaranvel+benjaminjack@gmail.com | | DMS Cisco 6821 | 5486BCAE7E45 | Cisco-CP-6821-3PCC/11.3.7_5486bcae7e45_ | amareswaranvel+lucasoliver@gmail.com | | DMS Cisco 8811 | F87B204E4066 | Cisco-CP-8811-3PCC/11.3.7_f87b204e4066_ | amareswaranvel+owenalex@gmail.com | ------------------------------------------------------------------------------------------------------------------- Do you want to migrate all these devices? ([Y]es or [N]o) yes Uploading Device Profiles for DMS Cisco MPP LC Rebuild Device Process Started Rebuild Device Process Completed Successfully Reboot Process Started Reboot Process Completed Successfully Modifying profiles for Business Communicator under group collabmigrationtestGRP_engg Activate webex phone numbers process started for customer org Id : 85ea1d6f-ff9e-41a1-843f-7362aaf12b4c Activate webex phone numbers process completed for customer org id : 85ea1d6f-ff9e-41a1-843f-7362aaf12b4c Deactivate broadworks phone numbers process started for groupId : collabmigrationtestGRP_engg Deactivate broadworks phone numbers process completed for groupId : collabmigrationtestGRP_engg Device Migration Completed 

Output

After the device migration, devices have come online and ready to make/receive calls. Refer to figure 15 to see an example of the device status:

Figure 15: Device status

After the device migration, numbers have come active. Refer to figure 16 to see an example of what numbers are active:

Figure 16: Numbers active

The revert operation must be executed for one enterprise at a time.

For BroadCloud Carrier

The revert process for BroadCloud partners is as follows:

1. Open a ticket with Cisco TAC to request a device revert.
2. Run the device move tool on revert mode:
   • Phone numbers will be unassigned from Webex Calling, leaving users and services with extensions only.
   • Email addresses in Webex Calling will be reverted to temporary email addresses.
   • Phones will be deleted from Webex Calling.
   • Phone numbers, email addresses used as alternatedIds, and phones will be recreated in BroadCloud.
   • Phones will be rebooted.
3. Partner administrators must move PSTN phone numbers back to BroadCloud Carrier.

For Cisco BroadWorks and Webex for BroadWorks

The revert process for Cisco BroadWorks and Webex for BroadWorks is as follows:

1. Open a ticket with Cisco TAC to request a device revert.
2. Run the device move tool on revert mode on the secondary BroadWorks Application Server to revert the device migrations. This will set the DMS URL back to the service provider DMS URL for device profiles in Cisco BroadWorks and re-activate phone numbers.
3. The Webex Calling Team sets the DMS URL back to the service provider DMS URL in device profiles in Webex Calling.
4. Partner administrators must deactivate or delete the phone numbers in the Webex Calling through the Control Hub portal.
5. Partner administrators must move PSTN phone numbers back to Cisco BroadWorks.

Instructions to run device move tool in revert mode

Follow the steps below to run the device move tool in revert mode:

Run the command below in the secondary Cisco BroadWorks Application Server inside the device move tool directory:

Revert profiles

./devicemove.sh -input= <Transform-Tool-Output-Customer-JSON-File-Path> -revertProfiles

Revert numbers

./devicemove.sh -input= <Transform-Tool-Output-Customer-JSON-File-Path> -revertNumbers

Terminal logs

We will get the following logs in the terminal on successful running the device move tool for revert operation:

Revert profiles

Tool Name: Device Move Tool Version: 1.15.0 Device Tool Started for Revert Process... Devices that can be moved back from Webex Calling to BroadWorks: - ------------------------------------------------------------------------------------------------------------------- | Device Type | Mac | Version | Email | ------------------------------------------------------------------------------------------------------------------- | DMS Cisco 7861 | CC98914EAAD7 | Cisco-CP-7861-3PCC/11.3.7_cc98914eaad7_ | amareswaranvel+benjaminjack@gmail.com | | DMS Cisco 6821 | 5486BCAE7E45 | Cisco-CP-6821-3PCC/11.3.7_5486bcae7e45_ | amareswaranvel+lucasoliver@gmail.com | | DMS Cisco 8811 | F87B204E4066 | Cisco-CP-8811-3PCC/11.3.7_f87b204e4066_ | amareswaranvel+owenalex@gmail.com | ------------------------------------------------------------------------------------------------------------------- Do you want to move back these devices from Webex Calling to BroadWorks? (Yes, Y, No, N):  yes Uploading Device Profiles for DMS Cisco MPP LC Rebuild Device Process Started Rebuild Device Process Completed Successfully Reboot Process Started Reboot Process Completed Successfully Device Migration Completed for Deprovision Process 

Revert numbers

Tool Name: Device Move Tool Version: 1.15.0 Do you want to continue reverting numbers to Broadworks ?  ([Y]es or [N]o):  Y [+15205551101, +15205551102, +15205551103, +15205551104, +15205551105, +15205551106, +15205551107, +15205551108, +15205551109, +15205551110] Starting revert Activate broadworks phone numbers process started for groupId : collabmigrationtestGRP_engg Activate broadworks phone numbers process completed for groupId : collabmigrationtestGRP_engg Device Migration Revert process Completed Successfully