Webex for BroadWorks is a new offering from Cisco that provides your BroadWorks calling customers with Webex collaboration features. Subscribers use a single Webex app for chatting, making calls, and hosting and joining meetings.


This article is intended for Service Provider administrators managing Webex for BroadWorks on behalf of your customers. For end-user features, see What's New in Webex.

For technical documentation, see the Webex for BroadWorks Knowledge Portal.

Premium subscriber packages

The Premium package has been added to the offer. Features include meetings with up to 1000 participants, recording, and more. For more information, see the Feature Matrix.

Change subscriber packages

You can now change a subscriber’s package manually through Partner Hub. In the early release, this was only possible using an API call.

Sign in to Partner Hub, open the Customer organization and find the user, then change the package.

Provisioning subscribers with untrusted emails

We no longer mandate that your subscribers have trusted email addresses in BroadWorks. Now when you assign the Integrated IM&P service to the subscriber in BroadWorks, Webex pauses the user provisioning process until the user provides and validates their own email address. In this mode, you or your customers need to communicate a provisioning link to those subscribers, so they can activate their Webex accounts.

Subscriber self-activation

This new provisioning mode does not require you to assign the Integrated IM&P service to the subscribers in BroadWorks. What you do instead is send them a provisioning link, so that they can supply and validate their email addresses to Webex, thus creating and activating their accounts.

Note that the subscribers must be in the same BroadWorks system that you connected to Webex, and they must have BroadWorks telephone numbers. The provisioning links you use are specific to your organization and its provisioning templates.

Enhanced configuration wizards for cluster and template

We added better validation and error messaging into the Cluster creation wizard, due to feedback we received about an early version. The Cluster wizard now checks each interface and provides better error messages, and prevents you from saving the cluster if there are any failed validations.

We also improved the template creation wizard with several new settings to enable you to configure the new provisioning modes.

Subscriber provisioning status page

This new page in Partner Hub is designed yo help you investigate subscriber onboarding issues. It shows the status of the provisioning request for each user, and whether they have yet to supply or validate their email addresses.

Public release of Webex for BroadWorks provisioning APIs

With this release, we are opening up the Webex for BroadWorks Provisioning APIs, so that anyone with access to developer.webex.com whose organizations are entitled to this offer can use the APIs for managing their subscribers.

Restricted Mode for customer administration

This new feature enables you to restrict the user features that are available to your customers' administrators in Control Hub, so those administrators will not be able to change user packages or add new users. This is intended to both support your role as the primary administrator to your customers, as well as keep your customers' package and billing information in sync with your BroadWorks systems.

First version subscriber packages

We defined the Basic, Standard, and Premium packages, with different features as follows:

Package

Calling

Messaging

Space Meetings

PMR Meetings

Basic

Included

Included

3 participants

Standard

Included

Included

25 participants

25 participants

Premium

Included

Included

25 participants

1000 participants

Partner Hub features for integrating BroadWorks with Webex

When we bring you on board with the Webex for BroadWorks offer, you nominate your first administrator. We create your partner organization, apply the relevant entitlements, and invite your administrator to sign in to Partner Hub. They can create other administrators as necessary.

Your partner administrator then configures your organization, with one or more “Clusters” that contain interfaces for your XSPs, and one or more “Templates” that control how customers and subscribers are provisioned.

Provisioning subscribers with trusted emails (Flow-through provisioning)


Webex requires unique, valid email addresses for user login identities. This option requires that your subscribers have such email addresses in BroadWorks, and that you trust the addresses to be valid and unique.

When you assign the Integrated IM&P service to a subscriber in BroadWorks, the Application Server calls our provisioning API to create a corresponding user in Webex. If the email domain is known to Webex, it adds the user to that existing organization.

If the user’s email domain is not yet known to Webex, Webex creates a new customer organization and makes that first user an administrator of that organization.

Both customer organizations and your partner organization are managed through Partner Hub.

First version of backwards-compatible provisioning API

We designed the subscriber provisioning API to be compatible with the calls made by Application Server, so that the new provisioning target does not require new functionality on Application Server.

If you want to create or augment your provisioning applications, there are additional APIs for subscriber management beyond what is possible from AS.

Notification Push Server authentication proxy

We designed a new NPS authentication model to reflect our strong focus on security. We now provide a proxy where your NPS authenticates to get authorization tokens. It uses these tokens to push notifications to APNS/FCM. The new model is more secure and simplifies the administration of push notifications on your XSP.

Device Management configuration templates for Webex clients

We provide template configuration files for you to apply to BroadWorks and configure for your SIP environment. Webex apps download their configuration via Device Management Service, so that they can register to BroadWorks and start making calls.