Webex for BroadWorks Reference

UC-One SaaS Comparison with Webex for BroadWorks

Solution >

UC-One SaaS

Webex for BroadWorks

Cloud

Cisco UC-One Cloud (GCP)

Cisco Webex cloud (AWS)

Clients

UC-One: Mobile, Desktop

Receptionist, Supervisor

Teams: Mobile, Desktop, Web

Major Technology Difference

Meetings delivered on Broadsoft Meet Technology

Meetings delivered on Webex Meetings Technology

Early Field Trials

Staging environment, Beta clients

Production environment, GA clients

User identity

BroadWorks ID served as primary ID, unless Service Provider has SSO Integration already.

 

User ID and secret in BroadWorks

Email ID in Cisco CI serves as primary ID

SSO integration into Service Provider BroadWorks where User will authenticate with BroadWorks User ID and BroadWorks secret at time.

 

User supplies credentials via SSO with BroadWorks and secret in BroadWorks

OR

User ID and secret in CI IdP

OR

User ID in CI, ID and secrets in IdP

Client authentication

Users supply credentials through client

BroadWorks long-lived tokens required if using Teams messaging

Users supply credentials via browser (either login page from Webex BIdP proxy or CI)

Webex access and refresh tokens

Management / configuration

Your OSS/BSS systems and

Reseller portal

Your OSS/BSS systems and Control Hub

Partner/Service Provider activation

One time setup by Cisco Operations

One time setup by Cisco Operations

Customer/enterprise activation

Reseller portal

Control Hub

Auto-created upon first user enrollment

User activation options

Self-enrolled

Set external IM&P in BroadWorks

Set Integrated IM&P in BroadWorks (typically enterprises)

XSP service interfaces

XSI-Actions

 

XSI-Events

CTI (mTLS)

AuthService (mTLS optional)

DMS

XSI-Actions

XSI-Actions (mTLS)

XSI-Events

CTI (mTLS)

AuthService (mTLS required)

DMS

Install Webex Teams and Sign In (Subscriber Perspective)

1

Download and install Webex Teams. For details, see Webex Teams | Download the App.

2

Run Teams.

Teams prompts you for your email address.
3

Enter your email address and click Next.

4

One of the following happens, depending on the way your organization is configured in Webex:

  1. Teams launches a browser for you to complete authentication with your identity provider. This could be multi-factor authentication (MFA).

  2. Teams launches a browser for you to enter your BroadWorks user ID and password.

Teams loads after you successfully authenticate against the IdP or BroadWorks.

Data Exchange and Storage

These sections provide detail on data exchange and storage with Cisco Webex. All data is encrypted both in transit and at rest. For additional details, see Cisco Webex Teams App Security.

Service Provider Onboarding

When you configure clusters and user templates in Cisco Webex Control Hub during Service Provider onboarding, you exchange the following BroadWorks data which Webex stores:

  • Xsi-Actions URL

  • Xsi-Actions mTLS URL

  • Xsi-Events URL

  • CTI interface URL

  • Authentication service URL

  • BroadWorks Provisioning Adaptor credentials

Service Provider User Provisioning

This table lists user and enterprise data that is exchanged as part of user provisioning through the Webex APIs.

Data Moving to Webex

From

Through

Stored by Webex?

BroadWorks UserID

BroadWorks

Webex APIs

Yes

Email (if SP Provided)

BroadWorks

Webex APIs

Yes

Email (if User Provided)

User

User Activation Portal

Yes

First name

BroadWorks

Webex APIs

Yes

Last name

BroadWorks

Webex APIs

Yes

Primary Phone Number

BroadWorks

Webex APIs

Yes

Mobile Phone Number

BroadWorks

Webex APIs

No

Primary Extension

BroadWorks, by API

Webex APIs

No

BroadWorks Service Provider ID & Group ID

BroadWorks, by API

Webex APIs

Yes

Language

BroadWorks, by API

