Cisco Webex Teams
Cisco Webex Teams is an app-centric, cloud-based service that provides a complete collaboration suite for teams to create, meet, message, call, care, white board, and share, regardless of whether they’re together or apart—in one continuous workstream before, during, and after meetings. It is built to help teams work seamlessly. It is simple, secure, complete, and open, and provides a space for people to work better. The core capabilities of Cisco Spark are Meetings, Messaging, and Calling. The Cisco Webex Teams platform, app-centric design, hybrid services, and architecture of Cisco Webex Teams create a unique and differentiated service.
For more information on the solution, refer to the Cisco Webex Teams website at https://www.cisco.com/c/en_uk/solutions/collaboration/webex-teams.html
Cisco Webex Teams provides an API that Verba is able to use to retrieve content from Webex Teams rooms.
For a general description of Verba Import sources, please refer to Import sources.
Recording is supported for the following modalities:
- Instant Messaging
- File Transfer
Creating the Integration on the Cisco Webex Teams side
The integration needs to be set up in Cisco Webex Teams for it to allow connections for the Verba servers to the company's Webex Teams instance.
Follow the steps below to add Verba as a trusted source in Cisco Webex Teams.
Step 1 - Navigate to the Cisco Webex Teams developer page at https://developer.webex.com/
Step 2 - Click on the My Apps link at the top-right corner.
Step 3 - Click on the green Add button.
Step 4 - Click on the Create an Integration button
Step 5 - Fill out the textboxes according to the table below.
Configuration item | Description |
|---|---|
| Name | Name the integration. This name will identify this integration in your Cisco Webex Teams environment |
| Contact Email | Set up a contact email. Certain messages may be sent as notifications to this email address |
| Icon | Select an icon |
| Description | Describe the integration |
| Redirect URI(S) | Set up the Verba server's hostname or IP address and port number in the following format: https://verbaserver.company.com:4000 This address and port is only used during authorization and needs to be accessible from the desktop computer used during the configuration. After successful authorization, this port is no longer used, the Verba servers will connect to Webex Teams directly. |
| Scopes | Select the following 3 scopes:
|
Step 6 - Click on the Create Integration button.
At this point, the integration's page refreshes and at the bottom, you are presented with the automatically generated OAuth login parameters. The Id and the Secret shown here will need to be specified when configuring the integration on the Verba side.
Step 7 - Configure the Verba side integration as shown in the next section. This is important, as Step 9 can only be performed if the Spark Import Source is already configured on the Verba side.
Step 8 - In the OAuth Authorization URL section, a URL is presented. Open this URL in the browser.
Step 9 - At this point, you are presented with the prompt below to give access to the application. Click on the Accept button.
If the following page appears, then the integration is successful.
If you receive an error here, please make sure that your Spark Import Source is correctly configured in Verba and try again.
Creating a Cisco Webex Teams import source
Follow the steps below to create a new Verba Import source for Cisco Webex Teams.
Step 1 - Open the Verba Web interface then select Data > Import Sources from the top menu
Step 2 - Click on the Add New Import Source link on the top right
Step 3 - Complete the configuration according to the requirements in the following table
Configuration item | Description |
|---|---|
| Name | Name your import source. This name will identify this source across the system |
| Type | Select Cisco Spark |
| Spark Integration Client Id | Enter the Client Id that is shown in Step 7 of the previous section (Creating the Integration on the Cisco Spark side) |
| Spark Integration Client Secret | Enter the Client Secret that is shown in Step 7 of the previous section (Creating the Integration on the Cisco Spark side) |
| Redirect URI | Enter the hostname or IP address of the Verba server. The same address needs to be used as the setting that was configured in Step 5 of the previous section (Creating the Integration on the Cisco Spark side) |
| Listener Port | Enter the port where the Verba server is listening. The same aport needs to be used as the setting that was configured in Step 5 of the previous section (Creating the Integration on the Cisco Spark side) |
| TLS Certificate File / Thumbprint | Specify the certificate file / certificate thumbprint that is being used for the Cisco Webex Teams connection. If left empty then the Verba default certificate will be used |
| TLS Key File | Specify the file where the certificate key is stored if not in the windows certificate store |
| TLS Key Password | Specify the password for the file that contains the certificate keys |
| TLS Trust List | Specify the list of certificates that Verba trusts from a 3rd-party connection. Available options:
|
Step 4 - Click Save to save the settings
Import policy configuration
Follow the steps below to configure the Data Import action:
Step 1 - In the Verba web interface, navigate to Data > Data Management Policies
Step 2 - Click on the Add New Data Management Policy button at the top-right corner of the page
Step 3 - For the action, select Data Import
Step 4 - Under Available Import Sources, select the Import Source that you created, then click on the Add button just below the text field
Step 5 - Configure the policy details, based on the information that is shown in the configuration items summary table below
Step 6 - Click on Save
| Configuration Parameter Name | Description |
|---|---|
| Enable Recording Rules | Specifies if all data should be processed in the imported data set or just the records of the recorded users as configured in Verba |
| Execute Only on Selected Servers | If enabled, a specific server can be chosen that will run this policy |