Løsningsformål

• For at levere webex cloud-samarbejdsfunktioner til små og mellemstore kunder, som allerede har opkaldstjeneste leveret af BroadWorks-tjenesteudbydere.

• For at levere BroadWorks-baseret opkaldstjeneste til små og mellemstore Webex-kunder.

Kontekst

Vi udvikler alle vores samarbejdsklienter mod en forenet applikation. Denne sti reducerer problemer med indførelse, forbedrer interoperabilitet og migrering og giver forudsigelige brugeroplevelser på tværs af hele vores samarbejdsportefølje. En del af dette arbejde er at flytte BroadWorks-opkaldskapaciteterne til Webex-appen og med tiden reducere investeringer i UC-One-klienter.

Fordele

• Fremtidig proofing: over for UC-One-samarbejdets afslutning, flytning af alle klienter mod Unified Client Framework (UCF)

• Det bedste fra begge: Aktivering af Webex-meddelelses- og mødefunktioner samtidig med, at BroadWorks-opkald bevares på dit telefoninetværk

Løsningsomfang

• Eksisterende/nye små til mellemstore kunder (færre end 250 abonnenter), der ønsker en række samarbejdsfunktioner, har muligvis allerede BroadWorks-opkald.

• Eksisterende små til mellemstore Webex-kunder, der gerne vil tilføje BroadWorks Calling.

• Ikke større virksomheder (gennemgå venligst vores virksomhedsportefølje for Webex).

• Ikke en enkelt bruger (Evaluer Webex Online tilbud).

Funktionssæt i Webex til Cisco BroadWorks er målrettet til brugstilfælde for små til mellemstore virksomheder. Webex til Cisco BroadWorks-pakker er designet til at reducere kompleksiteten for SMBs, og vi evaluerer løbende deres tilpasningsevne til dette segment. Vi kan vælge at skjule eller fjerne funktioner, der ellers ville være tilgængelige i virksomhedspakkerne.

Forudsætninger for succes med Webex til Cisco BroadWorks

#	Krav	Bemærkninger
1	Patch Current BroadWorks R22 or above
2	XSP|ADP for XSI, CTI, DMS, and authService	Dedicated XSP|ADP for Webex for Cisco BroadWorks
3	Separate XSP|ADP for NPS, can be shared with other solutions that use NPS.	If you have an existing collaborate deployment, then review recommendations on XSP|ADP and NPS configurations.
4	CI-tokenvalidering (med TLS) konfigureret til Webex-forbindelser til godkendelsestjenesten.
5	mTLS konfigureret til Webex-forbindelser til CTI-grænsefladen.	Andre applikationer kræver ikke mTLS.
6	Brugere skal eksistere i BroadWorks og har brug for følgende attributter, afhængigt af din klargørings beslutning: Flowthroverensstemmelse med betroede e-mails: E-mailattribut for BroadWorks-bruger skal indeholde en gyldig e-mailadresse, der er unik for denne bruger. User must also have a primary number or extension. Flowthraktivering med ikke-betroede e-mails eller selvaktivering eller API-klargøring: User does not need email address but must have a primary number or extension.	For betroede e-mails: Vi anbefaler, at du også skriver den samme e-mailadresse i attributten Alternativt ID for at gøre det muligt for brugere at logge ind med e-mailadresse mod BroadWorks. For ikke-betroede e-mails: Afhængigt af brugerens e-mailindstillinger kan brugen af ikke-betroede e-mails resultere i, at e-mailen sendes til brugerens uønskede eller SPAM-mappe. Administratoren skal muligvis ændre brugerens e-mailindstillinger for at tillade domæner
7	Webex til Cisco BroadWorks DTAF-fil til Webex-app
8	BW Business Lic eller Std Enterprise eller Prem Enterprise User Lic + Webex til Cisco BroadWorks-abonnement	Hvis du har en eksisterende udrulning af samarbejde, har du ikke længere brug for UC-One Add-On Bundle, Collab Lic og Meet-me konferenceporte. Hvis du har en eksisterende UC-One SaaS-udrulning, er der ingen yderligere ændringer end at acceptere Vilkårene for Premium Package.
9	IP/porte skal være tilgængelige via Webex-backend-tjenester og Webex-apps via offentligt internet.	Se afsnittet "Forbered dit netværk".
10	TLS v1.2 Configuration on XSP|ADPs
11	For at klargøre flowthrskal skal applikationsserveren tilslutte til BroadWorks-klargøringsadapter.   Vi tester eller understøtter ikke udgående proxykonfiguration. Hvis du bruger en udgående proxy, accepterer du ansvaret for at understøtte den med Webex for Cisco BroadWorks.	Se emnet "Forbered dit netværk".