Webex APIs

Yes

Time zone

BroadWorks, by API

Webex APIs

Yes

User Removal

Webex for BroadWorks APIs support both partial and full user removal. This table lists all user data that is stored during provisioning and what is deleted in each scenario.

User Data

Partial Deletion

Full Deletion

BroadWorks UserID

Yes

Yes

Email

No

Yes

First name

No

Yes

Last name

No

Yes

Primary Phone Number

Yes

Yes

BroadWorks Service Provider ID & Group ID

Yes

Yes

Language

No

Yes

User Login and Configuration Retrieval

Webex Authentication

Webex authentication refers to user sign-in to a Webex Teams client by any of the Cisco Webex support authentication mechanisms. (BroadWorks authentication is covered separately.) This table illustrates the type of data exchanged between the different components on the authentication flow.

Data Moving

From

To

Email address

User through Teams client

Webex

Limited access token and (independent) IdP URL

Webex

User browser

User credentials

User browser

Identity provider (which already has user identity)

SAML assertion

User browser

Webex

Authentication code

Webex

User browser

Authentication code

User browser

Webex

Access and Refresh tokens

Webex

User browser

Access and Refresh tokens

User browser

Teams client

BroadWorks Authentication

BroadWorks authentication refers to user sign-in to a Webex Teams client using their BroadWorks credentials. This table illustrates the type of data exchanged between the different components on the authentication flow.

Data Moving

From

To

Email address

User through Teams client

Webex

Limited access token and (Webex Bwks IdP proxy) IdP URL

Webex

User browser

Branding information and BroadWorks URLs

Webex

User browser

BroadWorks user credentials

User through browser (branded sign-in page served by Webex)

Webex

BroadWorks user credentials

Webex

BroadWorks

BroadWorks user profile

BroadWorks

Webex

SAML assertion

User browser

Webex

Authentication code

Webex

User browser

Authentication code

User browser

Webex

Access and Refresh tokens

Webex

User browser

Access and Refresh tokens

User browser

Teams client

Client Configuration Retrieval

This table illustrates the type of data exchanged between the different components while retrieving client configurations.

Data Moving

From

To

Registration

Client

Webex

Organization settings, including BroadWorks URLs

Webex

Client

BroadWorks JWT token

BroadWorks through Webex

Client

BroadWorks JWT token

Client

BroadWorks

Device Token

BroadWorks

Client

Device Token

Client

BroadWorks

Config file

BroadWorks

Client

Steady State Usage

This section describes the data moving between components during re-authentication after token expiry, either through BroadWorks or Webex.

This table lists data movement for calling.

Data Moving

From

To

SIP signalling

Client

BroadWorks

SRTP media

Client

BroadWorks

SIP signalling

BroadWorks

Client

SRTP media

BroadWorks

Client

This table lists data movement for messaging, presence, and meetings.

Data Moving

From

To

HTTPS REST messaging and presence

Client

Webex

HTTPS REST messaging and presence

Webex

Client

SIP signalling

Client

Webex

SRTP media

Client

Webex

SIP signalling

Webex

Client

SRTP media

Webex

Client

Using the Provisioning API

The Webex for BroadWorks Provisioning API is for BroadWorks Service Providers (SPs) who sign up for Cisco Webex for BroadWorks. The API enables those SPs to provision, update, and remove Cisco Webex services for their subscribers.

Developer Access

The API specification is available on https://developer.webex.com to developers to whom we have explicitly given access. Contact your Cisco Administrator to gain access to these API specifications.

Application Authentication and Authorization

Your application integrates with Cisco Webex as an Integration. This mechanism allows the application to perform administrative tasks (such as subscriber provisioning) for an administrator within your Partner organization.

