- Početak
- /
- Članak
Alatke za migraciju na rešenja veleprodajnog RTM-a
Pokrenite migraciju sa minimalnom preliminarnom konfiguracijom. Komande za lako pokretanje. Administratori mogu da pregledaju svoje podatke nakon dodele privilegija i da upućuju i primaju pozive odmah nakon migracije. Podržava automatsku nadogradnju na aplikaciju Webex za UC-One klijente.
Pregled
Svrha ovog dokumenta je da pruži detaljna uputstva o upotrebi alatki za migraciju sa Cisco BroadWorks, Webex za BroadWorks i BroadCloud za veleprodaju i Webex Calling. Ovaj dokument pokriva skup alatki za migraciju dizajniranih da pomognu migraciju postojećih Cisco BroadWorks, Webex za BroadWorks i BroadCloud kupaca u rešenje Route-to-Market za veleprodaju.
Alatke za migraciju imaju za cilj da omoguće potpuni prelazak sa BroadWorks na usluge veleprodaje. One nisu dizajnirane za dugoročnu koegzistenciju obe usluge unutar iste organizacije kupca.
Uticaj migracije
Uticaj posle migracije su sledeći:
Administratori
Nakon migracije, administratori moraju da:
- Počnite da koristite Partner Hub i Control Hub za konfigurisanje funkcija, a ne CommPilot.
- Ponovo konfigurišite sve funkcije koje nisu deo migracije.
Morate ručno da migrirate funkcije koje se ne migriraju automatski kada se završe alatke za migraciju.
Korisnici
Podržane funkcije bi trebalo da funkcionišu nakon migracije na isti način kao i pre migracije. Migracija ne podržava funkcije Webex Calling koje migracija ne podržava:
- Korisnici će izgubiti istoriju poziva i istoriju poruka.
- Korisnici će izgubiti sva podešavanja lične linije ključa i prilagođavanja i moraju ponovo da konfigurišu ova podešavanja nakon migracije. Primeri uključuju brzo biranje.
- Korisnici moraju da resetuju svoje pristupne kodove i lozinke pri prvom prijavljivanju.
- Korisnici koji koriste UC-One klijent moraju pri prvom prijavljivanju da bi se nadogradili u aplikaciju Webex.
Arhitektura alatki za migraciju
Arhitektura alatki za migraciju se sastoji od četiri različita alata:
- Alatka za ekstrakciju– Ekstrahuje preduzeća, grupe, brojeve, korisnike, usluge, telefone i softverske klijente iz usluge Cisco BroadWorks. BroadCloud partneri moraju da podnesu zahtev za ekstrakt na portalu pružaoca usluga.
- Alatka za transformisanje– Transformiše informacije koje je izdvojio alatka za ekstrakciju u JSON datoteku koja se može uređivati.
- Alatka za dodelu privilegija – Koristi JSON izlaznu datoteku iz alatke za transformisanje za obezbeđivanje kupaca, lokacija, brojeva, korisnika, usluga i telefona koristeći Webex javne API-je.
- Alatka za premeštanje uređaja – Koristi izlaznu datoteku alata za transformisanje JSON, alatku za transformisanje da bi ponovo izradili profile i ponovo pokrenuli telefone, aktivirali brojeve u RTM rešenju za veleprodaju i deaktivirali brojeve telefona u Cisco BroadWorks-u.
- Ova alatka podržava vraćanje profila telefona i softverskog klijenta i aktivaciju brojeva u Cisco BroadWorks.
- BroadCloud partneri moraju da podnesu zahtev za migraciju na portalu pružaoca usluga.
Sledeća ilustracija prikazuje kako četiri alatke rade sekvencijalno tako što komuniciraju sa Cisco BroadWorks-om, javnim API-jima i otpremanjem metrika na Webex usluge za buduću analitiku nakon što administrator pokrene zadatke migracije.