Om dette dokument

Formålet med dette dokument er at hjælpe dig med at forstå, forberede, implementere og administrere din Webex til Cisco BroadWorks-løsning. De store afsnit i dokumentet afspejler dette formål.

Denne vejledning inkluderer referencemateriale og referencemateriale. Vi har til hensigt at dække alle aspekter af løsningen i dette dokument.

Det mindste sæt opgaver til at implementere løsningen er:

1. Kontakt dit kontoteam for at blive Cisco-partner. Det er afgørende, at du udforsker Cisco touch-pointene for at gøre dig selv bekendt (og opdage muligheder). Når du bliver Cisco-partner, anvender vi Webex til at skifte Cisco BroadWorks til din Webex-partnerorganisation. (Se Installer Webex til Cisco BroadWorks > Partner Onboarding i dette dokument.)

2. Konfigurer dine BroadWorks-systemer til integration med Webex. (See Deploy Webex for Cisco BroadWorks > Configure Services on Your Webex for Cisco BroadWorks XSP|ADPs in this document.)

3. Brug Partner Hub til at tilslutte Webex til BroadWorks. (Se Installer Webex til Cisco BroadWorks > Konfigurer din partnerorganisation i Partner Hub i dette dokument.)

4. Brug Partner Hub til at forberede bruger klargøringsskabeloner. (See Deploy Webex for Cisco BroadWorks > Configure your Onboarding templates in this document.)

5. Test and onboard a customer by provisioning at least one user. (See Deploy Webex for Cisco BroadWorks > Configure Your Test Organization.)

Disse er højniveautrin i den typiske rækkefølge. Du kan ikke ignorere flere medvirkende opgaver. Hvis du vil oprette dine egne programmer for at administrere dit Webex for Cisco BroadWorks-abonnenter, skal du læse Brug klargørings API i afsnittet Reference i denne vejledning.

Terminologi

We try to limit the jargon and acronyms used in this document, and to explain each term when it’s first used. (See Webex for Cisco BroadWorks Reference > Terminology if a term isn’t explained in context.)

Webex-sikkerhed

Webex-klienten er en sikker applikation, der foretager sikre forbindelser til Webex og BroadWorks. De data, der er gemt i Webex Cloud og udsat for brugeren via Webex app-grænsefladen, krypteres både ved overførsel og i hvile.

Der er flere oplysninger om dataudveksling i afsnittet Reference i dette dokument.

Yderligere læsning

• https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/cloudCollaboration/spark/esp/cisco-spark-security-white-paper.pdf

• https://trustportal.cisco.com/c/dam/r/ctp/docs/privacydatasheet/collaboration/cisco-broadcloud-uc-one-saas-privacy-data-sheet.pdf

• https://www.cisco.com/c/en/us/products/security/general-data-protection-regulation.html

• https://www.cisco.com/c/en/us/about/trust-center/gdpr.html

• https://www.cisco.com/c/en/us/products/security/comply-with-GDPR.html

• https://www.cisco.com/c/en/us/about/legal/privacy-full.html

Organisationsdataopbevaring

Vi gemmer dine Webex-data i det datacenter, der passer mest til din region. Se Data residency i Webex i Hjælpecenter.

Roller

Tjenesteudbyderadministrator (dig): For dag-til-dag vedligeholdelsesaktiviteter administrerer du lokale (opkald) dele af løsningen ved hjælp af dine egne systemer. Du administrerer Webex-delene af løsningen via Partner Hub.

For information on the roles that are available to partners, the access privileges that accompany those roles, and how to assign roles, see Partner Administrator Roles for Webex for BroadWorks and Wholesale RTM.

The first user provisioned to a new partner organizaiton is assigned automatically to the Full Administrator and Full Partner Administrator roles. That administrator can use the above article to assign additional roles.

Cisco cloud-driftsteam: Opretter din "partnerorganisation" i Partner Hub, hvis den ikke eksisterer, under din onboarding.

Når du har din Partner Hub-konto, skal du konfigurere Webex-grænsefladerne til dine egne systemer. You next create “Onboarding templates” to represent the suites or packages served through those systems. Derefter klargør du dine kunder eller abonnenter.

Hvad er i diagrammet?

Klienter

• Webex App-klienten fungerer som den primære applikation i Webex til Cisco BroadWorks tilbud. Klienten er tilgængelig på desktop-, mobil- og webplatforme.

  Klienten har indbyggede meddelelser, tilstedeværelse og lyd/videomøder med flereparter i Webex-skyen. Webex-klienten bruger din BroadWorks-infrastruktur til SIP og PSTN opkald.