Cisco Webex APIs follow the OAuth 2 standard (http://oauth.net/2/). OAuth 2 allows third-party integrations to obtain refresh and access tokens on behalf of your chosen Partner administrator for authenticating API calls.

You must first register your integration with Cisco Webex. Once registered, your application must then support this OAuth 2.0 authorization grant flow to obtain the necessary refresh and access tokens.

For more details on integrations and how to build this OAuth 2 authorization flow into your application, see https://developer.webex.com/docs/integrations.

Methods and Content Types

The Webex for BroadWorks Provisioning API is RESTful. In REST, a base URL represents each resource. You use the HTTP methods GET, POST, PUT, and DELETE to request data and perform actions on those resources.

For methods that accept request parameters, the platform accepts only application/json content types.

API Errors

This API returns standard HTTP status codes for request responses. If an error occurs, the response body provides more information.

Important Implementation Notes

OAuth Scopes

When registering your application as an Integration on https://developer.webex.com, enable the following scopes to access all Webex for BroadWorks Provisioning APIs:

  • spark-admin:broadworks_subscribers_write

  • spark-admin:broadworks_subscribers_read

  • spark-admin:broadworks_enterprises_read

Asynchronous Provisioning Model

Subscriber provisioning on Cisco Webex can take considerable time. Therefore, the Webex for BroadWorks provisioning APIs don’t wait or block until subscriber is fully provisioned. Instead, the API responds quickly while initiating subscriber provisioning as a background task.

You can design your application to query the subscriber later to determine its provisioning status. All representations of the subscriber through the APIs include a “status” attribute to indicate the subscriber’s provisioning status:

  • On successful completion, the subscriber status changes to “provisioned”.

  • If any error occurs during provisioning, the user status transitions to “error”. The subscriber representation through these APIs also includes specific error codes and the reasons behind the provisioning error.

Enterprise ID

When provisioning a BroadWorks subscriber for Webex for BroadWorks, one of the required parameters is the spEnterpriseId. This parameter defines as a unique identifier for subscriber's enterprise on BroadWorks.

This table defines how to supply the spEnterpriseId value for your model:

Enterprise Configuration Model

Description

Logic

Example enterpriseID

Service Provider Model

Individual customers are configured as Groups under a Service Provider on BroadWorks.

The spEnterpriseId must be a concatenation of Service Provider ID and Group ID on BroadWorks, separated by a plus, as follows:

"<Service Provider ID>" + "+" + "<Group ID>"

“SP1+Acme"

Enterprise Model

Individual customers are configured as Enterprises on BroadWorks.

The spEnterpriseId must be an exact match of the Enterprise ID on BroadWorks:

"<Enterprise ID>"

“Acme”

Avoid Refresh Token Expiry

If a Refresh Token expires, then the application can no longer generate the necessary access tokens for this API. A Service Provider admin needs to reauthorize the application to gain access to the APIs again. So, it's important that your application maintains an active Refresh Token.

Generating a new access token automatically renews the lifetime of your Refresh Token. An application that regularly makes requests to this API also generates new access tokens. By its nature, the application also renews its Refresh Token lifetime. However, if the application becomes inactive for a long time, then the Refresh Token can expire. (Refresh token expiry is 60 days.) We recommend that your application runs a scheduled task/job that generates a new access token using the Refresh Token. This technique ensures that the Refresh Token doesn't expire, even during periods of inactivity.

Subscriber Deletion

Webex for APIs supports both a soft and hard deletion model for subscribers.

  • Soft Delete—The Webex for BroadWorks Subscriber Delete API removes all entitlements and capabilities from when the subscriber was first provisioned for Webex for BroadWorks. But, the subscriber remains provisioned within their Customer organization on Cisco Webex. The subscriber may continue to use Webex Teams in line with their remaining capabilities.

  • Hard Delete—If you wish to remove the subscriber completely from Cisco Webex, perform a DELETE with the People APIs as documented at https://developer.webex.com/docs/api/v1/people.

BroadWorks Software Requirements

See Lifecycle Management - BroadSoft Servers.

We expect the Service Provider to be on the current patch. The list of patches below is the minimum requirement for integrating with Webex.

Version 21 SP1 (Minimum supported version)

Server

Patches required

Application Server

AP.as.21.sp1.551.ap233913

AP.as.21.sp1.551.ap342028

AP.as.21.sp1.551.ap343504

AP.as.21.sp1.551.ap343572

AP.as.21.sp1.551.ap343670

AP.as.21.sp1.551.ap343760

AP.as.21.sp1.551.ap343918

AP.as.21.sp1.551.ap346337

AP.as.21.sp1.551.ap358508

AP.as.21.sp1.551.ap369763

Platform

AP.platform.21.sp1.551.ap233913

AP.platform.21.sp1.551.ap346337

AP.platform.21.sp1.551.ap347534

AP.platform.21.sp1.551.ap348531

AP.platform.21.sp1.551.ap355855

AP.platform.21.sp1.551.ap358508

AP.platform.21.sp1.551.ap364243

AP.platform.21.sp1.551.ap367732

AP.platform.21.sp1.551.ap361945

AP.platform.21.sp1.551.ap364239

Profile Server

AP.ps.21.sp1.551.ap233913

Execution Server

AP.xs.21.sp1.551.ap233913

XSP

AP.xsp.21.sp1.551.ap233913

AP.xsp.21.sp1.551.ap338964

AP.xsp.21.sp1.551.ap338965

AP.xsp.21.sp1.551.ap339087

AP.xsp.21.sp1.551.ap346337

AP.xsp.21.sp1.551.ap347534

AP.xsp.21.sp1.551.ap347879

AP.xsp.21.sp1.551.ap348531

AP.xsp.21.sp1.551.ap348574

AP.xsp.21.sp1.551.ap348987

AP.xsp.21.sp1.551.ap349230

AP.xsp.21.sp1.551.ap349443

AP.xsp.21.sp1.551.ap349923

AP.xsp.21.sp1.551.ap350396

AP.xsp.21.sp1.551.ap350524

AP.xsp.21.sp1.551.ap351040

AP.xsp.21.sp1.551.ap352340

AP.xsp.21.sp1.551.ap358508

AP.xsp.21.sp1.551.ap362075

Version 22

Server

Required Patches

Application Server

AP.as.22.0.1123.ap364260

AP.as.22.0.1123.ap365173

AP.as.22.0.1123.ap369763

AP.as.22.0.1123.ap372989

AP.as.22.0.1123.ap372757

Profile Server

AP.ps.22.0.1123.ap372989

AP.ps.22.0.1123.ap372757

Platform

AP.platform.22.0.1123.ap353577

AP.platform.22.0.1123.ap354313

AP.platform.22.0.1123.ap365173

AP.platform.22.0.1123.ap367732

AP.platform.22.0.1123.ap369433

AP.platform.22.0.1123.ap369607

AP.platform.22.0.1123.ap372757

XSP

AP.xsp.22.0.1123.ap354313

AP.xsp.22.0.1123.ap365173

AP.xsp.22.0.1123.ap368067

AP.xsp.22.0.1123.ap370952

AP.xsp.22.0.1123.ap369607

AP.xsp.22.0.1123.ap373008

AP.xsp.22.0.1123.ap372757

AP.xsp.22.0.1123.ap372433

AP.xsp.22.0.1123.ap374677

AP.xsp.22.0.1123.ap375206

Other

AP.xsa.22.0.1123.ap372757

AP.xs.22.0.1123.ap372757

Version 23

Server

Required Patches

Application Server

AP.as.23.0.1075.ap369763

Platform

AP.platform.23.0.1075.ap367732

AP.platform.23.0.1075.ap370952

AP.platform.23.0.1075.ap369607

XSP

AP.xsp.23.0.1075.ap368067

AP.xsp.23.0.1075.ap370952

AP.xsp.23.0.1075.ap369607

AP.xsp.23.0.1075.ap373008

AP.xsp.23.0.1075.ap374677

AP.xsp.23.0.1075.ap375206

BroadWorks Tags Required for Webex Teams

System Tags

System Tag

Description

%BWNETWORK-CONFERENCESIPURI-1%

This is the server URI used to enable N-Way conferencing.

%BWVOICE-PORTAL-NUMBER-1%

This number is used for voice mail. The client dials this number when retrieving voice mail.

%BWLINEPORT-1%

SIP username used in SIP signaling, for example, in registration.

%BWAUTHPASSWORD-1%

SIP password used in SIP signaling.

%BWHOST-1%

Typically used as the SIP domain.

%BWAUTHUSER-1%

SIP username typically used in 401 and 407 signaling. Can be different from the default SIP username.

%BWE164-1%

This tag provides the user’s phone number in international format.

Custom Tags

Tag

Desktop

Mobile

Default

%ENABLE_CALL_STATISTICS_WXT%

Y

Y

FALSE

%ENABLE_CALL_PULL_WXT%

Y

Y

FALSE

%PN_FOR_CALLS_CONNECT_SIP_ON_ACCEPT_WXT%

N

Y

FALSE

%PN_FOR_CALLS_USE_REGISTRATION_V1_WXT%

N

Y

FALSE

%ENABLE_MWI_WXT%

Y

Y

FALSE

%MWI_MODE_WXT%

Y

Y

empty

%ENABLE_VOICE_MAIL_WXT%

Y

Y

FALSE

%ENABLE_VISUAL_VOICE_MAIL_WXT%

Y

Y

FALSE

%ENABLE_FORCED_LOGOUT_WXT%

Y

N

FALSE

%FORCED_LOGOUT_APPID_WXT%

Y

N

empty

%ENABLE_CALL_FORWARDING_ALWAYS_WXT%

Y

Y

FALSE

%ENABLE_BROADWORKS_ANYWHERE_WXT%

Y

Y

FALSE

%ENABLE_BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_WXT%

Y

Y

FALSE

%BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_DEFAULT_WXT%

Y

Y

FALSE

%ENABLE_BROADWORKS_ANYWHERE_DESCRIPTION_WXT%

Y

Y

TRUE

%ENABLE_BROADWORKS_ANYWHERE_CALL_CONTROL_WXT%

Y

Y

FALSE

%BROADWORKS_ANYWHERE_CALL_CONTROL_DEFAULT_WXT%

Y

Y

FALSE

%ENABLE_BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_WXT%

Y

Y

FALSE

%BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_DEFAULT_WXT%

Y

Y

FALSE

%ENABLE_BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_WXT%

Y

Y

FALSE

%BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_DEFAULT_WXT%

Y

Y

FALSE

%SETTINGS_PORTAL_URL_WXT%

Y

Y

empty

%ENABLE_EMERGENCY_DIALING_WXT%

N

Y

FALSE

%EMERGENCY_DIALING_NUMBERS_WXT%

N

Y

911,112

%ENABLE_USE_RPORT_WXT%

Y

Y

FALSE

%RPORT_USE_LOCAL_PORT_WXT%

Y

Y

FALSE

%USE_TLS_WXT%

Y

Y

FALSE

%SBC_ADDRESS_WXT%

Y

Y

empty

%SBC_PORT_WXT%

Y

Y

5060

%USE_PROXY_DISCOVERY_WXT%

Y

Y

FALSE

%USE_TCP_FROM_DNS_WXT%

Y

Y

TRUE

%USE_UDP_FROM_DNS_WXT%

Y

Y

TRUE

%USE_TLS_FROM_DNS_WXT%

Y

Y

TRUE

%DOMAIN_OVERRIDE_WXT%

Y

Y

empty

%SOURCE_PORT_WXT%

Y

Y

5060

%USE_ALTERNATIVE_IDENTITIES_WXT%

Y

Y

FALSE

%TCP_SIZE_THRESHOLD_WXT%

Y

Y

18000

%SIP_REFRESH_ON_TTL_WXT%

Y

Y

FALSE

%ENABLE_SIP_UPDATE_SUPPORT_WXT%

Y

Y

FALSE

%ENABLE_PEM_SUPPORT_WXT%

Y

Y

FALSE

%ENABLE_SIP_SESSION_ID_WXT%

Y

Y

FALSE

%ENABLE_FORCE_SIP_INFO_FIR_WXT%

Y

Y

FALSE

%SRTP_ENABLED_WXT%

Y

Y

FALSE

%SRTP_MODE_WXT%

Y

Y

FALSE

%ENABLE_REKEYING_WXT%

Y

Y

TRUE

%RTP_AUDIO_PORT_RANGE_START_WXT%

Y

Y

8000

%RTP_AUDIO_PORT_RANGE_END_WXT%

Y

Y

8099

%RTP_VIDEO_PORT_RANGE_START_WXT%

Y

Y

8100

%RTP_VIDEO_PORT_RANGE_END_WXT%

Y

Y

8199

%ENABLE_RTCP_MUX_WXT%

Y

Y

TRUE

%ENABLE_XSI_EVENT_CHANNEL_WXT%

Y

Y

TRUE

%CHANNEL_HEARTBEAT_WXT%

Y

Y

10000

User Provisioning and Activation Flows


Provisioning describes adding the user to Webex. Activation includes email validation and service assignment in Webex.

Users email addresses must be unique as Webex uses the email address to identify a user. If you have trusted email addresses for the users, you can choose to have them automatically activated when you automatically provision them. This process is “automatic provisioning and automatic activation”.

Automated User Provisioning and Automatic Activation (Trusted Email Flow)

Prerequisites

  • Your provisioning adapter points to Webex for BroadWorks (which requires an outbound connection from AS to Webex Provisioning Bridge).

  • You must have valid reachable end-user email addresses as alternate IDs in BroadWorks.

  • Control Hub has a provisioning account in your partner organization configuration.

Figure 1.

This image is not available in preview/cisco.com

Step

Description

1

You quote and take orders for the service with your customers.

2

You process the customer order and provision the customer in your systems.

3

The service provisioning system triggers the provisioning of BroadWorks. This step, in summary, creates the enterprise and the users. It then assigns the necessary services and numbers to each user. One of those services is the external IM&P.

4

This provisioning step triggers the automatic provisioning of the customer organization and users in Cisco Webex. (The IM&P service assignment causes the provisioning adapter to call the Webex provisioning API).

5

Your systems need to use the Webex provisioning API if you later need to adjust the package for the user (to change from the default).

User Interactions

Sign In

Figure 2.
  1. The Webex Teams client launches a browser to Cisco Common Identity (CI) to allow users to enter their email address.

  2. CI discovers that the associated customer org has the BroadWorks IDP Proxy (IDP) configured as their SAML IDP. CI redirects to the IDP which presents the user with a sign-in page. (The Service Provider can brand this sign-in page.)

  3. The user enters their BroadWorks credentials.

  4. Broadworks authenticates the user through the IDP. On success, the IDP redirects the browser back to CI with a SAML Success to complete the authentication flow (not shown in diagram).

  5. On successful authentication, the Webex Teams client obtains access tokens from CI (not shown in diagram). The client uses them to request a BroadWorks long-lived Jason Web Token (JWT).

  6. Teams discovers its calling configuration from BroadWorks and other services from Webex.

  7. Teams registers with BroadWorks.

Sign In from a User Perspective

This diagram is the typical sign-in flow, as seen by the end user or subscriber:

Figure 3.
  1. You download and install the Webex Teams client.

  2. You may have received the link from your service provider, or you can find the download on Cisco Webex downloads page.

  3. You enter your email address at the Teams sign-in screen. Click Next.

  4. Typically, you’re redirected to a Service Provider branded page.

  5. That page may welcome you by your email address.

    If there’s no email address, or if the email address is wrong, enter your BroadWorks user name instead.

  6. Enter your BroadWorks password.

  7. Teams opens if you signed in successfully.

Call Flow—Corporate Directory

Figure 4.

Call Flow—PSTN Number

Figure 5.

Presentation and Sharing

Figure 6.

Start a Space Meeting

Figure 7.

Client Interactions

Retrieve Profile from DMS and SIP Register with AS

  1. Client calls XSI to get a device management token and the URL to the DMS.

  2. Client requests its device profile from DMS by presenting the token from step 1.

  3. Client reads the device profile and retrieves the SIP credentials, addresses, and ports.

  4. Client sends a SIP REGISTER to SBC using the information from step 3.

  5. SBC sends the SIP REGISTER to the AS (SBC may perform a look-up in the NS to locate an AS if SBC does not already know the SIP user.)

Terminology

ACL
Access Control List
ALG
Application Layer Gateway
API
Application Programming Interface
APNS
Apple Push Notification Service
AS
Application Server
ATA
Analog Telephone Adapter, adapter that converts analog telephony to VoIP
BAM
BroadSoft Application Manager
Basic authentication
A method of authentication where an account (username) is validated by a shared secret (password)
BMS
BroadSoft Messaging Server
BOSH
Bidirectional-streams Over Synchronous HTTP
BRI
Basic Rate Interface BRI is an ISDN access method
Bundle
A collection of services as delivered to an end user or subscriber (cf. Package)
CA
Certification Authority
Carrier
An organization that handles telephony traffic (cf. Partner, Service Provider, Value Added Reseller)
CAPTCHA
Completely Automated Public Turing test to tell Computers and Humans Apart
CCXML
Call Control eXtensible Markup Language
CIF
Common Intermediate Format
CLI
Command Line Interface
CN
Common Name
CNPS
Call Notifications Push Server. A Notification Push Server that runs on an XSP in your environment, to push call notifications to FCM and APNS. See NPS Proxy.
CPE
Customer Premises Equipment
CPR
Custom Presence Rule
CSS
Cascading Style Sheet
CSV
Comma-Separated Value
CTI
Computer Telephony Integration
CUBE
Cisco Unified Border Element
DMZ
Demilitarized Zone
DN
Directory Number
DND
Do Not Disturb
DNS
Domain Name System
DPG
Dial Peer Group
DSCP
Differentiated Services Code Point
DTAF
Device Type Archive File
DTG
Destination Trunk Group
DTMF
Dual-Tone Multi-Frequency
End user
The person who is using the services, that is making calls, joining meetings, or sending messages (cf. Subscriber)
Enterprise
A collection of end users (cf. Organization)
FCM
Firebase Cloud Messaging
FMC
Fixed Mobile Convergence
Flow-through provisioning
Creating users in the Webex identity store by assigning the “Integrated IM&P” service in BroadWorks.
FQDN
Fully Qualified Domain Name
Full flow-through provisioning
Creating and verifying users in the Webex identity store by assigning the “Integrated IM&P” service in BroadWorks and asserting that each BroadWorks user has a unique and valid email address.
FXO
Foreign Exchange Office is the port that receives the analog line. It is the plug on the phone or fax machine or the plugs on your analog phone system. It delivers an on-hook/off-hook indication (loop closure). Since the FXO port is attached to a device, such as a fax or a phone, the device is often called the “FXO device”.
FXS
Foreign Exchange Subscriber is the port that actually delivers the analog line to the subscriber. In other words, it is the "plug in the wall" that delivers a dial tone, battery current, and ring voltage.
GCM
Google Cloud Message
GCM
Galois/Counter Mode (encryption technology)
HID
Human Interface Device
HTTPS
Hypertext Transfer Protocol Secure Sockets
IAD
Integrated Access Device
IM&P
Instant Messaging and Presence
IP PSTN
A service provider that provides VoIP to PSTN services, interchangeable with ITSP, or a general term for internet-connected 'public' telephony, collectively provided by major telecomms providers (rather than by countries, as PSTN is)
ITSP
Internet Telephony Service Provider
IVR
Interactive Voice Response / Responder
JID
The native address of an XMPP entity is called a Jabber Identifier or JID localpart@domain.part.example.com/resourcepart (@ . / are separators)
JSON
Java Script Object Notation
JSSE
Java Secure Socket Extension; the underlying technology providing secure connectivity features to BroadWorks servers
KEM
Key Extension Module (hardware Cisco phones)
LLT
Long-lived (or Long Life) Token; a self-describing, secure form of bearer token that enables users to remain authenticated for longer, and is not tied to specific applications.
MA
Message Archival
MIB
Management Information Base
MS
Media Server
mTLS
Mutual authentication between two parties, using certificate exchange, when establishing a TLS connection
MUC
Multi-User Chat
NAT
Network Address Translations
NPS
Notification Push Server; see CNPS
NPS Proxy

A service in Cisco Webex that supplies short-lived authorization tokens to your CNPS, enabling it to push call notifications to FCM and APNs, and ultimately to Android and iOS devices running Webex Teams.

OCI
Open Client Interface
Organization
A company or organization representing a collection of end users (cf. Enterprise)
OTG
Outgoing Trunk Group
Package
A collection of services as delivered to an end user or subscriber (cf. Bundle)
Partner
An agent organization that works with Cisco to distribute products and services to other organizations (cf. Value Added Reseller, Service Provider, Carrier)
PBX
Private Branch Exchange
PEM
Privacy Enhanced Mail
PLMN
Public Land Mobile Network
PRI
Primary Rate Interface (PRI) is a telecommunications interface standard used on an Integrated Services Digital Network (ISDN)
PS
Profile Server
PSTN
Public Switched Telephone Network
QoS
Quality of Service
Reseller portal
A web site that enables the reseller’s administrator to configure their UC-One SaaS solution. It is sometimes referred to as BAM portal, admin portal, or management portal.
RTCP
Real-Time Control Protocol
RTP
Real-Time Transport Protocol
SBC
Session Border Controller
SCA
Shared Call Appearance
SD
Standard Definition
SDP
Session Description Protocol
SP
Service Provider; An organization that provides telephony or related services to other organizations (cf. Carrier, Partner, Value Added Reseller)
SIP
Session Initiation Protocol
SLT
Short-lived (or Short Life) Token (also called BroadWorks SSO Token); a single-use authenticated token that is used to gain secure access to web applications.
SMB
Small to Medium Business
SNMP
Simple Network Management Protocol
sRTCP
secure Realtime Transfer Control Protocol (VoIP call media)
sRTP
secure Realtime Transfer Protocol (VoIP call media)
SSL
Secure Sockets Layer
Subscriber
The person who is using the services, that is making calls, joining meetings, or sending messages (cf. End user)
TCP
Transmission Control Protocol
TDM
Time Division Multiplexing
TLS
Transport Layer Security
ToS
Type of Service
UAP
User Activation Portal
UC
Unified Communications
UI
User Interface
UID
Unique Identifier
UMS
Messaging Server
URI
Uniform Resource Identifier
URL
Uniform Resource Locator
USS
Sharing Server
UTC
Coordinated Universal Time
UVS
Video Server
Value Added Reseller (VAR)
An agent organization that works with Cisco to distribute products and services to other organizations (cf. Carrier, Partner, Service Provider)
VGA
Video Graphics Array
VoIP
Voice over Internet Protocol (IP)
VXML
Voice Extensible Markup Language
WebDAV
Web Distributed Authoring and Versioning
WebRTC
Web Real-Time Communications
WRS
WebRTC Server
XMPP
Extensible Messaging and Presence Protocol