Slika 1: Alatke za migraciju
Zahtevi
Pre pokretanja alatki za migraciju, partner mora da ispunjava sledeće uslove:
- Nalog partnera i administratora partnera moraju da se priključe u rešenju za veleprodaju RTM. Tokom faze pre prodaje, nije potrebno da partneri budu priključeni u RTM rešenje za veleprodaju za pokretanje alata za ekstrakt.
- Partner mora da prođe kroz kontrolnu listu za pre migracije da bi bio siguran da su ispunjeni svi zahtevi.
- Akreditivi administratora sistema Cisco BroadWorks su potrebni za pokretanje ekstrakta i alatki za premeštanje uređaja. Ovo ne važi za BroadCloud partnere.
- Alatke za ekstrakciju i premeštanje uređaja moraju biti pokrenute sa sekundarnog Cisco BroadWorks servera aplikacije tokom perioda održavanja da bi se smanjio rizik. BroadCloud partneri će pokrenuti alatku za premeštanje uređaja sa portala pružaoca usluga.
- Pregledajte listu podržanih Webex Calling uređaja.
- Pregledajte listu nepodržanih Webex Calling uređaja.
- Partneri moraju da zatraže od tima za naloge u kompaniji Cisco da bi dobili podržanu verziju firmvera za telefone i uređaje.
- UC-One klijent mora da se nadogradi na sledeće verzije:
- Kupci usluge Desktop Communicator moraju biti verzija 22.9.12 ili novija
- Klijenti usluge Mobile Connect moraju biti verzije 3.9.14 ili novija.
- Administratorska mašina mora da ima:
- JDK/JRE 1,8 je potreban za alatku za dodelu privilegija.
- MAC i Linux mašine zahtevaju Python 3.10.5 ili noviju alatku za transformisanje.
- Kupci moraju da imaju važeću adresu za naplatu, a krajnji korisnici moraju da imaju poslovnu e-adresu konfigurisanu u usluzi Cisco BroadWorks. Ako vrednosti nisu podešene, administratori partnera moraju da se obrate svojim kupcima da bi ih dobili. Ovi detalji moraju da se dodaju u CSV datoteke (vrednosti odvojene zarezima) pre nego što pokrenete alatku za transformisanje. Primer CSV datoteke obezbeđene su sa alatkom za transformisanje.
Plan migracije
Plan migracije ima 3 faze:
- Priprema
- Preuzmite kopiju korisničkih podataka pomoću alatke za Extract
- Generišite token pomoću alatke za generatora tokena
- Koristite alatku za transformisanje da biste formatirali korisničke podatke
- Dodela privilegija
- Dobijte najnovije korisničke podatke pomoću alatke za Extract
- Koristite alatku za transformisanje da biste formatirali korisničke podatke
- Dodeljivanje privilegija korisnicima alatki za dodelu privilegija
- Migracija
- Migrirajte uređaje pomoću alatke za premeštanje uređaja
- Migracije bez uređaja [ Aktiviranje brojeva telefona putem portala Control Hub ]
Ako administratori partnera nemaju uređaje za premeštanje iz aplikacije Cisco BroadWorks u veleprodaju, onda pokretanje alatke za premeštanje uređaja nije potrebno. Administratori partnera mogu da koriste javnu vezu u nastavku da bi aktivirali brojeve telefona direktno preko portala Control Hub. Za više informacija, pogledajte upravljanje brojevima telefona na platformi Control Hub.
Deaktiviranje brojeva telefona u usluzi Cisco BroadWorks je opcionalno ako administratori partnera aktiviraju svoje brojeve telefona putem portala Control Hub.
Funkcije su automatski migrirane u pozivanje za veleprodaju
Ove korisničke funkcije se automatski migriraju pomoću alatki za migraciju:
- Podešavanja razmene glasovnih poruka i prilagođeni pozdravi (glasovne poruke, personalizovani audio ime i PIN korisnika se ne migriraju)
- Rezervni brojevi
- BroadWorks Anywhere
- Polje za lampicu za zauzeto
- ID pozivaoca (prilagođeno ime i broj telefona)
- Poziv je na čekanju
- Podešavanja prosleđivanja poziva (prosleđivanje poziva uvek/zauzeto/nema odgovora/nije dostupno)
- Presretanje poziva
- Ne uznemiravaj
- Podešavanja faksa
- Udaljena kancelarija
- Izgled deljenog poziva
- Lično simultano zvono (uključujući raspored i selektivne kriterijume)
- Obaveštenje o pozivu (uključujući raspored i selektivne kriterijume)
- Odbijanje anonimnog poziva
- Selektivno odbijanje poziva
- Selektivno prosleđivanje poziva
- Preuzimanje usmerenog prenosa i ubacivanje
- Izuzeće ubacivanja
- Pritisni za razgovor
- Privatnost
- Muzika na čekanju
- Usluga tokom odmora
- Noćna usluga
Alatke za migraciju automatski migriraju ove funkcije grupe:
- Automatski službenik
- Samo jedan nivo
- Prilagođeni pozdravi
- Podešavanja prosleđivanja poziva (uvek, zauzeto, selektivno)
- Rezervni brojevi
- Meni odmora nije dostupan u aplikaciji Webex
- Selektivno odbijanje poziva
- Standardni red za čekanje poziva za Cisco BroadWorks Call Center i BroadCloud:
- Osnovna konfiguracija
- Prilagođeni pozdravi
- Agenti i supervizori
- Podešavanja prosleđivanja poziva (uvek, zauzeto, selektivno)
- Rezervni brojevi
- Muzika na čekanju
- Nametnuto prosleđivanje
- Poništena poruka za udobnost
- Parkiranje poziva
- Preuzimanje poziva
- Ciljana grupa
- Podešavanja prosleđivanja poziva (uvek, zauzeto, selektivno, nije dostupno)
- Rezervni brojevi
- Kôd lokacije (jedan po lokaciji ili grupi)
- Pejdžing grupa
- Rasporedi (samo na nivou grupe, rasporedi preduzeća nisu migrirani)
- Glasovni portal
- Muzika na čekanju
- Uobičajena lista telefona
Podržani uređaji
Podržani telefoni će se automatski kreirati i dodeliti korisnicima u usluzi Webex Calling pomoću alatke za dodelu privilegija. Telefoni sa „Da“ u koloni „Podržano u alatki za premeštanje uređaja“ takođe će se automatski premestiti iz aplikacija Cisco BroadWorks ili BroadCloud u Webex Calling kada se alatka za premeštanje uređaja pokrene. Telefonima koji su označeni „Ne“ u toj koloni potrebna je ručna intervencija da bi se promenila DMS URL adresa u Cisco BroadWorks šablonu uređaja ili u samom telefonu.
Poslednja kolona obezbeđuje mapiranje modela telefona u kolonu „Tip uređaja” alatke za transformisanje datoteke/unos/newphones.csv. (Pogledajte odeljak Alatka za transformisanje ovog članka da biste saznali više o newphones.csv).
Model telefona |
Podržano u alatki za premeštanje uređaja |
Tip uređaja u newphones.csv |
---|---|---|
Cisco MPP 6821 |
Da |
Cisco DMS 6821 |
Cisco MPP 6841 |
Da |
Cisco DMS 6841 |
Cisco MPP 6851 |
Da |
Cisco DMS 6851 |
Cisco MPP 6861 |
Da |
Cisco DMS 6861 |
Cisco MPP 6871 |
Da |
Cisco DMS 6871 |
Cisco MPP 7811 |
Da |
Cisco DMS 7811 |
Cisco MPP 7821 |
Da |
Cisco DMS 7821 |
Cisco MPP 7832 |
Da |
Cisco DMS 7832 |
Cisco MPP 7841 |
Da |
Cisco DMS 7841 |
Cisco MPP 7861 |
Da |
Cisco DMS 7861 |
Cisco MPP 8811 |
Da |
Cisco DMS 8811 |
Cisco MPP 8832 |
Da |
Cisco DMS 8832 |
Cisco MPP 8841 |
Da |
Cisco DMS 8841 |
Cisco MPP 8845 |
Da |
Cisco DMS 8845 |
Cisco MPP 8851 |
Da |
Cisco DMS 8851 |
Cisco MPP 8861 |
Da |
Cisco DMS 8861 |
Cisco MPP 8865 |
Da |
Cisco DMS 8865 |
Cisco MPP 8875 |
Da |
Cisco DMS 8875 |
Cisco ATA191 |
Da |
Cisco DMS 191 |
Cisco ATA192 |
Da |
Cisco DMS 192 |
Cisco DBS 110 |
Da |
Cisco DMS DBS110 |
Поликом VVX101 |
Da |
Полицома VVX101 |
Поликом VVX150 |
Da |
Полицома VVX150 |
Поликом VVX201 |
Da |
Полицома VVX201 |
Поликом VVX250 |
Da |
Полицома VVX250 |
Поликом VVX301 |
Da |
Полицома VVX301 |
Поликом VVX311 |
Da |
Полицома VVX311 |
Поликом VVX350 |
Da |
Полицома VVX350 |
Поликом VVX401 |
Da |
Полицома VVX401 |
Поликом VVX411 |
Da |
Полицома VVX411 |
Поликом VVX450 |
Da |
Полицома VVX450 |
Поликом VVX501 |
Da |
Полицома VVX501 |
Поликом VVX601 |
Da |
Полицома VVX601 |
Полицома 8300 |
Da |
Полицома Trio8300 |
Полицома 8500 |
Da |
Полицома Trio8500 |
Полицома 8800 |
Da |
Полицома Trio8800 |
Polycom zvučna stanica 5000 |
Da |
Полицома SSIP5000 |
Polycom zvučna stanica 6000 |
Da |
Полицома SSIP6000 |
Јеalинк T33G |
Da |
Јеalink je T33G |
Јеalинк T41S |
Da |
Јеalink je T41S |
Јеalинк T42S |
Da |
Јеalink je T42S |
Јеalинк T43U |
Da |
Јеalink je T43U |
Јеalинк T46U |
Da |
Јеalink je T46U |
Јеalинк T46S |
Da |
Јеalink je T46S |
Јеalинк T48S |
Da |
Јеalink je T48S |
Јеalинк T48U |
Da |
Јеalink je T48U |
Јеalинк T53W |
Da |
Јеalink je T53W |
Јеalинк T54W |
Da |
Јеalink je T54W |
Јеalинк T57W |
Da |
Јеalink je T57W |
Јеalинк T58V |
Da |
Јеalink je T58V |
Јеalинк CP920 |
Da |
Јеalink je CP920 |
Јеalинк CP960 |
Da |
Јеalink je CP960 |
Јеalинк W52B |
Da |
Јеalink je W52P |
Јеalинк W56B |
Da |
Јеalink je W56P |
Јеalинк W60B |
Da |
Јеalink je W60P |
Јеalинк W70B |
Da |
Јеalink je W70P |
Јеalинк CP925 |
Da |
Јеalink je CP925 |
Јеalинк CP965 |
Da |
Јеalink je CP965 |
Audio kodovi MP204R |
Da |
DMS audio kodovi MP204R |
Audio kodovi MP202R |
Da |
DMS audio kodovi MP202R |
Audio kodovi MP204 |
Da |
DMS audio kodovi MP204 |
Audio kodovi MP202 |
Da |
DMS audio kodovi MP202 |
Uređaji koji nisu podržani
Ako kupac koristi nepodržane uređaje od strane rešenja veleprodaje RTM, ti uređaji ne ispunjavaju uslove za migraciju. U ovom slučaju, imate sledeće opcije:
- Dodelite privilegije za nove telefone na Cisco BroadWorks pre migracije.
- Napustite stare telefone u usluzi Cisco BroadWorks i korisnici moraju da instaliraju aplikaciju Webex da bi upućivali i primali pozive.
Paketi pozivanja za veleprodaju
Alatke za migraciju imaju skup podrazumevanih vrednosti za izbor paketa pozivanja za veleprodaju za pretplatnike. Ako kasnije želite drugi paket, administrator partnera može da ih promeni na portalu Control Hub.
Konfiguracija Cisco BroadWorks paketa migracije
Svi pretplatnici koji migriraju iz Cisco BroadWorks-a podrazumevano će biti na Webex Calling paket. Ako je Webex glasovni paket potreban za pretplatnike koji nemaju dodeljene funkcije „Pozivi na čekanju“ ili „Govorna pošta“, to se može omogućiti u partner.cfg datoteci alatke za transformisanje tako što ćete poništiti komentar na liniju „KORISTI_WEBEX_VOICE_“.
Mapiranje paketa Webex za BroadWorks migracije
Migracija iz Webex-a za Broadworks paketa zasniva se na tipu Broadworks paketa. Konfigurišite podrazumevano mapiranje u konfiguracionoj datoteci alatke za transformisanje na adresi conf/w4b_package_to_wholesale_package.csv.
Webex za BroadWorks paket |
Paket pozivanja za veleprodaju |
---|---|
Softfon |
Webex Voice |
Osnovno |
Webex Calling |
Standardni |
Webex Suite |
Premium |
Webex Suite |
Mapiranje paketa migracije BroadCloud
Migracije iz BroadCloud Carrier paketa za mapiranje po tipu stanice. Podrazumevano mapiranje može da se konfiguriše u konf/rialto_station_type_to_wholesale_package.csv datoteci za konfiguraciju alatke za transformisanje.
Tip stanice BroadCloud |
Paket pozivanja za veleprodaju |
---|---|
Osnovno |
Webex Voice |
Soba za konferencije |
Webex Voice |
Razmena poruka |
Webex Voice |
Standardni |
Webex Voice |
Izvršni rukovodilac |
Webex Suite |
Svi drugi tipovi stanice |
Webex Voice |
Transformisanje BroadWorks ili BroadCloud korisničkog naloga u radni prostor za Webex Calling
Webex radni prostor je telefon koji se deli među mnogim ljudima, na primer: Na primer: telefona u konferencijskoj sobi, skladištu ili čekaonici. Takvi telefoni u usluzi Webex Calling mogu da se konfigurišu kao Webex radni prostori, a ne kao Webex korisnici. Dostupna je opcija za automatsko transformisanje korisničkih naloga iz Cisco BroadWorks ili BroadCloud operatera u radne prostore tokom procesa migracije.
Korake:
- U datoteci transform_tool/unos/users.csvdodelite paket „common_area“ korisnicima koji će se transformisati u radni prostor.
- Primer: bwkorisnik@domain,,,,common_area
- (Samo BroadCloud) Da biste konvertovali sve korisničke naloge određenog tipa stanice u radne prostore, dodajte unos za transformisanje alatke/conf/rialto_station_type_to_wholesale_package.csv i podesili paket za veleprodaju u „common_area_calling“.
- Primer: conference_room_v2,common_area_calling
- Pokrenite alatku za transformisanje.
- Pokrenite alatku za dodelu privilegija.
- Otvorite Control Hub novokreirane organizacije kupca i podesite SIP domen (pogledajte sliku 2, Konfigurisanje SIP domena na platformi Control Hub).
- Ponovo pokrenite alatku za dodelu privilegija. Na taj način će se kreirati radni prostori i dodeliti telefone njemu.
Ograničenja:
Konfiguracija korisničkih funkcija (na primer, prosleđivanje poziva, ne uznemiravaj) ne migrira se automatski u radni prostor.