• Cisco IP-telefoner og tilknyttede tilbehør bruger også din BroadWorks-infrastruktur til SIP- PSTN opkald. Vi forventer at kunne understøtte tredjepartstelefoner.

• Brugeraktiveringsportal, så brugere kan logge ind på Webex ved hjælp af deres BroadWorks-legitimationsoplysninger.

• Partner Hub er en webgrænseflade til administration af din Webex-organisation og dine kunders organisationer. Partner Hub er stedet, hvor du konfigurerer integrationen mellem din BroadWorks-infrastruktur og Webex. Du bruger også Partner Hub til at administrere klientkonfiguration og -fakturering.

Tjenesteudbyder netværk

Den grønne blok til venstre i diagrammet repræsenterer dit netværk. Komponenter, der hostes i dit netværk, leverer følgende tjenester og grænseflader til andre dele af løsningen:

• Public-facing XSP|ADP, for Webex for Cisco BroadWorks: (The box represents one or multiple XSP|ADP farms, possibly fronted by load balancers.)

  • Værter for Xtended Services Interface (XSI-Actions & XSI-Events), Device Administrationsservice (DMS), CTI-grænseflade og godkendelsestjeneste. Disse programmer giver sammen telefoner og Webex-klienter mulighed for at godkende sig selv, downloade deres opkaldskonfigurationsfiler, foretage og modtage opkald og se hinandens krogstatus (telefoni tilstedeværelse) og opkaldshistorik.

  • Udgiver adressebog til Webex-klienter.

• Public-facing XSP|ADP, running NPS:

  • host opkald meddelelser push-server: A Notification Push Server on an XSP|ADP in your environment. Den grænseflader mellem din applikationsserver og vores NPS-proxy. Proxyen leverer tokens med kort varsel til dine NPS for at autorisere underretninger til cloudtjenester. Disse tjenester (APNS & FCM) sender opkaldsmeddelelser til Webex-klienter på Apple iOS- og Google Android-enheder.

• Applikationsserver:

  • Giver opkaldskontrol og grænseflader til andre BroadWorks-systemer (generelt)

  • For flowthr provisionering bruges AS af partneradministratoren til at klargøre brugere i Webex

  • Skubber brugerprofil ind i BroadWorks

• OSS/BSS: Dit Driftssupportsystem/Business SIP-tjenester til administration af dine BroadWorks-virksomheder.

Webex Cloud

Blå blok i diagrammet repræsenterer Webex-skyen. Webex-mikrotjenester understøtter alle Webex-samarbejdsegenskaber:

• Cisco Common Identity (CI) er den identitetstjeneste i Webex.

• Webex til Cisco BroadWorks repræsenterer sættet af mikrotjenester, der understøtter integrationen mellem Webex og Tjenesteudbyder BroadWorks:

  • Bruger klargørings-API'er

  • Tjenesteudbyder konfiguration

  • Brugerlogin ved hjælp af BroadWorks-legitimationsoplysninger

• Webex-meddelelsesboks til meddelelsesrelaterede mikrotjenester.

• Webex Meetings, der repræsenterer mediebehandlingsservere og SBCs for flere deltagervideomøder (SIP & SRTP)

Tredjeparts-webtjenester

Følgende tredjepartskomponenter er repræsenteret i diagrammet:

• APNS (Apple Push Notifications Service) pusher opkalds- og beskedunderretninger til Webex-applikationer på Apple-enheder.

• FCM (FireBase Cloud Messaging) sender opkalds- og beskedunderretninger til Webex-applikationer på Android-enheder.

XSP|ADP Architecture Considerations

The Role of Public-Facing XSP|ADP Servers in Webex for Cisco BroadWorks

The public-facing XSP|ADP in your environment provides the following interfaces/services to Webex and clients:

• Bekræftelsestjeneste (AuthService), sikret af TLS, som besvarer Webex-anmodninger om BroadWorks JWT (JSON Web Token) på brugerens vegne

• CTI-grænseflade, sikret med mTLS, som Webex abonnerer på for opkaldshistorik begivenheder og telefoni-tilstedeværelsesstatus fra BroadWorks (hook-status).

• Xsi-handlinger og -begivenhedsgrænseflader (eXtended Services Interface) til opkaldskontrol for abonnenten, kontakt- og opkaldslistemapper og konfiguration af slutbrugertelefonitjeneste

