| Status | ||||||
|---|---|---|---|---|---|---|
|
...
Follow the steps below to create a new Verba Import source for Zoom:
Step 1 - Open the Verba Web interface then select Data / Import Sources from the top menu
...
| Name | Description |
|---|---|
| API Key | The Zoom API key associated with the Zoom application registered earlier |
| API Secret | The Zoom API secret associated with your Zoom application registered earlier |
| Forward Proxy Address | IP of the forward proxy server. If left empty, no attempt is made for establishing a forward proxy connection. |
| Forward Proxy Port | Port for the forward proxy connection. |
| Forward Proxy User | Username for authenticating with the Forward Proxy. If left empty, authentication is omitted. |
| Forward Proxy Password | Password for authenticating with the Forward Proxy. |
| API Address | The base URL of the Zoom API |
TLS Certificate File / Thumbprint | Specify the certificate file / certificate thumbprint that is being used for the Zoom API 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:
|
...
- Zoom Phone: to control which user recordings have to be downloaded and archived, and to match the imported conversations to an extension (and to a user account) you need to add the Zoom user phone extension numbers (not the Zoom user ID) as extensions with type Number User / AddressAgent ID.
- Zoom Meeting: to control which user recordings have to be downloaded and archived, and to match the imported conversations to an extension (and to a user account) you need to add the Zoom user ID as extensions with type User / Agent ID.
...