UC-One SaaS Comparison with Webex for Cisco BroadWorks
Solution > |
UC-One SaaS |
Webex for Cisco BroadWorks |
---|---|---|
Cloud |
Cisco UC-One Cloud (GCP) |
Webex Cloud (AWS) |
Clients |
UC-One: Mobile, Desktop Receptionist, Supervisor |
Webex: 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 Webex 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 (TLS) DMS |