• DM (Device Management) tjeneste for klienter til at hente deres opkaldskonfigurationsfiler

Levering af URL-adresser for disse grænseflader, når du konfigurerer Webex til Cisco BroadWorks. (See Configure your BroadWorks Clusters in Partner Hub in this document.) For each cluster, you can only provide one URL for each interface. Hvis du har flere grænseflader i din BroadWorks-infrastruktur, kan du oprette flere klynger.

XSP|ADP Architecture

We require that you use a separate, dedicated XSP|ADP instance or farm to host your NPS (Notification Push Server) application. Du kan bruge de samme NPS med UC-One SaaS eller UC-One samarbejd. However, you may not host the other applications required for Webex for Cisco BroadWorks on the same XSP|ADP that hosts the NPS application.

We recommend that you use a dedicated XSP|ADP instance/farm to host the required applications for Webex integration for the following reasons

• For example, if you’re offering UC-One SaaS, we recommend creating a new XSP|ADP farm for Webex for Cisco BroadWorks. På den måde kan de to tjenester fungere uafhængigt, mens du migrerer abonnenter.

• If you collocate the Webex for Cisco BroadWorks applications on an XSP|ADP farm that is used for other purposes, it's your responsibility to monitor usage, manage the resulting complexity, and plan for the increased scale.

• The Cisco BroadWorks System Capacity Planner assumes a dedicated XSP|ADP farm and may not be accurate if you use it for collocation calculations.

Unless noted otherwise, the dedicated Webex for Cisco BroadWorks XSP|ADPs must host the following applications:

• AuthService (TLS med CI-tokenvalidering eller mTLS)

• CTI (mTLS)

• XSI-handlinger (TLS)

• XSI-Begivenheder (TLS)

• DMS (TLS)—Optional. It's not mandatory that you deploy a separate DMS instance or farm specifically for Webex for Cisco BroadWorks. You can use the same DMS instance that you use for UC-One SaaS or UC-One Collaborate.

• Call Settings Webview (TLS)—Optional. Call Settings Webview (CSW) is required only if you want Webex for Cisco BroadWorks users to be able to configure calling features on the Webex App.

Webex kræver adgang til CTI igennem en grænseflade, der er sikret fælles TLS godkendelse. For at understøtte dette krav anbefaler vi en af disse valgmuligheder:

• (Diagram labelled Option 1) One XSP|ADP instance or farm for all applications, with two interfaces configured on each server: en mTLS-grænseflade for CTI og en TLS-grænseflade til andre apps, såsom AuthService.

• (Diagram labelled Option 2) Two XSP|ADP instances or farms, one with an mTLS interface for CTI, and the other with a TLS interface for other apps, such as the AuthService.

XSP|ADP Reuse If you have an existing XSP|ADP farm that conforms to one of the suggested architectures above (Option 1 or 2) and it is lightly loaded, then it is possible to reuse your existing XSP|ADPs. You will need to verify that there are no conflicting configuration requirements between existing applications and the new application requirements for Webex. De to primære overvejelser er: If you need to support multiple webex partner organizations on the XSP|ADP, then that means you must use mTLS on the Auth Service (CI Token Validation is only supported for a single partner organization on an XSP|ADP). Hvis du bruger mTLS på godkendelsestjenesten, betyder det, at du ikke kan have klienter, der bruger basisgodkendelse på bekræftelsestjenesten på samme tid. This situation would prevent reuse of the XSP|ADP. If the existing CTI Service configured to be used by clients with the secure port (typically 8012) but without mTLS (i.e., client authentication) then that will conflict with the webex requirement to have mTLS. Because the XSP|ADP’s have many applications and the number of permutations of these applications is large, there may be other unidentified conflicts. For this reason, any potential reuse of XSP|ADP’s should be verified in a lab with the intended configuration prior to committing to the reuse.

Configure NTP Synchronization on XSP|ADP

The deployment requires time synchronization for all XSP|ADPs that you use with Webex.

Installer ntp-pakken, når du har installeret OS'et, og før du installerer BroadWorks-softwaren. Then you can configure NTP during the XSP|ADP software installation. Se BroadWorks Software Management Guide for yderligere oplysninger.

During the interactive installation of the XSP|ADP software, you’re given the option to configure NTP. Fortsæt som følger:

1. Når installeringsprogrammet spørger, Vil du konfigurere NTP?, indtast y.

2. Når installeringsprogrammet spørger, Vil denne server være en NTP-server? , indtast n .

3. Når installeringsprogrammet spørger, hvad er NTP-adressen, værtsnavnet eller FQDN? , indtast adressen på din NTP-server eller en offentlig NTP-tjeneste, for eksempel pool.ntp.org.