Slika 2: Konfigurisanje SIP domena na portalu Control Hub
Alatka za generatora tokena
Administratori partnera pokreću ovu alatku za alatku generatora tokena najmanje jednom pre nego što počnu da pokreću alatke za migraciju. Pokretanje ove alatke je jednokratna aktivnost nakon što nalog partnera bude ulazno migriran u rešenje veleprodaje RTM. Ova alatka omogućava administratorima partnera da se prijave putem veb-pregledača kako bi dobili jedinstveni TOKEN koji je potreban za ažuriranje na datoteke konfiguracije partnera za alatke za migraciju.
Preduslovi
Instalirajte Java 8, 11, 17 ili 21 na računar. Java je dostupna iz mnogo izvora, uključujući:
- https://learn.microsoft.com/en-us/java/openjdk/download
- https://aws.amazon.com/corretto/
- https://www.oracle.com/java/technologies/downloads/#java21
Nakon preuzimanja, izdvojte binare alatke za migraciju.
Ovaj korak je opcionalan
Uputstva za pokretanje
Pokrenite sledeću komandu u terminalu unutar direktorijuma generatora tokena:
-
Sledeći portovi moraju da budu dostupni za pokretanje alatke za generisanje tokena. Portovi: 8080, 50009, 50010, 50011, 50012 i 50013
-
Barem jedan od ovih navedenih portova mora da bude otvoren za vezu na računaru korisnika.
Windows:
token_generator.bat
MacOS:
./token_generator.sh
Одлика:
Tool Name: Token Generator Tool
Version: 1.13.0
Load the URL in your web browser: http://localhost:8080
Otvorite URL u veb-pregledaču na terminalu, prijavite se pomoću akreditiva administratora partnera da biste dobili TOKEN i kopirali ga za dalju upotrebu.
Ilustracije korisničkog interfejsa su date u nastavku za referencu:
Slika 3: Prijavite se pomoću usluge Cisco Webex
Slika 4: Prozor akreditiva
Slika 5: Generisanje tokena
Zadaci podešavanja BroadWorks
Konfigurišite sledeće korake pre nego što pokrenete ekstrakt i premeštanje uređaja na sekundarnom BroadWorks serveru.
Omogući OCI-P mogućnost povezivanja
Alatka za premeštanje uređaja komunicira sa BroadWorks-om preko OCI-P komandi da bi se omogućila OCI-P veza, koristite korake u nastavku:
Korak 1: Koristite CLI da biste konfigurisali opšta podešavanja.
Pokrenite sledeću komandu u CLI da biste promenili u GeneralSettings direktorijum:
AS_CLI> cd /Applications/OpenClientServer/GeneralSettings.
Pokrenite sledeću komandu u CLI da biste dobili trenutne opšte postavke:
AS_CLI/Applications/OpenClientServer/GeneralSettings> get
clientPort = 2208
clientPortEnabled = true
secureClientPort = 2209
secureClientPortEnabled = true
systemDomain = <>
Ako se vaša podešavanja ne podudaraju sa gorenavedenom, koristite komandu Set da biste ponovo konfigurisali podešavanja.
Korak 2: Koristite CLI za konfigurisanje OCI proxy servera.
Promenite direktorijum u OCI proxy server:
AS_CLI> cd /Applications/OpenClientServer/OCIProxy
Pokrenite sledeću CLI da biste dobili trenutna podešavanja. Trebalo bi da vidite sledeće:
AS_CLI/Applications/OpenClientServer/OCIProxy> get
enabled = true
enabledLoginLevelScreening = false
enableResponseCaching = false
responseCacheDurationHours = 24
responseCacheRenewPeriodMins = 30
messageQueueCapacity = 50
messageQueueTimeoutSeconds = 1800
Ako se vaša podešavanja ne podudaraju sa gorenavedenom, koristite komandu Set da biste ponovo konfigurisali podešavanja.
Korak 3: Koristite CLI da biste konfigurisali OCI dodeljivanje privilegija.
Promenite u direktorijum za dodelu privilegija:
AS_CLI> cd /System/NetworkAccessLists/OCI/Provisioning
Pokrenite sledeću komandu da biste dobili trenutna podešavanja dodele privilegija za OCI:
AS_CLI/System/NetworkAccessLists/OCI/Provisioning> get
Address Description
========================
127.0.0.1 local as
Korak 4: Pokrenite komandu u nastavku na CLI da biste proverili da li je konfiguracija tačna.
AS_CLI/Maintenance/ManagedObjects> get broadworks and check
that your output looks OK.
See below for sample output:
AS_CLI/Maintenance/ManagedObjects> get broadworks
BroadWorks Managed Objects
==========================
* Server:
Identity..............: AS
Version...............: Rel_21.sp1_1.551
Administrative State..: Unlocked
* Applications:
Name Version Deployed Administrative State Effective State
=========================================================================================
ExecutionAndProvisioning 21.sp1_1.551 true Unlocked Unlocked
FlashPolicy 21.sp1_1.551 false Unlocked Stopped
OpenClientServer 21.sp1_1.551 true Unlocked Unlocked
WebContainer 21.sp1_1.551 true Unlocked Unlocked
4 entries found.
* Hosted Applications:
Name Version Context Path Deployed
==================================================================
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 entries found.
Potvrdi da je otvoren server klijenta primenjen i aktivan
Koristite komande u nastavku da biste primenili i pokrenuli Otvori server klijenta na sekundarnom serveru aplikacije ako nije primenjen ili već nije pokrenut.
Korak 1: Primenite server sa sledećom CLI komandom:
AS_CLI/Maintenance/ManagedObjects> deploy application OpenClientServer
Korak 2: Pokrenite server pomoću ove komande:
AS_CLI/Maintenance/ManagedObjects> start application OpenClientServer
Omogući aktivaciju brojeva
Izvršite sledeće komande u CLI da biste omogućili aktiviranje brojeva:
Korak 1: Pokrenite komandu za aktiviranje broja:
AS_CLI> cd SubscriberMgmt/NumberActivation
Korak 2: Pokrenite komandu omogućenu aktivaciju:
AS_CLI> set dnMode groupAndUserActivationEnabled
Korak 3: U upitu za potvrdu unesite Y.
Alatka za ekstrakciju
Za BroadCloud
Alatka za ekstrakciju je integrisana na BroadCloud portalu za pružaoca usluga. Administrator pružaoca usluga može:
- Prosledite zahteve za ekstrakciju za do 50 kupaca po zahtevu.Zahtev za ekstrakciju ne može da se pošalje istom kupcu više od 10 puta u toku dana.
- Preuzmite datoteku izvezenih podataka, u ZIP formatu, do 28 dana od datuma slanja zahteva.
Na sledećoj slici prikazan je portal za pružaoca usluga.

