- 主页
- /
- 文章
适用于 Cisco BroadWorks 的 Webex 的设备集成指南
在此文章中设备集成指南针对合作伙伴级别的管理员。本文档介绍了如何使用此解决方案部署和管理设备。
介绍
关于本指南
文档更改历史记录
下表总结了该文档的更改历史记录。
|
日期 |
文档版本 |
更改的描述 |
|---|---|---|
|
2023年5月12日 |
1.7 | 在 bex集成设备的最终用户功能部分下 添加了针对W4B集成RoomOS设备 的 bex for BroadWorks集成Cisco RoomOS设备 Webex for BroadWorks集成Cisco RoomOS设备 的目录搜索增强功能。 |
|
2023年2月27日 |
1.6 | 更新了设备自行激活 下的“Configure Services for Room OS”（为Room OS配置服务）步骤。 |
|
2023年2月17日 |
1.5 | 在 bex集成设备的最终用户功能 下添加了 bex感知MPP电话的统一呼叫历史记录。 |
|
2022 年 10 月 14 日 |
1.4 |
|
|
2022年6月20日 |
1.3 |
|
|
2022年6月3日 |
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上，使用不同用户使用的不同身份/设备配置文件 中的激活代码激活设备： |
下一步
-
新的设备所有者在设备上输入激活代码。
-
设备使用新配置重新注册到Webex和BroadWorks。BroadWorks上的新 /设备配置文件 会使用设备MAC地址自动更新。
性能监控
该功能存在以下性能计数器。
|
计数器 |
描述 |
|---|---|
|
模块：企业。broadsoft.broadworks.设备激活。 | |
|
bwDASActivateRequests |
收到的激活请求总数。这包括激活BroadWorks请求和激活Webex请求。 |
|
bwDASActivate故障 |
未能成功完成的激活请求总数。其中包括激活失败的BroadWorks请求和激活失败的Webex请求。 |
|
bwDASActivateBroadWorks请求 |
收到的激活BroadWorks请求数。 |
|
bwDASActivateBroadWorks失败 |
未能成功完成的激活BroadWorks请求数。此计数器不会考虑授权和验证失败。 |
|
bwDASActivateWebex请求 |
收到的激活Webex请求数。 |
|
bwDASActivateWebex故障 |
未能成功完成的激活Webex请求数。 |
|
模块：企业。broadsoft.broadworks.dms.dmBridge | |
|
bwDMBridgeRequests |
已发送的DMBridge请求数。 |
|
bwDMBridge故障 |
未能成功完成的DMBridge请求数。 |
Webex集成设备的最终用户功能
统一呼叫历史记录
Webex感知MPP电话
Webex for BroadWorks平台上的Webex AwareCisco MPP设备现在能够显示从用户的Webex客户端及其设备发起/接收的呼叫的统一呼叫历史记录。这可以改善最终用户设备的体验，因为他们可以通过MPP设备上的呼叫日志观察和使用通过Webex应用程序发起/接收的呼叫以及在其设备上处理的所有本地呼叫。
Webex Unified 呼叫历史记录将成为查看用户呼叫历史记录的缺省来源。此呼叫历史记录包含从所有电话、Webex 视频设备或 Webex 应用程序发起的呼叫。
受影响的IP电话型号：
-
MPP68xx 6821、6841、6851、6861 系列
-
MPP78xx 7811、7821、7841、7861 系列
-
MPP88xx 8811、8841、8845、8851、8861、8865、8875
功能启用：
需要满足以下条件才能启用该功能
-
需要对MPP设备实施Webex for BroadWorks设备集成并实现功能。有关更多详细信息，请参阅本指南 -Integration-Guide-for-Webex-for-Cisco-BroadWorks。
补丁和DTAF要求：
期望/影响/限制：
-
主线路（仅限当前用户）
-
如上所述，将支持统一呼叫历史记录。
-
支持隐私保护-设置用户密码时保护/隐藏呼叫历史记录。
-
如果电话不能感知云，则只会显示进出此设备的呼叫的“本地历史记录”。
-
-
其他线路（共享或其他）
-
仅支持与设备之间的本地呼叫历史记录。
-
-
工作空间设备
-
在此实例中不支持统一呼叫历史记录。
-
当启用该功能时，MPP上的所有本地呼叫历史记录（源自BroadWorks）都将删除。
Webex for BroadWorks集成的RoomOS设备
Webex for BroadWorks集成的Cisco RoomOS设备现在能够显示从用户的Webex客户端及其设备发起/接听的呼叫的统一呼叫历史记录。这可以改善最终用户设备的体验，因为他们可以通过RoomOS设备上的呼叫日志观察和使用通过Webex应用程序发起/接收的呼叫以及在其设备上处理的所有本地呼叫。
Webex Unified 呼叫历史记录将成为查看用户呼叫历史记录的缺省来源。此呼叫历史记录包含从所有电话、Webex 视频设备或 Webex 应用程序发起的呼叫。
在以下RoomOS设备型号上可用：
-
RoomOS设备
-
桌面系列：Desk， Desk Mini， Desk Pro
-
Room 系列
-
RoomKit系列
-
Webex Board 系列
功能启用：
-
需要对RoomOS设备实施Webex for BroadWorks设备集成并使其正常运行。有关更多详细信息，请参阅本指南 -Integration-Guide-for-Webex-for-Cisco-BroadWorks。
补丁和DTAF要求：
-
Broadworks -此功能取决于安装的相关BroadWorks补丁。有关详细信息，请参见此处。
配置要求：
-
以下配置需要设置为指定配置
-
Bwks配置：电话eature_oggle_ebex_=是
-
Webex for BroadWorks集成RoomOS设备的目录搜索增强功能
通过实施新的增强型Webex目录服务，Webex for BroadWorks集成的Cisco RoomOS设备用户现在可以直接从其RoomOS设备搜索Webex组织中的人员、空间甚至设备。此服务为Webex for BroadWorks用户提供增强的搜索和查找功能，以便能够在其Webex组织中查找用户和事物（工作空间、设备等）。
在以下RoomOS设备型号上可用：
-
RoomOS设备
-
桌面系列：Desk， Desk Mini， Desk Pro
-
Room 系列
-
RoomKit系列
-
Webex Board 系列
功能启用：
-
需要对MPP设备实施Webex for BroadWorks设备集成并实现功能。有关更多详细信息，请参阅本指南 -Integration-Guide-for-Webex-for-Cisco-BroadWorks。
配置要求：
-
需要在设备上启用目录服务切换“xConfiguration Webex DirectoryServiceSupport”。