If your XSP|ADPs use silent (noninteractive) installation, the installer configuration file must include the following Key=Value pairs:

NTP

NTP_SERVER=<NTP Server address, e.g., pool.ntp.org>

XSP|ADP Identity and Security Requirements

Baggrund

Protokollerne og koderne for Cisco BroadWorks TLS-forbindelser kan konfigureres på forskellige specificitetsniveauer. Disse niveauer varierer fra den mest generelle (SSL-udbyder) til den mest specifikke (individuel grænseflade). En mere specifik indstilling tilsidesætter altid en mere generel indstilling. Hvis de ikke er angivet, så nedarves SSL-indstillinger på lavere niveau fra "højere" niveauer.

Hvis ingen indstillinger ændres fra deres standardindstillinger, så overtager alle niveauer SSL-udbyderens standardindstillinger (JSSE Java Secure Sockets Extension).

Kravliste

• The XSP|ADP must authenticate itself to clients using a CA-signed certificate in which the Common Name or Subject Alternate Name matches the domain portion of the XSI interface.

• Xsi-grænsefladen skal understøtte TLSv1.2-protokollen.

• Xsi-grænsefladen skal bruge en kodepakke, der opfylder følgende krav.

  • Diffie-Hellman kortvarig (DHE) eller elliptisk kurve Diffie-Hellman kortvarig (ECDHE) key-exchange

  • AES (Avanceret krypteringsstandard) kode med en minimumsblokstørrelse på 128 bits (f.eks. AES-128 eller AES-256)

  • GCM (kugleskædnings-/tællertilstand) eller CBC (kodeblokkædning) kodetilstand

    • Hvis en CBC-kode bruges, er det kun SHA2-serien af hash-funktioner, der er tilladt for nøglefunktioner (SHA256, SHA384, SHA512).

For eksempel opfylder følgende koder kravene:

• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

• TLS_DHE_PSK_WITH_AES_256_CBC_SHA384

The XSP|ADP CLI requires the IANA naming convention for cipher suites, as shown above, not the openSSL convention.

Understøttede TLS-koder til AuthService- og XSI-grænseflader

Denne liste kan blive ændret, efterhånden som vores cloud-sikkerhedskrav ændres. Følg den aktuelle Cisco Cloud-sikkerhedsanbefaling ved valg af kode, som beskrevet på listen over krav i dette dokument.

• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256

• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256

• TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256

• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256

• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

• TLS_DHE_RSA_WITH_AES_256_CBC_SHA256

• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256

• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

• TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

• TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA

• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

• TLS_DHE_RSA_WITH_AES_256_CBC_SHA

• TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA

• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA

• TLS_DHE_RSA_WITH_AES_128_CBC_SHA

• TLS_RSA_PSK_WITH_AES_256_GCM_SHA384

• TLS_DHE_PSK_WITH_AES_256_GCM_SHA384

• TLS_RSA_PSK_WITH_CHACHA20_POLY1305_SHA256

• TLS_DHE_PSK_WITH_CHACHA20_POLY1305_SHA256

• TLS_ECDHE_PSK_WITH_CHACHA20_POLY1305_SHA256

• TLS_RSA_WITH_AES_256_GCM_SHA384

• TLS_PSK_WITH_AES_256_GCM_SHA384

• TLS_PSK_WITH_CHACHA20_POLY1305_SHA256

• TLS_RSA_PSK_WITH_AES_128_GCM_SHA256

• TLS_DHE_PSK_WITH_AES_128_GCM_SHA256

• TLS_RSA_WITH_AES_128_GCM_SHA256

• TLS_PSK_WITH_AES_128_GCM_SHA256

• TLS_RSA_WITH_AES_256_CBC_SHA256

• TLS_RSA_WITH_AES_128_CBC_SHA256

• TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA384

• TLS_ECDHE_PSK_WITH_AES_256_CBC_SHA

• TLS_RSA_PSK_WITH_AES_256_CBC_SHA384

• TLS_DHE_PSK_WITH_AES_256_CBC_SHA384

• TLS_RSA_PSK_WITH_AES_256_CBC_SHA

• TLS_DHE_PSK_WITH_AES_256_CBC_SHA

• TLS_RSA_WITH_AES_256_CBC_SHA

• TLS_PSK_WITH_AES_256_CBC_SHA384

• TLS_PSK_WITH_AES_256_CBC_SHA

• TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA256

• TLS_ECDHE_PSK_WITH_AES_128_CBC_SHA