Slika 6: Portal pružaoca usluga

Slika 7: Portal pružaoca usluga
Zahtev za CSV ekstrakciju
Pokreni zahtev za CSV ekstrakt
-
Preuzmi CSV datoteku kupca
Kliknite na vezu Preuzmi CSV vezu kupca u gornjem desnom uglu odeljka Pokreni CSV zahtev za ekstrakt .
-
Uredi listu kupaca
Administrator može da uredi ovu CSV datoteku tako da uključi samo kupce za koje treba izvršiti ekstrakt.
-
Otpremi i pošalji
Nakon uređivanja, otpremite izmenjenu CSV datoteku.
Kliknite na Prosledi da biste pokrenuli zahtev za ekstrakt za navedene kupce i njihove povezane lokacije.
Pokrenite zahtev za ekstrakciju za kupca pomoću CSV datoteke lokacija
-
Izaberi kupca i preuzmi lokacije
Izaberite kupca u padajućem meniju.
Preuzmite odgovarajuće sa locations.csvopcije Prikaži kupce → Kartica Lokacije → Izvezi lokacije kao CSV.
-
Uređivanje datoteke lokacija
Administrator može da uredi CSV tako da uključi samo lokacije koje žele da ekstrahuju.
-
Otpremi i pošalji
Otpremite uređeno locations.csv i kliknite na dugme Prosledi.
U zahtev za ekstrakt će biti uključene samo navedene lokacije za izabranog kupca.
Pokreni zahtev za ekstrakt za sve kupce
- Kliknite na Prosledi da biste pokrenuli zahtev za ekstrakt za sve kupce i sve njihove lokacije u okviru trenutnog pružaoca usluga.

