All subscribers that you are provisioning for Webex must exist in the BroadWorks system that you integrate with Webex. You can integrate multiple BroadWorks systems if necessary.

All subscribers must have BroadWorks licenses and a primary number or extension.

Webex uses email addresses as primary identifiers for all users. If you are using flowthrough provisioning with trusted emails, then your users must have valid addresses in the email attribute in BroadWorks.

If your template uses BroadWorks authentication, you can copy subscriber email addresses into the Alternate ID attribute in BroadWorks. This makes it possible for users to sign into Webex using their email addresses and their BroadWorks passwords.

Your admins must use their Webex accounts to sign in to Partner Hub.

• BroadWorks instance(s) with minimum version R22. See BroadWorks Software Requirements (in this document) for supported versions and patches. For more information, see BroadSoft products lifecycle policy section in BroadSoft Lifecycle Policy and BroadWorks Software Compatibility Matrix.

• The BroadWorks instance(s) should include at least the following servers:

  • Application Server (AS) with BroadWorks version as above

  • Network Server (NS)

  • Profile Server (PS)

• Public-facing XSP|ADP Server(s) or Application Delivery Platform (ADP) meeting the following requirements:

  • Authentication service (BWAuth)

  • XSI actions and events interfaces

  • DMS (device management web application)

  • CTI interface (Computer Telephony Intergration)

  • TLS 1.2 with a valid certificate (not self-signed) and any intermediates required. Requires System Level Admin to facilitate enterprise lookup.

  • Mutual TLS (mTLS) authentication for Authentication Service (Requires the public Webex client certificate chain installed as trust anchors)

  • Mutual TLS (mTLS) authentication for CTI interface (Requires the public Webex client certificate chain installed as trust anchors)

• A separate XSP/ADP server acting as a “Call Notifications Push Server” (an NPS in your environment used to push call notifications to Apple/Google. We call it “CNPS” here to distinguish it from the service in Webex that delivers push notifications for messaging and presence).

  This server must be on R22 or later.

• We mandate a separate XSP/ADP server for CNPS because the unpredictability of the load from Webex for BWKS cloud connections could negatively impact the performance of the NPS server, with the result of increasing notification latency. See the Cisco BroadWorks System Engineering Guide for more on XSP|ADP scale.

To download the English version of the Webex App, go to https://www.webex.com/webexfromserviceproviders-downloads.html. The Webex App is available on:

• Windows PCs/laptops

• Apple PCs / laptops with MacOS

• iOS (Apple store)

• Android (Play store)

• Web browsers (go to https://teams.webex.com/)

Localized Versions

To download a localized version of the Webex App, use one of these links:

• https://www.webex.com/ko/webexfromserviceproviders-downloads.html (Korean)

• https://www.webex.com/fr/webexfromserviceproviders-downloads.html (French)

• https://www.webex.com/pt/webexfromserviceproviders-downloads.html (Portuguese)

• https://www.webex.com/zh-tw/webexfromserviceproviders-downloads.html (Chinese Traditional)

• https://www.webex.com/zh-cn/webexfromserviceproviders-downloads.html (Chinese Simplified)

• https://www.webex.com/ja/webexfromserviceproviders-downloads.html (Japan)

• https://www.webex.com/es/webexfromserviceproviders-downloads.html (Spain)

• https://www.webex.com/de/webexfromserviceproviders-downloads.html (German)

• https://www.webex.com/it/webexfromserviceproviders-downloads.html (Italian)