• TLS_RSA_PSK_WITH_AES_128_CBC_SHA256

• TLS_DHE_PSK_WITH_AES_128_CBC_SHA256

• TLS_RSA_PSK_WITH_AES_128_CBC_SHA

• TLS_DHE_PSK_WITH_AES_128_CBC_SHA

• TLS_RSA_WITH_AES_128_CBC_SHA

• TLS_PSK_WITH_AES_128_CBC_SHA256

• TLS_PSK_WITH_AES_128_CBC_SHA

Skaleringsparametre for Xsi Events

Du er muligvis nødt til at øge Xsi-Events-køstørrelsen og trådantallet for at håndtere lydstyrken for begivenheder, som Webex til Cisco BroadWorks-løsningen kræver. Du kan øge parametrene til de minimumsværdier, der vises, som følger (du skal ikke sænke dem, hvis de ligger over disse minimumsværdier):

XSP|ADP_CLI/Applications/Xsi-Events/BWIntegration> eventQueueSize = 2000

XSP|ADP_CLI/Applications/Xsi-Events/BWIntegration> eventHandlerThreadCount = 50

Multiple XSP|ADPs

Indlæs balancerings edge-element

If you have a load balancing element on your network edge, it must transparently handle the distribution of traffic between your multiple XSP|ADP servers and the Webex for Cisco BroadWorks cloud and clients. I dette tilfælde skal du angive URL-adressen for indlæsningsbalancen i Webex til Cisco BroadWorks-konfiguration.

Noter til denne arkitektur:

• Konfigurer DNS, så klienterne kan finde indlæsnings balanceren, når du opretter forbindelse til Xsi-grænsefladen (se DNS-konfiguration).

• Vi anbefaler, at du konfigurerer Edge-elementet i omvendt SSL-proxytilstand for at sikre, at peger på datakryptering.

• Certificates from XSP|ADP01 and XSP|ADP02 should both have the XSP|ADP domain, for example your-XSP|ADP.example.com, in the Subject Alternate Name. They should have their own FQDNs, for example XSP|ADP01.example.com, in the Common Name. Du kan bruge jokertegn certifikater, men vi anbefaler dem ikke.

Internet-Facing XSP|ADP Servers

If you expose the Xsi interfaces directly, use DNS to distribute the traffic to the multiple XSP|ADP servers.

Noter til denne arkitektur:

• Two records are required to connect to the XSP|ADP servers:

  • For Webex microservices: Round-robin A/AAAA records are required to target the multiple XSP|ADP IP addresses. This is because the Webex microservices can’t do SRV lookups. For examples, see Webex Cloud Services.

  • For Webex App: An SRV record that resolves to A records where each A record resolves to a single XSP|ADP. For examples, see Webex App.

    Use prioritized SRV records to target the XSI service for the multiple XSP|ADP addresses. Prioritize your SRV records so that the microservices will always go to the same A record (and subsequent IP address) and will only move to the next A record (and IP address) if the first IP address is down. DO NOT use a round-robin approach for the Webex App.

• Certificates from XSP|ADP01 and XSP|ADP02 should both have the XSP|ADP domain, for example your-XSP|ADP.example.com, in the Subject Alternate Name. They should have their own FQDNs, for example XSP|ADP01.example.com, in the Common Name.

• Du kan bruge jokertegn certifikater, men vi anbefaler dem ikke.

Undgå HTTP-omdirigeringer

Sometimes, DNS is configured to resolve the XSP|ADP URL to an HTTP load balancer, and the load balancer is configured to redirect through a reverse proxy to the XSP|ADP servers.

Webex does not follow a redirect when connecting to the URLs you supply, so this configuration does not work.

Flowthrough Provisioning with Trusted Emails

Du konfigurerer den integrerede IM&P-tjeneste til at bruge en Webex-klargørings-URL-adresse og derefter tildeler tjenesten til brugerne. Applikationsserveren bruger Webex-klargørings-API'en til at anmode om de tilsvarende Webex-brugerkonti.

Hvis du kan påstå, at BroadWorks har gyldige e-mailadresser som abonnent og unikke for Webex, opretter og aktiverer denne klargøringsvalgmulighed automatisk Webex-konti med disse e-mailadresser som bruger-id.

Du kan ændre abonnentpakken via Partner Hub, eller du kan skrive din egen applikation for at bruge klargørings-API'en til at ændre abonnentpakker.

Flowthrvirke-klargøring uden betroede e-mails