Za Cisco BroadWorks i Webex za BroadWorks
- Alatka za izvlačenje se pokreće na sekundarnom Cisco BroadWorks serveru aplikacije u okviru partnerske mreže i povezuje se preko OCI-P-a.
- Alatka povlači podatke neobrađenih preduzeća, grupe, brojeva, korisnika, usluga, uređaja i softverskog klijenta sa Cisco BroadWorks ili BroadCloud platforme i izlaže ove podatke u XML datoteke koje obezbeđuju ulazne podatke za alatku za transformaciju.
Sledeći odeljci objašnjavaju kako da instalirate i konfigurišete alatku za ekstrakciju.
Preduslovi
- SCP binari alatke za ekstrakt na sekundarni Cisco BroadWorks server aplikacije.
- SSH na sekundarni Cisco BroadWorks server aplikacije da bi konfigurisao preduslove i pokrenuo alatku za ekstrakciju.
- Konfigurišite pružaoca usluge i ID grupe za izdvajanje iz usluge Cisco BroadWorks u konf/exportTool.yml. Pogledajte sledeći uzorak YAML isečak:
ServiceProviderID-A: - GroupID-A1 - GroupID-A2 - GroupID-A3 ServiceProviderID-B: - ALL
- Uverite se da su sekundarni ID, lozinka i ime organizatora Cisco BroadWorks aplikacije tačni u konf/partner.cfg datoteci:
BROADWORKS_USER_ID = admin BROADWORKS_PASSWORD = admin BROADWORKS_HOST_NAME = localhost REFRESH_TOKEN = Partner administrator’s refresh token copied from the Token Generator tool.
Svojstvo
REFRESH_TOKEN
je obavezno za Webex za BroadWorks migraciju. - Izmenite putanju JDK/JRE okruženja u export.sh datoteci ako se sekundarna putanja Cisco BroadWorks Application Server JDK/JRE okruženja razlikuje od datoteke:
JAVA_HOME=/usr/local/java/java_base
Uputstva za pokretanje
Pokrenite sledeću komandu na sekundarnom Cisco BroadWorks serveru aplikacije iz direktorijuma za ekstract alatke:
./export.sh
Evidencije terminala
Sledeće evidencije su dostupne u terminalu prilikom uspešnog izvoza: Pokretanje BroadSoft alatke za izvoz podataka:
Running BroadSoft Data Export Tool
************************************************
Starting Export Tool v: 1.15.0
Export started for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg
Exporting users for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg
Export users completed for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg
Export completed for SP=collabmigrationtestSP_engg, Group=collabmigrationtestGRP_engg
Export completed
Export Dump Zip Directory : output/20221017223452_ExportTool
Export Dump Zip File name :extracted_data_1666060500618.zip
Zip file with the name extracted_data_1666060500618.zip has been created
ZIP file creation process completed
Exported files converted as ZIP file
**************************************************
Izlaz
Izlazna ZIP datoteka (extracted_data_<timestamp>.zip) je dostupna u istom direktorijumu alata za ekstrakt. Koristite sledeću komandu za pregled i korišćenje ZIP datoteke za unos alatke za transformisanje:
ls –ltr
drwxr-xr-x 2 bwadmin bwadmin 4096 Oct 4 11:53 lib/
-rwxr-xr-x 1 bwadmin bwadmin 956719 Oct 4 11:53 exportTool.jar
-rwxr-xr-x 1 bwadmin bwadmin 2635 Oct 4 11:53 export.sh
drwxr-xr-x 2 bwadmin bwadmin 4096 Oct 5 05:04 conf/
drwxrwxr-x 3 bwadmin bwadmin 4096 Oct 17 22:34 output/
drwxrwxr-x 2 bwadmin bwadmin 4096 Oct 17 22:34 logs/
-rw-rw-r-- 1 bwadmin bwadmin 46341 Oct 17 22:35 extracted_data_1666060500618.zip
Alatka za transformisanje
Ova alatka za transformisanje radi za sve migracije. Alatka za transformisanje radi na bilo kom računaru, uključujući laptop administratora partnera i koristi Webex javne API-je. On očitava izlaznu alatku ZIP (extracted_data_<timestamp>.zip) datoteku kao unos i pretvara sirovi XML u JSON format koji koristi alatka za dodelu privilegija.
Preduslovi
Nakon preuzimanja i preuzimanja binara za alatke za migraciju, konfigurišite sledeće preduslove:
- Podesite token za OSVEŽAVANJE_ (Token kopiran iz alatke za generatora tokena) i IME_GLAVNE__LOKACIJE u konf/partner.cfg datoteci:
REFRESH_TOKEN=MzUwYjljODEtYmQ4MS00NGVhLTgwNGUtZjQ1NTEyZTViNzJkOTdj NAME_OF_MAIN_LOCATION=Main
- Optionally set the PROVISIONING_ID (copied from the template in Partner Hub) in the conf/partner.cfg file:
PROVISIONING_ID=YmE4MjFkZGYtYTlkNy00NDdlLWIwODctYmNkOTM2NjUyYWQ1
To get more complete verification of the customer email address you can optionally set the PROVISIONING_ID. - Configure missing information in the input/customers.csv file (see next section) if missing.
- Add the end user email address in the input/users.csv file.
- If new phones are to be provisioned, add the mac address and email address of the user’s new phone to input/newphones.csv file. This is required only if the partner administrators want to provision new phones in Wholesale calling.
- Convert the BroadWorks Call Centers into the CxEssentials by using the input/cxessentials.csv file.
- Optionally, enable the UPGRADE_ALL_CALL_CENTERS_TO_CX_ESSENTIALS property to convert all Call Centers to CxEssentials.
- Use the input/locations.csv file to support the large enterprise migration that allows administrators to migrate their customer’s locations by location
- Optionally enable usage of MAC addresses from the User-Agent header of the SIP REGISTER message when the MAC address is not available in the Cisco BroadWorks device profile. Uncomment the line USE_MAC_ADDRESS_FROM_SIP_REGISTER=yes in file conf/partner.cfg
- The network server sync feature allows administrators to provision phone numbers, MAC addresses, and users email addresses during the provision in the same region migration. To enable it, set
USE_NS_SYNC=yes
inconf/partner.cfg
.If NS sync is disabled, phone number and device provisioning will be skipped, and users will get temporary email addresses.
- Optionally enable the properties ANALOG_USER_TYPE_ENABLE_CALL_WAITING, ANALOG_USER_TYPE_ENABLE_MUSIC_ON_HOLD, and ANALOG_USER_TYPE_DISABLE_T38 to configure call waiting, music on hold, and disable T38 settings for all analog-type users.
-
If you want to set up generic gateway devices, add the device's MAC address and user ID to the input/genericgateways.csv file. Also, mention whether the user is the PRIMARY owner or a SHARED user (for shared call appearances). This is only needed if partner admins plan to use generic gateway devices in Wholesale Calling.
This feature is not available for BroadCloud to Wholesale migrations.
-
For BroadCloud migrations, to convert all users with the messaging station type to voice_mail_group, update the conf/rialto_station_type_to_wholesale_package.csv file by replacing the Wholesale Package value with voice_mail_group for the row where the Rialto Station Type is messaging.
Optionally, enable the COMMON_VOICE_MAIL_GROUP_PASSCODE property in partner.cfg to configure the default PIN for voice mail groups.
If this property is not specified in partner.cfg, it must be provided per customer in the customers.csv file under the commonVoicemailGroupPassCode column.
-
For migration of common contacts to Webex Calling
It is the enhancement for managing enterprise and site-level common contacts. These contacts can now be migrated either as organization contacts (Org Contacts) or as virtual extensions, based on the configuration settings. Below are the details to guide you through this migration process.
Key configuration:
- COMMON_PHONE_LIST_TO_VIRTUAL_EXTENSION_START_RANGE
A new property, COMMON_PHONE_LIST_TO_VIRTUAL_EXTENSION_START_RANGE, is introduced in the partner.cfg file. This property determines how common contacts are migrated from Rialto to Webex Calling.
- Without COMMON_PHONE_LIST_TO_VIRTUAL_EXTENSION_START_RANGE Configured
Common contacts will be migrated as organization contacts (Org Contacts).
No additional configuration is required.
Contacts remain accessible at the organization level.
- With COMMON_PHONE_LIST_TO_VIRTUAL_EXTENSION_START_RANGE configured
Common contacts will be migrated as Virtual Extensions.
Each contact will be appended with an extension number, and the start range of the extension is defined in the COMMON_PHONE_LIST_TO_VIRTUAL_EXTENSION_START_RANGE property in partner.cfg.
Virtual extensions are supported at both the organization level and location level, depending on the scope of the contact.
- COMMON_PHONE_LIST_TO_VIRTUAL_EXTENSION_START_RANGE
-
Exclusion of selected phone numbers from migration:
To exclude specific phone numbers from the migration process, the following two-step procedure using the transform tool must be followed:
- Initially execute the transform tool for the first time. Upon completion, the tool will generate a file named telephone_numbers_inventory.csv, located within the output/timestamp/ directory. The customer is required to review this file and indicate "Yes" in the "Drop Tn's" column for each phone number that should be excluded from the upcoming migration.
- After updating the telephone_numbers_inventory.csv file with the appropriate exclusion flags, the transform tool is executed a second time. The updated file should be passed as an argument in the following format.
./transform.sh -extract=input/extracted_data_1747640608219.zip -decommissionnumbers={filepath/telephone_numbers_inventory.csv}
Filling-up the input/customers.csv
The file input/customers.csv provides data that maybe missing in Cisco BroadWorks or BroadCloud. This file can be left empty if all mandatory information is already available. You don’t have to fill in all columns, only the missing information is mandatory.
The table below explains the most important columns in input/customers.csv.
Column name |
Pravila |
---|---|
ID |
In Cisco BroadWorks enterprise mode:
In BroadWorks service provider mode, this is the Cisco BroadWorks groupId. In BroadCloud, this is the Rialto customerId. |
spoljni ID |
This is an identifier that matches the partner’s internal identifier for this customer. This column must be unique within a Webex partner org. This column is optional, a unique identifier will be generated automatically by the transform tool. This column is not used for groups within an enterprise. |
customerName |
For the enterprise, this column is used as the Webex customer name field. For a group within an enterprise, this column is used as the location name. Location names must be unique within an enterprise. |
primaryEmail |
This is used as the email address of the Webex customer admin. This column is optional for groups within an enterprise. |
Address columns |
For an enterprise, the address is used as the billing address and the first location address. For a group within an enterprise, the address is used as the location address. |
vremenska zona |
Refer to the time zone section of this article. |
arapski jezik | See Languages Webex supports. |
defaultvoicemailpin |
See Set a voicemail PIN. |
commonVoicemailGroupPassCode | Use this column to specify the default PIN that will be applied to all voice mail groups for the respective customer. After migration, administrators must update the PIN for each voice mail group. During the transform process, the common PIN specified by the administrator is assigned to all voice mail groups. |
Filling-up the input/users.csv
The file input/users.csv provides data that maybe missing in Cisco BroadWorks or BroadCloud. This file can be left empty if all mandatory information is already available. You don’t have to fill in all columns, only the missing information is mandatory.
All these fields are optional.
Column name |
Pravila |
---|---|
userid |
A unique identifier for the user. This can be a BroadWorks or BroadCloud user ID. |
e-pošta | (Optional) The user’s email address. If provided, it will be used for provisioning purposes. |
phonenumber |
(Optional) The user’s phone number to be provisioned. |
package |
(Optional) User package type. Allowed values: voice, calling, suite, common_area, virtual_line, dont_migrate, call_park_ext or voice_mail_group. The dont_migrate value is used when partners want to exclude certain users—along with their devices and phone numbers—from both provisioning and migration. This is supported for both BroadWorks and BroadCloud. When applied, the selected users and their associated resources will not be migrated or provisioned. To use this, administrators should enter dont_migrate in the package column of the users.csv file. |
extension |
(Optional) The phone extension to be assigned to the user. |
ime |
(Optional) The full name of the user. |
ata_settings |
(Optional) Allowed values: t38, analog To enable/disable call waiting, music on hold, and T38 settings T38: This option disables call waiting and music on hold, and enables T38 settings for ATA devices. Analog:
|
do_not_move_phone |
BroadWorks only. Optional flag to prevent device migration to Webex Calling. This option allows partners to provision users along with their calling settings, devices, and phone numbers without migrating the devices to Webex or activating phone numbers in Webex Calling. This setting is only available for BroadWorks, not BroadCloud. To use it, administrators should specify do_not_move_phone in the do_not_move_phone (BroadWorks only) column of the users.csv file. This ensures users are provisioned without activating numbers or moving their phones, so they continue operating via BroadCloud. |
Instructions to run
Run the Transform Tool in any operating system. Use the below steps to run the tool in Windows and macOS:
Windows
Execute the command below to run the Transform Tool in Windows:
transform.bat -extract= -customers= -users= -newphones=
macOS
Execute the following steps to run the transform tool on macOS:
- Create a virtual environment and install dependencies to run the transform tool using Python:
python3 -m venv venv source venv/bin/activate python3 -m pip install requests python3 -m pip install requests-oauthlib python3 -m pip install phonenumbers
- Run the transform tool:
./transform.sh -extract= -customers= -users= -newphones=
Customer/user precheck
The Transform Tool makes API calls to Webex to catch potential provisioning issues. By default, it will validate the customer’s address and primary email. If the PROVISIONING_ID value is specified in the conf/partner.cfg file, it will also validate location information. The precheck results are included in the exception report.
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).
precheckinfo takes extra time to run.
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
Izlaz
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 `webex_for_broadworks_info` JSON property is present for Webex for BroadWorks migrations only. The `broadcloud_info` JSON property is present for BroadCloud migrations only.
Provisioning tool
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.
Preduslovi
Configure the following prerequisites inside the provisioning tool directory:
- Install Java 8, 11, 17, or 21 on the computer. Java is available from many sources, including:
- 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.
- 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.
- 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:
- Use the WEBEX4BWKS_EMAIL_SUBJECT property for Webex for BroadWorks migrations to send the change password request email subject for Webex for BroadWorks subscribers.
- Use the WEBEX4BWKS_EMAIL_BODY property for Webex for BroadWorks migrations to send the change password request email body for Webex for BroadWorks subscribers.
- The network server sync feature allows administrators to provision phone numbers, MAC addresses, and users email addresses during the provision in the same region migration. To enable it, set
USE_NS_SYNC=yes
inconf/partner.cfg
.If NS sync is disabled, phone number and device provisioning will be skipped, and users will get temporary email addresses.
- Use the
CUSTOM_TAGS
property to add tags after customer creation.
For BroadCloud migrations same region:
- The tool skips the numbers, devices, and Shared Call Appearances provisioning.
- The tool creates users and virtual users with extension and temporary extension.
For BroadCloud migrations another region:
- The tool will provision numbers, devices, and Shared Call Appearances.
- 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=
To provision multiple customers:
provision.bat -input=
macOS
Execute the following steps to run the tool on macOS:
To provision single customer:
./transform.sh -input=
To provision multiple customers:
./transform.sh -input=
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:

