- ホーム
- /
- 投稿記事
Cisco BroadWorks 版 Webex のデバイス連携ガイド
この記事の内容デバイス統合ガイドは、パートナーレベルの管理者で必要です。このドキュメントでは、このソリューションを使用してデバイスを展開および管理する方法について説明します。
紹介
このガイドについて
このドキュメントは、Cisco BroadWorks 版 Webex を展開するサービス プロバイダー組織のパートナー管理者を対象としています。このガイドは、Cisco BroadWorks での Webex の Room OS および MPP デバイスのオンボーディングとサービスの方法を説明しています。このガイドは、次の 2 つの章に分きます。
- デバイスのオンボーディング—Room OS デバイス (Room および Room Kit シリーズ、Desk シリーズ、Board シリーズ) および MPP デバイスを Cisco BroadWorks 版 Webex にオンボードする方法について説明します。
- デバイスの保守性—Control Hub 内でオンボードデバイスを管理する方法について説明します。
ドキュメントの変更履歴
次の表に、このドキュメントの変更履歴をまとめています。
|
日付 |
ドキュメントバージョン |
変更の説明 |
|---|---|---|
|
2023年5月12日。 |
1.7 | [Webex 統合デバイスのエンド ユーザー機能] セクションに、BroadWorks 版 Webex 統合型 Cisco RoomOS デバイス および W4B 統合型 RoomOS デバイスのディレクトリ検索の強化 が追加されました。 |
|
2023年2月27日。 |
1.6 | 「デバイスのオンボーディング」の「Room OS のサービスの設定 」手順が更新されました。 |
|
2023年2月17日。 |
1.5 | 「Webex 統合デバイスのエンド ユーザー機能」の「Webex 対応 MPP 電話の統合通話履歴 」セクションを追加しました。 |
|
2022 年 10 月 14 日 |
1.4 |
|
|
2022 年 6 月 20 日 |
1.3 |
|
|
2022 年 6 月 03 日 |
1.2 |
|
|
2022 年 5 月 27 日 |
1.1 |
|
|
2022 年 5 月 20 日 |
1.0 |
|
Cisco BroadWorks 用 Webex のデバイスインテグレーション
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:
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
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
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 シリーズ
-
Webex Desk シリーズ
-
Webex Room シリーズ
| 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 は OAuth クライアント ID、クライアント シークレット、および 60 日間、有効な更新トークンを提供します。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: |
次に行うこと
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. |
次に行うこと
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.
詳細情報
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:
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
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
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
オプションです。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
スケジューリングを始める前に
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 は OAuth クライアント ID、クライアント シークレット、および 60 日間、有効な更新トークンを提供します。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
スケジューリングを始める前に
|
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. |
次に行うこと
-
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: |
次に行うこと
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.
デバイスの保守性
保守性の概要
Control Hub には、管理者がデバイスのステータスを表示できるサービスアビリティ オプションと、一連のメンテナンス オプションが含まれています。管理者は、次のことを行うことができます。
-
現在のデバイス ステータスを表示
-
デバイスをリモートで再起動する
-
トラブルシューティングのための問題レポートの送信
-
デバイスを削除する
デバイス ステータスの表示
| 1 |
顧客組織の Control Hub インスタンスにサインインします。 |
| 2 |
[デバイス] をクリックします。 |
| 3 |
適切なデバイスをクリックします。 |
デバイスを再起動
| 1 |
顧客組織の Control Hub インスタンスにサインインします。 |
| 2 |
[デバイス] をクリックします。 |
| 3 |
デバイスを選択します。 |
| 4 |
[アクション ] ドロップダウンから、[リブート] を選択します。 |
エラー報告
| 1 |
顧客組織の Control Hub インスタンスにサインインします。 |
| 2 |
[デバイス] をクリックします。 |
| 3 |
該当するデバイスをクリックします。 |
| 4 |
[アクション] から、[問題を報告] を選択します。 |
| 5 |
レポートの概要を確認します。 |
デバイスを削除
| 1 |
顧客組織の Control Hub インスタンスにサインインします。 |
| 2 |
[デバイス] をクリックします。 |
| 3 |
該当するデバイスを選択します。 |
| 4 |
[アクション ] ドロップダウンから、[削除] を選択します。 |
デバイスの所有者の変更
| 1 |
Webex から既存のデバイス登録を削除する: |
| 2 |
BroadWorks では、既存のユーザーの下でデバイス登録を無効にします。 |
| 3 |
BroadWorks で、別のユーザが使用する別の ID/デバイス プロファイル のアクティベーション コードを使用してデバイスをアクティブ化します。 |
次に行うこと
-
新しいデバイスの所有者は、デバイスのアクティベーション コードを入力します。
-
デバイスは、新しい設定を使用して Webex と BroadWorks の両方に再登録されます。BroadWorks の新しい ID/デバイス プロファイル は、デバイスの MAC アドレスで自動的に更新されます。
パフォーマンス監視
この機能には、次のパフォーマンス カウンタが存在します。
|
カウンター |
説明 |
|---|---|
|
モジュール: enterprise.broadsoft.broadworks.deviceActivation.activateを起動 | |
|
bwDASActivateリクエスト |
受信されたアクティベート要求の合計数。これには、BroadWorks 要求のアクティブ化と Webex 要求のアクティブ化が含まれます。 |
|
bwDASActivateエラー |
正常に完了できなかったアクティブ化要求の合計数。これには、失敗した BroadWorks 要求のアクティブ化と、失敗した Webex 要求のアクティブ化が含まれます。 |
|
bwDASActivateBroadWorksリクエスト |
受信された BroadWorks アクティベート要求の数。 |
|
bwDASActivateBroadWorksエラー |
正常に完了できなかった BroadWorks のアクティブ化要求の数。このカウンタでは、認証と認証の失敗は考慮されません。 |
|
bwDASActivateWebexリクエスト |
受信された Webex アクティベート要求の数。 |
|
bwDASActivateWebexエラー |
正常に完了しなかった Webex アクティベート要求の数。 |
|
モジュール: enterprise.broadsoft.broadworks.dms.dmブリッジ | |
|
bwDMBridgeリクエスト |
送信された DMBridge 要求の数。 |
|
bwDMBridgeエラー |
正常に完了できなかった DMBridge 要求の数。 |
Webex 統合デバイスのエンドユーザー機能
統合通話履歴
Webex aware MPP phones
Webex Aware Cisco MPP Devices on Webex for BroadWorks platform will now be able to display a unified call history for calls made/received from the user’s Webex client and their devices. This allows for an improved experience for the end users device as they can observe & use the calls made/received through their Webex app via call logs on their MPP devices along with all local calls processed on their device.
Webex統合通話履歴は、ユーザーの通話履歴を表示するためのデフォルトのソースになります。この通話履歴には、すべての電話、 Webexビデオ デバイス、またはWebexアプリからのコールが含まれています。
Affected IP Phone Models:
-
MPP68xxシリーズ 6821、6841、6851、6861
-
MPP78xx 7811、7821、7841、7861
-
MPP 88xx Series 8811, 8841, 8845, 8851, 8861, 8865, 8875
Feature Enablement:
Following criteria is required to be fulfilled to enable the feature
-
Webex for BroadWorks device integration needs to be implemented and functional for MPP devices. More details can be found in this guide Device-Integration-Guide-for-Webex-for-Cisco-BroadWorks.
Patch & DTAF requirements:
Expectations/Impacts/Limitations:
-
Primary line (Current User Only)
-
Unified Call History will be supported as mentioned.
-
Support Privacy protection - Protect/Hide Call History when user password is set.
-
If the phone is not Cloud Aware, only the ‘local history’ of calls to and from this device will be shown.
-
-
Other lines (Shared or otherwise)
-
Only local history of calls to and from a device will be supported.
-
-
Workspace Devices
-
Unified Call History will not be supported at this instance.
-
When the feature is turned on, all local call history on the MPP (derived from BroadWorks) will be deleted.
Webex for BroadWorks integrated RoomOS Devices
Webex for BroadWorks integrated Cisco RoomOS Devices will now be able to display a unified call history for calls made/received from the user’s Webex client and their devices. This allows for an improved experience for the end users device as they can observe & use the calls made/received through their Webex app via call logs on their RoomOS devices along with all local calls processed on their devices as well.
Webex統合通話履歴は、ユーザーの通話履歴を表示するためのデフォルトのソースになります。この通話履歴には、すべての電話、 Webexビデオ デバイス、またはWebexアプリからのコールが含まれています。
Available on the below RoomOS Device Models:
-
RoomOS Devices
-
Desk シリーズ: Desk, Desk Mini, Desk Pro
-
Room シリーズ
-
RoomKit Series
-
Webex Board シリーズ
Feature Enablement:
-
Webex for BroadWorks device integration needs to be implemented and functional for RoomOS devices. More details can be found in this guide Device-Integration-Guide-for-Webex-for-Cisco-BroadWorks.
Patch & DTAF requirements:
-
Broadworks - This feature is dependent on the relevant BroadWorks patches being installed. Details can be found here.
Configuration requirements:
-
Below configurations needs to be set as specified
-
Bwks Config: Feature_Toggle_Webex_Call=Yes
-
Directory search enhancements for Webex for BroadWorks integrated RoomOS Devices
Webex for BroadWorks integrated Cisco RoomOS Device users will now be able to search the people, spaces and even devices in their Webex org directly from their RoomOS devices with the implementation of a new enhanced Webex Directory service. This service provides enhanced search and lookup capabilities to Webex for BroadWorks users to be able to find users and things (workspaces, devices etc.) in their Webex org.
Available on the below RoomOS Device Models:
-
RoomOS Devices
-
Desk シリーズ: Desk, Desk Mini, Desk Pro
-
Room シリーズ
-
RoomKit Series
-
Webex Board シリーズ
Feature Enablement:
-
Webex for BroadWorks device integration needs to be implemented and functional for MPP devices. More details can be found in this guide Device-Integration-Guide-for-Webex-for-Cisco-BroadWorks.
Configuration requirements:
-
Directory service toggle “xConfiguration Webex DirectoryServiceSupport” needs to be enabled on the Device.