Du konfigurerer den integrerede IM&P-tjeneste til at bruge en Webex-klargørings-URL-adresse og derefter tildeler tjenesten til brugerne. Applikationsserveren bruger Webex-klargørings-API'en til at anmode om de tilsvarende Webex-brugerkonti.

Hvis du ikke kan stole på abonnentens e-mailadresser, som BroadWorks opbevarer, opretter denne valgmulighed Webex-konti, men de kan ikke aktiveres, før abonnenter leverer og validerer deres e-mailadresser. På det tidspunkt kan Webex aktivere kontiene med disse e-mailadresser som bruger-id'er.

Du kan ændre abonnentpakken via Partner Hub, eller du kan skrive din egen applikation for at bruge klargørings-API'en til at ændre abonnentpakker.

Brugers selvbetjening

Med denne valgmulighed er der ingen flowthroption-klargøring fra BroadWorks til Webex. Når du har konfigureret integrationen mellem Webex og dit BroadWorks-system, får du et eller flere links, der er specifikke for klargøring af brugere i din Webex til Cisco BroadWorks-partnerorganisation.

Derefter designer du dine egne kommunikationer (eller uddeleger til dine kunder) for at distribuere linket til abonnenter. Abonnenterne følger linket, og forsyning og valider så deres e-mailadresser for at oprette og aktivere deres egne Webex-konti.

Da kontiene er klargjort inden for din partnerorganisations rækkevidde, kan du manuelt justere brugerpakker via Partner Hub eller bruge API'en til at gøre det.

Brugere skal findes i BroadWorks-systemet, som du integrerer med Webex, eller de kan ikke oprette konti med det link.

Tjenesteudbyder af API'er

Webex viser et sæt offentlige API'er, der gør det muligt at bygge Webex til Cisco BroadWorks-bruger/abonnentklargøring i din eksisterende arbejdsgang/værktøjer til brugeradministration.

Påkrævede programrettelser med flow-through klargøring

Hvis du bruger flow-through klargøring, skal du installere en system programrettelse og anvende en CLI-egenskab. Se nedenstående liste for vejledninger, der gælder for din BroadWorks udgivelse:

For R22:

1. Install AP.as.22.0.1123.ap376508.

2. After installation, set the property bw.msg.includeIsEnterpriseInOSSschema to true from the CLI in Maintenance/ContainerOptions.

   For yderligere oplysninger, se noterne til https://www.cisco.com/web/software/286326332/154309/AP.as.22.0.1123.ap376508.txtprogramrettelsen .

For R23:

1. Install AP.as.23.0.1075.ap376509

2. After installation, set the property bw.msg.includeIsEnterpriseInOSSschema to true from the CLI in Maintenance/ContainerOptions.

   For yderligere oplysninger, se noterne til https://www.cisco.com/web/software/286326332/154325/AP.as.23.0.1075.ap376509.txtprogramrettelsen .

For R24:

1. Install AP.as.24.0.944.ap375100

2. After installation, set the property bw.msg.includeIsEnterpriseInOSSschema to true from the CLI in Maintenance/ContainerOptions.

   For yderligere oplysninger, se noterne til https://www.cisco.com/web/software/286326332/154326/AP.as.24.0.944.ap375100.txtprogramrettelsen .

Når du har fuldført disse trin, vil du ikke kunne klargøre nye brugere med UC-One-samarbejdstjenester. Nyligt klargjorte brugere skal være Webex for Cisco BroadWorks-brugere.

Extension Dialing

Extension Dialing feature support allows Webex for Cisco Broadworks users to dial other users with an extension similar to the primary phone number within the same enterprise. This is especially useful for users who do not have DID numbers.

During provisioning, the extension of the users gets stored in the Webex directory as the user’s extension. For BroadWorks calling, the extension appears on the Webex App in the extension field of all the call initiation method areas and the user’s profile. Webex for Cisco BroadWorks supports extension-only calls between users within the same group and different groups of the same enterprise with the combination of location dialing code and extension. However, calling between two enterprises using only extensions is not supported.

An extension can be provisioned for the Cisco BroadWorks users through the following methods:

• Cisco BroadWorks users

  • Public API provisioning as ‘extension

    • The extension parameter should be explicitly passed as part of the API call. For enterprises/groups that have Location Dialing Code (LDC) configured, the extension parameter should be the combination of LDC and 'extension number.

  • Flowthrough or Self-Activation provisioning

    • Extension and LDC (where applicable) will be automatically retrieved from BroadWorks.

• BroadWorks-only Calling users or entities

  • Synced automatically from BroadWorks by Directory Sync using the combination of Location Dialing Code (LDC) and extension number.

