==== Cisco Webex Control Hub with Workspace Integration ==== To be able to use the Cisco Webex APIs to monitor your Cisco Webex devices, you need to: * Have administrator access to Control Hub ([[https://admin.webex.com]]) * Enable the Zebrix Control integration in Control Hub > Workspace > Integration * Declare an external service of type **Cisco Control Hub with Workspace Integration** in Zebrix Control. * Create and configure your devices. === Enable the Zebrix Control integration in Control Hub === Beginning by downloading the Zebrix integration file:[[https://control.zebrix.net/download/webex/manifest_webex_workspace_zebrix_control.json|Manifest Workspace Integration]] Once logged in to [[https://admin.webex.com|Control Hub]], go to Workspace > Integrations {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.18.56.png?400|}} Then, click the **Add Integration button** and choose **Upload Integration** {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.19.57.png?400|}} Drop the Zebrix integration file (downloaded at the beginning of this section manifest_webex_workspace_zebrix_control.json) {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.20.30.png?400|}} Click **Upload** {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.22.05.png?400|}} You need **to retrieve and securely store the OAuth Client ID and Secret** for Webex service authentication. {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.22.57.png?400|}} Then activate the integration by clicking **Actions > Activate** {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.25.40.png?400|}} Finally, you will need to retrieve the activation code (JWT) {{:fr:guide:cisco:control_hub:screenshot_2025-04-01_at_15.26.21.png?400|}} === Extract data from the activation code (JWT) === As explained in [[https://github.com/cisco-ce/workspace-integrations-nodejs?tab=readme-ov-file#prelude-adding-and-activating-an-integration|the Cisco documentation]], to extract the necessary fields for the driver configuration, you can either use: * via JWT.io * Via a NodeJS script (see documentation) For the configuration in Zebrix Control, you will need to retrieve the following fields: * **oauthUrl** * **appUrl** * **webexapisBaseUrl** * **refreshToken** For example, by using JWT.io : {{:fr:guide:cisco:control_hub:screenshot_2025-04-07_at_09.21.54.png?400|}} === External Service Configuration in Zebrix Control === Let's configure the __External Service (Cisco Control Hub with Workspace Integration) driver__ in the Zebrix Control administration interface: * **Client ID** : Use the AccessKey ID (Client ID) retrieved previously. * **Client Secret** : Use the AccessKey Secret (Client Secret) retrieved previously. * **oauthUrl** : Use the oauthUrl retrieved previously. * **appUrl** : Use the appUrl retrieved previously. * **webexapisBaseUrl** : Use the webexapisBaseUrl retrieved previously. * **refreshToken** : Use the refreshToken retrieved previously. Your External Service is now added in Zebrix Control. === How to retrieve the device ID (Driver configuration) ? === There are several methods to retrieve the Webex device ID. == API Request == You can retrieve it on [[https://developer.webex.com/docs/api/v1/devices/list-devices|List Webex device API]] == PowerShell script == We also provide a Powershell script allowing you to retrieve the list of devices and export them into a CSV. Invoke-WebRequest -Uri "https://control.zebrix.net/download/webex/Get-Devices.ps1" -OutFile "Get-Devices.ps1" ./Get-Devices.ps1 -UseImplicitFlow -AutoExport == Control Hub == Log on to the Control Hub and go to the device page. Click on **View all statuses** {{ .:pasted:20250619-111121.png }} Go to **Webex** section {{ .:pasted:20250619-111255.png }} The ID you are looking for is the **Webex DeveloperId**. === Port Opening === The probe must be able to establish outbound connections to the configured URLs: **oauthUrl**, **appUrl**, and **webexapisBaseUrl**. === Equipments Configuration === To enable the full collection of Room Analytics metrics in Zebrix Control, several settings must be activated on Cisco endpoints. These settings ensure features such as presence detection, people counting, and acoustic analysis, even when the endpoint is not in a call. {{ .:pasted:20251226-191747.png }} Contact Zebrix support for more informations.