Settings for the Cisco Webex Meeting Audio Capture Adapter

The following settings are for the audio capture adapter:

Specify the following required parameters:
1. Adapter Name: Required. A unique name for this adapter. Do not use the following characters, which are reserved for XML tagging: < > $ & ' ".
2. Description: Optional. Enter a description for this adapter.
3. DataSource: The related Application data source.
4. Client ID: The client ID created in Developer Portal for the Verint application that is registered to access the Cisco Webex API.
5. Client Secret: The client secret created for the registered application to access the Cisco Webex API.
6. Refresh Token: The refresh token is used to generate a short-lived access token, which allows Verint to access the Cisco Webex API.
  
  The Verint adapter regularly retrieves the refresh token, which automatically refreshes the access token before it expires. The access token usually expires in 12 hours. Each time the tokens are retrieved, their expiration resets to the initial value. Refreshing the token reduces the overall volume of Authentication API requests made to the Cisco Webex API.
7. API Server Address: The API endpoint destination is api.zoom.us.
8. Authentication Server Address: Address used to refresh authentication status of the adapter is api.zoom.us/oauth/token.
If you are advised by Verint support, configure the following parameters:
1. Startup Type: How the adapter behaves after the host server restarts. The options are:
  - Automatic: Default. The adapter starts automatically when the host server starts.
  - Manual. The adapter starts only when a user clicks the Start button.
  - Disabled. The adapter does not run when the host server starts.
2. Polling frequency (minutes): How often the adapter requests closed interactions from the Cisco Webex Meetings application. The default is 5 minutes.
3. Polling time window (hours): The amount of time, starting from the current moment and extending into the past, that the adapter requests closed interactions from the application. The default is 12 hours.
  
  Example:
  
  When the Polling Time Window is set to 12 hours, the adapter requests all closed interactions between now and 12 hours previously.
  
  If you notice that interactions are consistently missing from Verint, it may be that closed interactions take longer to be saved in the application's database. If this happens, change the Polling Time Window to an amount of time greater than the maximum expected delay.
4. Time interval for triggering purging (minutes): How often to check for events to purge from the event store. The default is 10 minutes.
5. Timespan for purging (hours): Interaction Capture saves the events it receives on an internal store. This event store needs to be purged periodically to prevent unnecessary growth.
  
  The Timespan for purging parameter defines the age of events to delete permanently from the event store. The default is 24 hours.
  
  Example:
  
  When Timespan for purging is 24 hours, event data older than 24 hours is deleted when the Time interval for triggering purging setting is triggered.
6. Recovery time window (hours): After the adapter starts, it enters Recovery mode to check for missed recordings. The Recovery time window is the amount of time that the adapter requests closed interactions. It starts from the time of the last ingested interaction (watermark) and extends into the past according to the time window. The default is 24 hours.
  
  The adapter remains in recovery mode until all missed recordings are retrieved, then it switches to Normal mode, which uses the Polling time window to check for closed interactions.
7. Recovery Polling frequency (minutes): How often the adapter requests closed interactions when in Recovery mode. The default is 5 minutes.

What to do next

Search and replay interactions for Cisco Webex Meetings