Forudsætninger

1. Client version required for supporting this feature is 42.11 or later.

2. Patch where extension and location dialing codes are added to XSI and Provisioning Adapter February 2022 for version 23 or above as part of :

   • AP.platform.23.0.1075.ap380045

   • AP.as.23.0.1075.ap380045

   • AP.xsp.23.0.1075.ap380045

   • AP.as.24.0.944.ap380045

3. Enable the header X-BroadWorks-Remote-Party-Info on the AS using the below CLI command for this SIP call flow which is required for extension dialing feature support.

   AS_CLI/System/DeviceType/SIP> set <device_profile_type> supportRemotePartyInfo true

App Call Options Priority

As part of the Extension Dialing feature support, The app call options priority setting is also provided at the partner level for all the Webex for Cisco Broadworks partners. Using this setting, the partner can control the call priority settings of all its managed customers from Partner Hub. The app call options priority setting for a customer can also be modified at a customer level from Control Hub.

The app call options priority setting contains extension as second option in both Partner Hub and Control Hub when a Webex for Cisco Broadworks user is newly provisioned with extension through any of the above-mentioned provisioning methods.

For all the existing provisioned Orgs, the extension option will be in the hidden state (by default) in the app call options priority setting. This will not show an extension in the audio/video call option of the user in the Webex App.

Following are the options to make the extension call option visible for the existing customers:

1. If a partner wants all its managed customer orgs to be provided with an extension as one of the call options, it is recommended for the Partner Admin to move the Extension from hidden to available in Partner Hub. This will let the managed customer orgs inherit the setting from their partner.

2. If a Partner wants to provide an extension in call options for a specific customer org, it is recommended for the Partner Admin to move the extension from hidden to available in Control Hub.

Group Contacts Support

This feature enhances the Webex for BroadWorks DirSync service by removing the limitation for syncing up to 1500 contacts from the Group phone lists on BroadWorks and allowing partners to sync up to 30K contacts from a single Group phone list and bring it on par with the 30K contacts increase for Enterprise phone list, which was released separately.

There is an overall limit of 200K for all external contacts per Organization, which would apply to the sum of Enterprise and Group phone lists in a single BroadWorks enterprise. For example, a BroadWorks enterprise that has Enterprise phone list with 30K and also 5 Group phone lists each with 30K will be supported (180K total per Org). However, if there are 6 group phone lists each with 30K, this will not be supported (210K total).

This feature is available on request. Please contact your account team to have it enabled. Before enabling the feature, a prerequisite migration is to be run to provision and associate groups for all the existing provisioned users. Cisco team will run an internal API to migrate any existing provisioned users to associate them with the correct group. BEMÆRK: This can take up to one week to process. Once the migration is completed for the partner and the feature is enabled, any newly provisioned users will be 'grouped' appropriately.

After the feature is enabled, the DirSync service starts syncing BroadWorks Group phone list contacts into dedicated per group contact storage in the Webex Contact Service.

During provisioning, the enterprise group of the user needs to be stored in the Webex directory to indicate the group this user belongs to. The association of the user with a BroadWorks group in the Webex Directory allows the Webex app to do contact search in the Contact Service group storage for the specific group of the user.

The feature requires the Webex for BroadWorks subscribers to be provisioned in Webex with the BroadWorks enterprise Group Id.

The BroadWorks enterprise Group Id can be provisioned for the Cisco BroadWorks users through the following methods:

• Webex til Cisco BroadWorks-brugere

  • Public API provisioning as ‘spEnterpriseGroupId’

    • The BroadWorks enterprise Group Id should be explicitly passed in spEnterpriseGroupId parameter of the API call.

  • Flowthrough or Self-Activation provisioning

    • BroadWorks enterprise Group Id will be automatically retrieved from BroadWorks.

  • BroadWorks-only Calling users or entities

    • Not applicable. It’s not required to sync BroadWorks enterprise Group Id for these users.

Public API must be updated PRIOR to the MIGRATION. Migration cannot be completed until THIS API is completed The BroadWorks enterprise Group Id should be explicitly passed in spEnterpriseGroupId parameter of the API call https://developer.webex.com/docs/api/changelog#2023-march After the feature is enabled and as a result of the next directory sync the enterprise user groups will also be displayed in Control Hub. Visualizing the groups in Control Hub for Webex for BroadWorks is purely informational at this stage. Partner and customer admins should not make any modifications to groups or group membership in Control Hub as these changes will not be reflected back to BroadWorks. Group Management in Control Hub is intended for use by partners who will be adopting the upcoming Contact Management APIs.