- Start
- /
- Artikel
Guide för enhetsintegrering för Webex för Cisco BroadWorks
I den här artikelnSyftet med enhetsintegreringsguiden är att göra administratörer på partnernivå. I dokumentet beskrivs hur du distribuerar och hanterar enheter med den här lösningen.
Inledning
Om den här guiden
Det här dokumentet är avsett för partneradministratörer hos tjänsteleverantörsorganisationer som distribuerar Webex för Cisco BroadWorks. I guiden beskrivs hur man ska registrera sig och använda Rums-OS och MPP-enheter för Webex för Cisco BroadWorks. Guiden är uppdelad i två kapitel:
- Enhetsregistrering – beskriver hur du registrerar Room OS-enheter (Room- och Room Kit-serien, Desk-serien och Board-serien) och MPP-enheter i Webex för Cisco Broad Works.
- Enhetsservicehantering – beskriver hur du hanterar registrerade enheter i Control Hub.
Ändringshistorik för dokument
Följande tabell sammanfattar ändringshistoriken för det här dokumentet.
|
Datum |
Dokumentversion |
Beskrivning av ändring |
|---|---|---|
|
12 maj 2023 |
1.7 | Förbättringar av Webex för BroadWorks integrerade Cisco Room -enheter och katalogsökning för W4B integrerade Room OS-enheter har lagts till under avsnittet Slutanvändarfunktioner för Webex integrerade enheter. |
|
27 februari 2023 |
1.6 | Uppdaterade steg för Konfigurera tjänster för Room OS under Enhetsregistrering. |
|
17 februari 2023 |
1.5 | Lade till avsnittet Unified Call History för Webex-medvetna MPP-telefoner under Slutanvändarfunktioner för Webex-integrerade enheter. |
|
14 oktober 2022 |
1.4 |
|
|
20 juni 2022 |
1.3 |
|
|
03 juni 2022 |
1.2 |
|
|
27 maj, 2022 |
1.1 |
|
|
20:e maj, 2022 |
1.0 |
|
Enhetsintegrering för Webex för Cisco BroadWorks
Device Onboarding Overview
This chapter describes how to onboard devices to Webex for Cisco BroadWorks. This chapter covers the following use cases:
-
Onboard new Webex Room OS devices (using activation codes)
-
Onboard new MPP devices
-
Add Webex capability to existing MPP devices
-
We recommended that you deploy this feature on Release Independent ADP servers. However, XSP also supports this feature. If you're using XSP, then where this document refers to "ADP", you can substitute "XSP", unless the text specifies ADP only.
-
This feature supports both Personal and Workspace devices.
Room OS Onboarding
Webex for Cisco BroadWorks supports activation code onboarding for both shared and workspace Room OS devices.
Device Onboarding with Activation Codes
Device Onboarding with activation codes provides a simple and secure way to onboard Room OS devices. An activation code is a 16-digit one-time system-generated passcode that a user must input on a device to onboard the device. The activation code is securely linked to the intended user account and assures that only the intended user onboards a device linked to the same account. After the user enters the correct code, the device connects to both Webex and BroadWorks, completes registration, downloads its configuration file, and is ready to use.
The following Room OS devices support onboarding with activation codes:
-
Webex Board Series (Room OS)
-
Webex Desk Series (Room OS)
-
Webex Room Series (Room OS)
Onboarding Process for Room OS
The following process shows what happens when a Room OS device onboards using activation codes:
-
The partner administrator provisions the primary user and device in BroadWorks and then generates the activation code in BroadWorks.
-
An email that contains the device activation code is sent to the device owner.
-
The device owner starts the device.
-
The device prompts the device owner to enter the activation code.
-
The device owner enters the activation code on the device.
-
The device onboards to BroadWorks and Webex using the following subprocess:
-
The Room OS device sends an activation request to Webex services. The activation code gets validated by GDS and if the code is correct, the device onboards to Webex. Webex returns a machine token to the device.
-
The device sends an activation request to the BroadWorks DM along with the machine token and MAC address.
-
BroadWorks authorizes and onboards the device.
-
The device sends a request to the BroadWorks DM for an updated config. The machine token is included for authorization.
-
BroadWorks authorizes the token, locates the updated config file, and returns an updated configuration file.
-
Room OS will attempt to locate a NAPTR record for the domain specified in the configuration file as it expects to find an SRV entry for _sip._tls.<domain_in_config> if no NAPTR record is present then RoomOS will then try and look for an SRV record followed by an A record respectively.
The SRV record must be _sip._tls. as roomOS will only support TLS for transport and SRTP for media.
-
-
The device registers and is ready to use.
The following diagram provides a simplified overview of the onboarding process.
For detailed information on Room OS onboarding, including more detailed flow diagrams, see the feature description Cisco BroadWorks Enhancements for Webex-Aware Device Onboarding.
Device Authentication (via OAuth Bearer Tokens)
Device authentication for Room OS devices requires that you enable Cisco OAuth Bearer Tokens on BroadWorks. During onboarding, the bearer token gets passed via the Activate Authorization header and serves to identify the device. The IdP validates the bearer token and returns the UUID (a machine UUID for workspace devices or user UUID for personal devices) as bearer subject. BroadWorks saves the UUID as the device name in the Network Server.
Room OS Prerequisites
Minimum Room OS Version
Room OS 10.13 minimum
BroadWorks Patch Requirements
This feature is supported as of version 2021.11 of the Release Independent (RI) ADP server with no patch requirements.
For non-RI servers, you must have installed the following patches (from patch groups ap381367, ap381951, ap382198) in order to use the feature. Install the patches that apply to your release:
För R22:
-
AP.as.22.0.1123.ap381367
-
AP.as.22.0.1123.ap382236
-
AP.nfm.22.0.1123.ap381367
-
AP.ns.22.0.1123.ap381367
-
AP.platform.22.0.1123.ap381367
-
AP.platform.22.0.1123.ap382198
-
AP.ps.22.0.1123.ap381367
-
AP.xsp.22.0.1123.ap381367
-
AP.xsp.22.0.1123.ap382198
För R23:
-
AP.as.23.0.1075.ap381367
-
AP.as.23.0.1075.ap382236
-
AP.ns.23.0.1075.ap381367
-
AP.platform.23.0.1075.ap382198
-
AP.platform.23.0.1075.ap381367
-
AP.xsp.23.0.1075.ap381367
-
AP.xsp.23.0.1075.ap382198
-
AP.ps.23.0.1075.ap381367
För R24:
-
AP.as.24.0.944.ap381367
-
AP.as.24.0.944.ap381951
-
AP.as.24.0.944.ap382236
BroadWorks Platform Requirements
This feature is available on:
-
R22: available on XSP only
-
R23: available on XSP or ADP (Release Independent)
-
R24: available on ADP (Release Independent)
BroadWorks Configuration Requirements
-
To implement this solution, the Flowthrough provisioning must be configured to allow Broadworks to provision devices to Webex.
While configuring the Flowthrough provisioning, it’s not mandatory to use flowthrough provisioning to provision users i.e., you can continue to use your existing provisioning methods (API, Trusted/Untrusted Email, User self, etc.) to provision users. See "Provisioning Requirements" in the Webex for Cisco BroadWorks Solution Guide.
-
Make sure that the Integrated IM+P service is enabled on BroadWorks and points to the BroadWorks Provisioning Bridge.
The Provisioning Bridge URL was assigned when the Customer Template was applied to the organization. This should have been completed during your initial Webex for Cisco BroadWorks setup. To find the existing URL in Partner Hub, see Configure Application Server with Provisioning Service URL in the Webex for Cisco BroadWorks Solution Guide.
-
If you have multiple partner organizations, you require a dedicated Device Management Service (DMS) instance per partner.
Prerequisites for Activation Code Onboarding with Room OS
Make sure that the following is set:
-
Deploy the Device Activation Service on BroadWorks. For details, see Cisco BroadWorks Secure Onboarding Using Activation Codes.
-
Verify that the DAS URL setting for the BroadWorks cluster is set to the Device Management Services (DMS) URL. To view the current DAS URL setting in Partner Hub, go to and select the appropriate cluster. The URL appears under Interface settings.
The following BroadWorks features must be activated on the AS:
-
101377 Enhancements for Webex and MPP device onboarding
-
25088 Support Handsets for DECT Devices
-
24104 Support Multicell Chaining for DECT devices
-
20077 Device Management Enhancements
-
19559 Visual Device Management Enhancements
-
02283 Device Profile Type Customization Enhancements
For example, run the following command to enable 101377. Change the feature number when activating the other features:
AS_CLI/System/ActivatableFeature> activate 101377
If all the listed patches are installed and an activatable feature is not listed for your particular AS release, it is because it is already included in your AS base release and does not require activation.
Run the following CLI command on the Network Server:
NS_CLI/System/DeviceManagement> asLocationLookupEnabled true
Make sure that the CA that signs your SBC certificate is listed in the Room OS Trust List. You can view the Room OS trust list from the Device Web Portal. On the portal, select to view the list of CAs.
Room OS Onboarding Flow
-
Webex Board serien
-
Webex Desk-serien
-
Webex Room serien
| 1 |
Configure Services for Room OS Configure BroadWorks support for Room OS devices. |
| 2 |
Provision the new device on BroadWorks. |
| 3 |
In the Device Profile, request an activation code. The code will be emailed to the primary user automatically. |
Configure Services for Room OS
| 1 |
Raise a Service Request with your onboarding agent or with Cisco TAC to provision Cisco OAuth for your Cisco Identity Provider Federation account. Title your service request "ADP AuthService Configuration". If you already obtained Cisco OAuth Identity Provider credentials using one of the flows in this document, there’s no need to create a new request. However, if you obtained Cisco OAuth credentials using a flow that is not in this document, complete a new service request to update your credentials. Cisco ger dig ett OAuth-klient-ID, en klienthemlighet och en uppdateringstoken som är giltig i 60 dagar. If the token expires before you use it with your ADP, you can raise another request.
| ||||||||||||||||||||
| 2 |
Enable OAuth by using this CLI command:
| ||||||||||||||||||||
| 3 |
Make sure that the OAuth scope includes broadworks-connector-user (the scope is enabled by default). Run this command to check your scopes: ADP_CLI/Applications/BroadworksDms/AccessControl/Authentication/OAuth/Scopes> get | ||||||||||||||||||||
| 4 |
Configure the Cisco Identity Provider parameters using the below CLI commands.
| ||||||||||||||||||||
| 5 |
Configure Identity Providers for Cisco Federation using the following commands: ADP_CLI/System/CommunicationUtility/DefaultSettings/ExternalAuthentication/CiscoIdentityProvider/Federation>
The refresh token is now under the CiscoIdentityProvider/Partners context and the partnerName from the CiscoIdentityProvider/Federation context needs to match the partner added in the CiscoIdentityProvider/Partners context. If you are running an ADP RI load older than 2022.10, an R23 XSP without patch AP.xsp.23.0.1075.ap383838, or an R22 XSP, then:
| ||||||||||||||||||||
| 6 |
Clear all existing scopes within the following three contexts under
For each context, run a
| ||||||||||||||||||||
Provision Room OS Devices
| 1 |
On BroadWorks CommPilot, check the Identity/Device Profile Type configuration to see if the device type exists for this Room OS device. If the device type does not exist on BroadWorks, import the device type into BroadWorks using a DTAF file that you download from cisco.com. |
| 2 |
After you import the device type, make sure that the following settings exist within the Identity/Device Profile Type configuration:
|
| 3 |
Validate that the Device Profile File has the SIP settings that you want to use. In the Identity/Device Profile Type File make sure that Authentication Mode is Bearer. |
| 4 |
Create a Device Profile with the settings for your new device. In the Identity/Device Profile Add/Modify page, leave the MAC address field empty. |
| 5 |
Configure the Primary User. On the Users Add page, check or uncheck the isPlace according to whether you intend the device to be personal or for a shared workspace.
Shared workspace devices also require you to assign a primary user. You can assign the primary user that you want. |
| 6 |
Complete the option that corresponds to the device type and provisioning method that you want to use:
|
| 7 |
If the device is for personal use, and you want to use flowthrough provisioning, then for the primary user, assign the Integrated IM+P service. On the page, add the IM+P service: |
Nästa steg
Request Activation Code
| 1 |
In the Identity/Device Profile page, search for and open the device profile for your new device. |
| 2 |
Click the Device Activation tab. |
| 3 |
Click Request activation code. |
Nästa steg
Provide the device to the user. After the user plugs in the device, they are required to enter the activation code that was sent in the email. This will onboard the device to Webex for Cisco BroadWorks.
MPP Onboarding to Webex
This section describes the onboarding of either new or existing MPP devices to Webex for Cisco BroadWorks. Note that 'existing' refers to an MPP device that exists on BroadWorks, but which does not have Webex capability.
MPP Device Onboarding (New Devices)
During onboarding, the administrator updates BroadWorks with support for MPP, upgrades the device firmware and provisions the device on BroadWorks to complete onboarding.
The following diagram provides an overview of the onboarding process after the activation code that the user enters is validated.
MPP Device Onboarding (Existing Devices)
For existing MPP devices, where the device exists already on BroadWorks, but is not onboarded to Webex, update BroadWorks and the device firmware to support MPP to Webex onboarding. After the updates, the device onboards to Webex automatically.
Mer information
For more information on MPP device onboarding to Webex, refer to the feature description Cisco BroadWorks DMS Enhancements for Webex Enabling MPP Devices.
MPP Device Prerequisites
Minimum MPP Version
MPP firmware 11.3.7 minimum
BroadWorks Patch Requirements
This feature is supported as of version 2021.11 of the Release Independent (RI) ADP server with no patch requirements.
For non-RI servers, you must have installed the following patches (from patch groups ap381367, ap381951, ap382198) in order to use the feature. Install the patches that apply to your release:
För R22:
-
AP.as.22.0.1123.ap381367
-
AP.as.22.0.1123.ap382236
-
AP.nfm.22.0.1123.ap381367
-
AP.ns.22.0.1123.ap381367
-
AP.platform.22.0.1123.ap381367
-
AP.platform.22.0.1123.ap382198
-
AP.ps.22.0.1123.ap381367
-
AP.xsp.22.0.1123.ap381367
-
AP.xsp.22.0.1123.ap382198
För R23:
-
AP.as.23.0.1075.ap381367
-
AP.as.23.0.1075.ap382236
-
AP.ns.23.0.1075.ap381367
-
AP.platform.23.0.1075.ap382198
-
AP.platform.23.0.1075.ap381367
-
AP.xsp.23.0.1075.ap381367
-
AP.xsp.23.0.1075.ap382198
-
AP.ps.23.0.1075.ap381367
För R24:
-
AP.as.24.0.944.ap381367
-
AP.as.24.0.944.ap381951
-
AP.as.24.0.944.ap382236
BroadWorks Platform Requirements
This feature is available on:
-
R22: available on XSP only
-
R23: available on XSP or ADP (Release Independent)
-
R24: available on ADP (Release Independent)
BroadWorks Configuration Requirements
-
To implement this solution, the Flowthrough provisioning must be configured to allow Broadworks to provision devices to Webex.
While configuring the Flowthrough provisioning, it’s not mandatory to use flowthrough provisioning to provision users i.e., you can continue to use your existing provisioning methods (API, Trusted/Untrusted Email, User self, etc.) to provision users. See "Provisioning Requirements" in the Webex for Cisco BroadWorks Solution Guide.
-
Make sure that the Integrated IM+P service is enabled on BroadWorks and points to the BroadWorks Provisioning Bridge.
The Provisioning Bridge URL was assigned when the Customer Template was applied to the organization. This should have been completed during your initial Webex for Cisco BroadWorks setup. To find the existing URL in Partner Hub, see Configure Application Server with Provisioning Service URL in the Webex for Cisco BroadWorks Solution Guide.
-
If you have multiple partner organizations, you require a dedicated Device Management Service (DMS) instance per partner.
Certificates and Firewalls
Make sure that you have configured the following:
-
Certificate Requirements—MPP devices use mTLS authentication using the device certificate. The device MAC address, which the certificate provides, authenticates the device. Download the required certificates for your MPP device from https://www.cisco.com/security/pki/.
Upload your certificates to establish trust on the ADP or firewall. For example, if you’re uploading to the ADP, use this command:
ADP_CLI/Interface/Http/SSLCommonSettings/ClientAuthentication/Trusts/updateTrust> <certificate_filename> -
Firewall requirements—If ADP is behind a firewall, your firewall must be configured with a rule to extract the MAC address from the device certificate and place it in an Authentication header that is then forwarded to the ADP. For example, the identity pattern
.*([0-9a-fA-F]{12}).*can be used to extract the MAC address, which can then be placed in a header that uses a descriptive name (for example,macaddress).If ADP is not behind a firewall, the preceding requirement doesn’t exist.
Feature Activation
Activate the following BroadWorks features on the AS:
-
101377 Enhancements for Webex and MPP device onboarding
-
25088 Support Handsets for DECT Devices
-
23775 Remote Reset for MPP Devices
-
24104 Support Multicell Chaining for DECT devices
-
20077 Device Management Enhancements
-
19559 Visual Device Management Enhancements
-
02283 Device Profile Type Customization Enhancements
For example, run the following command to enable 101377.Change the feature number when activating the other features:
AS_CLI/System/ActivatableFeature> activate 101377
If all the listed patches are installed and an activatable feature is not listed for your particular AS release, it is because it is already included in your AS base release and does not require activation.
Run the following CLI on the Network Server:
NS_CLI/System/DeviceManagement> asLocationLookupEnabled true
Activation Code Requirements
Valfritt. Activation codes are not mandatory for MPP device onboarding. Howver, if you want to use activation codes, see Request Activation Code for MPP for additional requirements that are specific to activation codes with MPP.
MPP Device Onboarding Flow
| 1 |
(New or existing MPP devices). Configure system support for MPP on Webex for Cisco BroadWorks. |
| 2 |
(Existing MPP devices). For any existing MPP devices for which you want to add Webex capability, upgrade to the latest device firmware. |
| 3 |
(New MPP devices only). If the device doesn’t exist on BroadWorks, provision the device and primary user on BroadWorks. |
| 4 |
Request Activation Code for MPP (Optional). If you want to use activation codes to onboard MPP devices, request an activation code.
|
Configure Services for MPP
Innan du börjar
If the ADP is behind a firewall, your firewall must be configured with a rule to extract the MAC address from the device certificate and place it in an Authentication header that is then forwarded to the ADP. For example, the identity pattern .*([0-9a-fA-F]{12}).* can be used to extract the MAC address, which can then be placed in a header that uses a descriptive name (for example, macaddress).
Refer to your firewall documentation for help with the configurations.
| 1 |
Raise a Service Request with your onboarding agent or with Cisco TAC to provision Cisco OAuth for your Cisco Identity Provider Federation account. Use "ADP AuthService Configuration" to title your request. Cisco ger dig ett OAuth-klient-ID, en klienthemlighet och en uppdateringstoken som är giltig i 60 dagar. If the token expires before you use it with your ADP, you can raise another request. If you already obtained Cisco OAuth Identity Provider credentials using one of the flows in this document, there’s no need to create a new request. However, if you obtained Cisco OAuth credentials using a flow that is not in this document, complete a new service request to update your credentials. | ||||||||||
| 2 |
Configure the Cisco Identity Provider parameters by running the following CLI commands.
| ||||||||||
| 3 |
Set the url of the DM Bridge using the below CLI command. The DM Bridge URL is different for each Teams Cluster (which you pulled in Step 2).
| ||||||||||
| 4 |
Enable MAC address extraction and authentication using either the Authentication header or Authentication certificate. For security reasons, we recommend that you use one of the options only:
| ||||||||||
Upgrade MPP Device Firmware
Innan du börjar
|
Upgrade the device firmware to the latest version to ensure that tha the MPP device supports Webex capability. For more information on firmware upgrades, refer to the Release Notes for your phone model firmware release. |
Nästa steg
-
Existing MPP devices—After the upgrade, the device onboards to Webex automatically. The user can start using Webex services on the device.
-
New MPP devices—Provision the new MPP device on BroadWorks.
Provision MPP Device
| 1 |
On BroadWorks CommPilot, check the Identity/Device Profile Type configuration to see if the device type exists for this MPP device. If the device type doesn’t exist on BroadWorks, import the device type into BroadWorks using a DTAF file that is downloaded from cisco.com. |
| 2 |
On BroadWorks CommPilot, open the Identity/Device Profile Type and check the Allow Activation Code Onboarding check box. |
| 3 |
Create an Identity/Device Profile Type File with the SIP settings that you want to use. |
| 4 |
Create an Identity/Device Profile with settings for your new device. In the MAC address field, enter the device MAC address. If you are using activation codes to onboard MPP devices, leave the MAC address field empty. |
| 5 |
Configure the Primary User. On the Users Add page, set the isPlace check box according to whether the device is personal or for a shared workspace:
|
| 6 |
Complete the option that corresponds to the device type and provisioning method that you want to use:
|
| 7 |
If the device is for personal use, and you want to use flowthrough provisioning, then for the primary user, assign the Integrated IM+P service. On the page, add the IM+P service: |
Nästa steg
Request Activation Code for MPP
(Optional) Webex for Cisco BroadWorks does not require activation codes to onboard new MPP devices. However, if you do decide to use activation codes, complete the Request Activation Code procedure to request an activation code for a new device.
Prerequisites for Using Activation Codes with MPP Devices
If you are using activation code onboarding for MPP devices, make sure that your system meets the following activation code-specific requirements.
Device Activation Service—Complete the following requirements to enable the Device Activation Service:
-
Deploy the Device Activation Service on BroadWorks. For details, see Cisco BroadWorks Secure Onboarding Using Activation Codes.
-
Point the Device Activation Service (DAS) to Device Management Services (DMS) on BroadWorks AS using the following CLI command:
AS_CLI/Interface/DAS> set url <url_of_DMS> -
Verify that the DAS URL setting for the BroadWorks cluster is set to the Device Management Services (DMS) URL. To view the current DAS URL setting in Partner Hub, go to and select the appropriate cluster. The URL appears under Interface settings.
Cisco Global Discovery Services (GDS)—GDS is required in order to provision the activation code. Enable GDS on BroadWorks by completing both of the below steps:
-
Create a service request to provision your GDS account. Cisco provides you with the client ID, client secret, refresh token and GDS domain.
-
After your GDS account is provisioned, enable GDS on the ADP using the following CLI:
ADP_CLI/Applications/BroadworksDms/DeviceActivation/IdentityProviders/Cisco> get set gdsDomain <gds_domain_from service request> e.g. https://activation.webex.com set clientId <id_from_service_request> clientSecret <secret_from_service_request> refreshToken <token_from_service_request>
Request Activation Code
Complete the following steps to request an activation code for a new MPP device.
-
In the Identity/Device Profile page, search for and open the device profile for your new device.
-
Click the Device Activation tab.
-
Click Request activation code.
The system generates the activation code and emails the code to the primary user. The user must enter the code on the device to complete onboarding.
Enhetens tjänstehantering
Översikt över servicevänlighet
Control Hub innehåller alternativ för servicevänlighet som låter administratörer visa enhetsstatus, tillsammans med en uppsättning underhållsalternativ. Administratörer kan:
-
Visa aktuell enhetsstatus
-
Starta om enheten på distans
-
Skicka en problemrapport för felsökning
-
Ta bort enheten
Visa enhetsstatus
| 1 |
Logga in på Control Hub-instansen för en kundorganisation. |
| 2 |
Klicka på Enheter. |
| 3 |
Klicka på lämplig enhet. |
Starta om enhet
| 1 |
Logga in på Control Hub-instansen för en kundorganisation. |
| 2 |
Klicka på Enheter. |
| 3 |
Välj en enhet. |
| 4 |
I listrutan Åtgärder väljer du Starta om. |
Rapportera problem
| 1 |
Logga in på Control Hub-instansen för en kundorganisation. |
| 2 |
Klicka på Enheter. |
| 3 |
Klicka på den tillämpliga enheten. |
| 4 |
Från Åtgärder väljer du Rapportproblem. |
| 5 |
Granska rapportsammanfattningen. |
Ta bort enhet
| 1 |
Logga in på Control Hub-instansen för en kundorganisation. |
| 2 |
Klicka på Enheter. |
| 3 |
Välj lämplig enhet. |
| 4 |
I listrutan Åtgärder väljer du Ta bort. |
Ändra enhetsägare
| 1 |
Ta bort befintlig enhetsregistrering från Webex: |
| 2 |
I BroadWorks inaktiverar du enhetsregistreringen under den befintliga användaren: |
| 3 |
I BroadWorks aktiverar du enheten med aktiveringskoden från en annan identitet/enhetsprofil som används av en annan användare: |
Nästa steg
-
Den nya enhetsägaren anger aktiveringskoden på enheten.
-
Enheten registreras om till både Webex och Broadfungerar med den nya konfigurationen. Den nya identitets-/enhetsprofilen på BroadWorks uppdateras automatiskt med enhetens MAC-adress.
prestandaövervakning
Följande prestationsräknare finns för den här funktionen.
|
Räknare |
Beskrivning |
|---|---|
|
Modul: enterprises.broadsoft.broadworks.deviceActivation.activate | |
|
bwDASA aktiverarförfrågningar |
Det totala antalet aktiveringsförfrågningar som har tagits emot. Detta inkluderar att aktivera BroadWorks-förfrågningar och aktivera Webex-förfrågningar. |
|
bwDASA aktiverarMisslyckanden |
Det totala antalet aktiveringsförfrågningar som inte slutfördes. Detta inkluderar aktivering av BroadWorks-förfrågningar som misslyckades och aktivering av Webex-förfrågningar som misslyckades. |
|
bwDASA aktiverarBroadworks-förfrågningar |
Antalet aktiveradeBroad Works-förfrågningar som togs emot. |
|
bwDASA aktiverarBroadWorksFel |
Antalet aktiveradeBroad Works-förfrågningar som inte slutfördes. Autentiserings- och autentiseringsfel beaktas inte av den här räknaren. |
|
bwDASA aktiverarWebex-förfrågningar |
Antalet aktiverade Webex-förfrågningar som togs emot. |
|
bwDASA aktiverarWebex-fel |
Antalet aktiverade Webex-förfrågningar som inte slutfördes. |
|
Modul: enterprises.broadsoft.broadworks.dms.dmBridge | |
|
bwDMBridge-förfrågningar |
Antalet DMBridge-förfrågningar som skickades. |
|
bwDMB ridgeFel |
Antalet DMBridge-förfrågningar som inte slutfördes. |
Slutanvändarfunktioner för Webex-integrerade enheter
Enhetlig samtalshistorik
Webex-medvetna MPP-telefoner
Webex Aware Cisco MPP-enheter på Webex för BroadWorks-plattformen kommer nu att kunna visa en enhetlig samtalshistorik för samtal som görs/tas emot från användarens Webex-klient och deras enheter. Detta ger en förbättrad upplevelse för slutanvändarenheten eftersom de kan observera och använda samtal som görs/tas emot via sin Webex-app via samtalsloggar på sina MPP-enheter tillsammans med alla lokala samtal som bearbetas på deras enhet.
Webex Unified Samtalshistorik är standardkällan för att visa en användares samtalshistorik. Den här samtalshistoriken innehåller samtal från alla telefoner, Webex-videoenheter eller Webex-appen.
Påverkade IP-telefonmodeller:
-
MPP68xx Serie 6821, 6841, 6851, 6861
-
MPP78xx Serie 7811, 7821, 7841, 7861
-
MPP 88xx Series 8811, 8841, 8845, 8851, 8861, 8865, 8875
Aktivering av funktioner:
Följande kriterier måste uppfyllas för att aktivera funktionen
-
Webex för BroadWorks-enhetsintegration måste implementeras och fungera för MPP-enheter. Mer information finns i den här guiden Enhetsintegrering-Guide-för-Webex-för-Cisco-Broad Works.
Krav på programfix och DTAF:
Förväntningar/effekter/begränsningar:
-
Primär linje (endast aktuell användare)
-
Enhetlig samtalshistorik stöds enligt ovan.
-
Support Privacy Protection – Skydda/dölj samtalshistorik när användarlösenord har angetts.
-
Om telefonen inte är molnmedveten visas endast den ”lokala historiken” för samtal till och från den här enheten.
-
-
Andra linjer (delade eller på annat sätt)
-
Endast lokal historik för samtal till och från en enhet stöds.
-
-
Arbetsytenheter
-
Enhetlig samtalshistorik stöds inte i det här fallet.
-
När funktionen är aktiverad kommer all lokal samtalshistorik på MPP (härledd från BroadWorks) att tas bort.
Webex för BroadWorks integrerade RoomOS-enheter
Webex för BroadWorks integrerade Cisco RoomOS-enheter kommer nu att kunna visa en enhetlig samtalshistorik för samtal som görs/tas emot från användarens Webex-klient och deras enheter. Detta ger en förbättrad upplevelse för slutanvändarenheten eftersom de kan observera och använda samtal som görs/tas emot via sin Webex-app via samtalsloggar på sina RoomOS-enheter tillsammans med alla lokala samtal som bearbetas på deras enheter.
Webex Unified Samtalshistorik är standardkällan för att visa en användares samtalshistorik. Den här samtalshistoriken innehåller samtal från alla telefoner, Webex-videoenheter eller Webex-appen.
Finns på följande rumsenhetsmodellerRoomOS:
-
RoomOS-enheter
-
Skrivbordsserie: Desk, Desk Mini, Desk Pro
-
Room-serien
-
Rumskit-serien
-
Webex Board serien
Aktivering av funktioner:
-
Webex för BroadWorks-enhetsintegration måste implementeras och fungera för RoomOS-enheter. Mer information finns i den här guiden Enhetsintegrering-Guide-för-Webex-för-Cisco-Broad Works.
Krav på programfix och DTAF:
-
Broadworks – Den här funktionen är beroende av att relevanta BroadWorks-korrigeringar installeras. Detaljer finns här.
Konfigurationskrav:
-
Konfigurationerna nedan måste ställas in enligt anvisningarna
-
Bwks-konfiguration: Feature_Toggle_Webex_Samtal=Ja
-
Förbättringar av katalogsökning för Webex för BroadWorks integrerade RoomOS-enheter
Webex för BroadWorks integrerade Cisco Room OS-enhetsanvändare kommer nu att kunna söka efter personer, utrymmen och till och med enheter i sin Webex-organisation direkt från sina RoomOS-enheter genom implementeringen av en ny förbättrad Webex Directory-tjänst. Den här tjänsten ger förbättrade sökfunktioner och sökfunktioner för Webex så att BroadWorks-användare kan hitta användare och saker (arbetsytor, enheter osv.) i sin Webex-organisation.
Finns på följande rumsenhetsmodellerRoomOS:
-
RoomOS-enheter
-
Skrivbordsserie: Desk, Desk Mini, Desk Pro
-
Room-serien
-
Rumskit-serien
-
Webex Board serien
Aktivering av funktioner:
-
Webex för BroadWorks-enhetsintegration måste implementeras och fungera för MPP-enheter. Mer information finns i den här guiden Enhetsintegrering-Guide-för-Webex-för-Cisco-Broad Works.
Konfigurationskrav:
-
Växlingsknappen för katalogtjänsten ”xConfiguration Webex DirectoryServiceSupport” måste aktiveras på enheten.