Izlaz
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:

Slika 8: Partner Hub

Slika 9: Control Hub

Slika 10: Uređaji

Slika 11: Pozivanje
Post-Provisioning Restrictions
Once provisioning is complete for a BroadCloud migration, the following actions will be blocked:
- CAP Portal – Adding users or ported devices.
- SP Portal – Creating ADD orders with devices or numbers.
- RSB API – Creating ADD orders with devices or numbers and creating users. RSB ADD orders made with devices or numbers will be rejected.
Device move tool
For BroadCloud
For BroadCloud partners, use the Service Provider portal to submit a migration request for numbers, devices, and Shared Call Appearances (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 Network Server Sync feature allows administrators to deactivate the broadCloud location and activate the Webex Calling location on setting the USE_NS_SYNC=yes
in the conf/partner.cfg
. After migration, devices and phone numbers are activated in Webex Calling location.
Administrators can enable automated rollback by setting ROLLBACK_TO_BROADCLOUD=true
in the conf/partner.cfg
file, which moves devices back to BroadCloud after migration. It supports both same- and different-region migrations with NS Sync, but only for successful migrations. For failed ones, administrators must raise a Cisco TAC before requesting rollback.
There are two options available for selecting the migration type in the portal:
- Migration – Select this option to initiate a request for migrating numbers, devices, and Shared Call Appearances (SCA).
- Device Status – Select this option to view the current status of a device on BroadCloud and Calling.
The following figures show the Service Provider portal.
Slika 12: Service Provider portal
Slika 13: Service Provider portal
Migrate selected locations (optional)
To start the migration for a specific subset of locations listed in the customer.json
file, include a locations.csv
file with your request. This CSV should list only the locations you intend to migrate.
When locations.csv is not provided, all locations in the customer.json will be migrated.
Termin | Definicija |
---|---|
ID lokacije |
The Site Id of the location to be migrated. |
Ime lokacije |
The name of the location to be migrated. |
To download the list of available active sites navigate to View Customers → Select a Customer → Export Locations as CSV.

Slika 14: Export Locations as CSV
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:
- Deregister devices from the Cisco BroadWorks and register them in Wholesale.
- Users using the UC-One client will redirect to the Webex App on first-time sign-in.
- Deactivate the Phone Numbers from Cisco BroadWorks or remove the phone numbers from BroadCloud.
- Activate numbers in Wholesale.
- Create Shared Call Appearances in Wholesale for BroadCloud migrations. [This step is applicable only for BroadCloud migrations].
SCP and SSH
- SCP the device move tool to the secondary Cisco BroadWorks Application Server.
- SSH to the secondary Cisco BroadWorks Application Server to configure the prerequisites and run the device move tool.
Preduslovi
- Set the REFRESH_TOKEN (Token copied from the Token Generator Tool) in the conf/partner.cfg file:
REFRESH_TOKEN=MzUwYjljODEtYmQ4MS00NGVhLTgwNGUtZjQ1NTEyZTViNzJkOTdj
- 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
- 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.
- Verify the JDK/JRE environment path is correct in devicemove.sh
JAVA_HOME=/usr/local/java/java_base
- 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:
- The device move tool replaces the file %BWMACADDRESS%.cfg at the device level with polycom_vvx2.cfg. This file refers to migration_%BWMACADDRESS%.cfg.
- 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.
- The device move tool asks the Cisco BroadWorks Application Server to reboot phones at the group level or device level.
- 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.
- The Polycom phone downloads %BWMACADDRESS%.cfg from https://plcm.sipflash.com and will be managed by the Webex Calling DMS.

Slika 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=
./devicemove.sh -input=/tmp/customername.json
For device move multiple customers:
./devicemove.sh -input=
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= -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
Izlaz
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:

Slika 15: Status uređaja
After the device migration, numbers have come active. Refer to figure 16 to see an example of what numbers are active:

Slika 16: Numbers active
Revert migration
The revert operation must be executed for one enterprise at a time.
For BroadCloud Carrier
The revert process for BroadCloud partners is as follows:
- Open a ticket with Cisco TAC to request a device revert.
- 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.
- 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:
- Open a ticket with Cisco TAC to request a device revert.
- 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.
- The Webex Calling Team sets the DMS URL back to the service provider DMS URL in device profiles in Webex Calling.
- Partner administrators must deactivate or delete the phone numbers in the Webex Calling through the Control Hub portal.
- 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= -revertProfiles
Revert numbers
./devicemove.sh -input= -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
Aneks
Large enterprise migration
Large enterprises that have many locations can’t migrate all locations within a single maintenance window. The functionality describes in this section allows partners to migrate a few locations at a time.
Koraci
Use the following steps to plan the phased migrations for a large enterprise:
- Extract the enterprise data from BroadWorks or BroadCloud.
- Run Transform tool without locations option on the extracted data.
- Look for the section Recommended location to move simultaneously in exception_report.txt to plan the migration phases to get more information on location dependencies, examine the features agent list files (refer to Transform tool below).
- Generate the input/ locations.csv by modifying locations_to_be_edited.csv.
- Run Transform tool again with the locations option.
- Examine exception_report.txt to identify any location dependency issues for current phase.
- Fix the location dependency issues as needed (by modifying locations.csv).
- Rerun Transform tool to generate customers.json for the current phase.
- Run the Provisioning tool for each customer.json.
- During the maintenance window, run the Device Move Tool.
- Repeat step 4 - 10 for the next phase.
Transform tool
To achieve the goal of migrating the locations in a large enterprise phase by phase, as mentioned above, a new file locations.csv is added as optional input (-locations=input/locations.csv) when running the transform-tool.
The locations.csv contains data that is specific to locations. It overrides the data found in input/customers.csv, which currently contains both enterprise and location data.
The following table lists the details of the locations.csv:
Opis |
Vrednosti |
Podrazumevana vrednost |
Obavezno |
Maps in BroadWorks |
Maps in BroadCloud | |
---|---|---|---|---|---|---|
enterpriseId |
Unique enterprise id |
Y |
serviceProviderId |
Rialto CustomerId | ||
locationId |
Location id, unique within the enterprise |
Y |
group id |
Rialto SiteId | ||
migration status |
Is this location migrated? |
migrated, dont_migrate, migrating |
migrating |
N | ||
ime |
Name of this location. Leave it empty to use locationId. |
N | ||||
vremenska zona |
N | |||||
arapski jezik |
N | |||||
address1 |
N | |||||
address2 |
N | |||||
grad |
N | |||||
država |
N | |||||
postal code |
ZIP code or postal code |
N | ||||
zemlja |
2-letter code |
N |
The locations.csv can be composed from the pre-filled locations_to_be_edited.csv when running Transform tool on large enterprise. Read further to see examples.
The locations.csv is an optional input when running transform tool, hence the Transform tool will behave same as before if the option -locations=input/locations.csv is not present.
New output files
There are 5 new output files from transform tool:
- locations_to_be_edited.csv – this is pre-filled with all locations’ info for the large enterprise to be migrated.
Primer:
locationId,enterpriseId,migration status,name,timezone,language,address1,address2,city,state,postal code,country
auto_mig_ent_grp1,auto_mig_ent,,auto_mig_ent_grp1,,,100 Main Street,,Gaithersburg,MD,20877,US
auto_mig_ent_grp2,auto_mig_ent,,auto_mig_ent_grp2,,,101 Main Street,,Gaithersburg,MD,20877,US
auto_mig_ent_grp3,auto_mig_ent,,auto_mig_ent_grp3,,,102 Main Street,,Gaithersburg,MD,20877,US
The partners/customers can use it to generate locations.csv to control the locations to be migrated for a specific phase (and update locations’ info as needed).
Primer: locations.csv generated from the above locations_to_be_edited.csv
locationId,enterpriseId,migration status,name,timezone,language,address1,address2,city,state,postal code,country
auto_mig_ent_grp1,auto_mig_ent,migrated,auto_mig_ent_grp1,,,100 Main Street,,Gaithersburg,MD,20877,US
auto_mig_ent_grp2,auto_mig_ent,migrating,auto_mig_ent_grp2,,,101 Main Street,,Gaithersburg,MD,20877,US
auto_mig_ent_grp3,auto_mig_ent,dont_migrate,auto_mig_ent_grp3,,,102 Main Street,,Gaithersburg,MD,20877,US
This locations.csvmeans: for this phase, location auto_mig_ent_grp1 had been migrated, location auto_mig_ent_grp2 is migrating, and don’t migrate location auto_mig_ent_grp3.
- hunt_group_agents.csv, call_center_agents_supervisors.csv, paging_group_originators_targets.csv, blf_monitored_elements.csv – 4 files have the same purpose: generate the complete lists of the corresponding features agents/supervisors/originators/targets/monitored_elements in the migrating locations if the migrating locations have dependencies on other locations.
They have almost same format (the 3rd column name varies based on feature), like below (auto_mig_ent_grp2’s hunt group’s agents list for the above phase):
Primer: the following is from hunt_group_agents.csv
feature name,feature location,agent,location
Sarah Rodriguez,auto_mig_ent_grp2,agent_michael@domain.com,auto_mig_ent_grp1
Sarah Rodriguez,auto_mig_ent_grp2,agent_sally@domain.com,auto_mig_ent_grp1
If the locations option not present when running the Transform tool, the above 4 files will generate the complete lists of the hunt-group/call-center/paging-group/busy-lamp-field’s agents/supervisors/originators/targets/monitored_elements for the whole enterprise, which can be used to plan the phased migrations.
New sections in exception_report
While performing phased migration for large enterprise, there will be some new sections in exception_report.txt if there are location dependencies which are not met.
Primer: The following new section is for location auto_mig_ent_grp2 hunt group Sarah Rodriguez’s agents in location auto_mig_ent_grp3 which is not migrated and not migrating in this phase.
Dependencies between locations - Hunt groups
Name Location Agent Agent's Location Comment
________________________________________________________________________________________________________________
Sarah Rodriguez auto_mig_ent_grp2 agent_william@domain.com auto_mig_ent_grp3 Agent in different location not migrated yet
Sarah Rodriguez auto_mig_ent_grp2 agent_melody@domain.com auto_mig_ent_grp3 Agent in different location not migrated yet
The following new section makes the recommendation on how to group the locations in the migration phases.
Recommended locations to move simultaneously:
Location auto_mig_ent_grp1 has dependency on location(s) auto_mig_ent_grp2, auto_mig_ent_grp3
Location auto_mig_ent_grp2 has dependency on location(s) auto_mig_ent_grp3
If the locations option not present when running the Transform tool, section recommended locations to move simultaneously lists all locations dependencies to provide the convenience for the planning.
While running the Transform tool with the locations option (ie, for a migration phase), section Recommended locations to move simultaneously only list the locations’ dependencies for the current phase.
Provisioning tool
For Large enterprise, the provisioning tool can be run as usual.
Device move tool
The device move tool can run for a subset of locations from the customer.json.to achieve that add a new optional locations.csv file which has two columns.
External_id |
LocationNames |
---|---|
External id value |
Names of the locations/group names |
- This is an optional file, if not provided or provided with the empty values it will migrate all the locations.
- If provided with the location names and their respective external_Id’s, then only those locations will be migrated.
The command is as follows:
./devicemove.sh -input=/customer.json -locations=/Location_names.csv
Vremenske zone
USA:
"timeZones":["America/Adak","America/Anchorage","America/Chicago","America/Denver","America/Los_Angeles","America/New_York","America/Phoenix","Pacific/Honolulu"]
Canada:
"timeZones":["America/Dawson_Creek","America/Edmonton","America/Halifax","America/Montreal","America/Regina","America/St_Johns","America/Vancouver","America/Winnipeg"]
Australia:
"timeZones":["Australia/Adelaide","Australia/Brisbane","Australia/Broken_Hill","Australia/Darwin","Australia/Hobart","Australia/Lord_Howe","Australia/Perth","Australia/Sydney"]
France:
"timeZones":["Europe/Paris"]
Portugal:
"timeZones":["Atlantic/Azores","Europe/Lisbon"]}
UK:
"timeZones":["Europe/London"]
Italy:
"timeZones":["Europe/Rome"]
Germany:
"timeZones":["Europe/Berlin"]