When editing an existing media, this field is read-only.

A name for the media. The name must be unique.

This field is required.

The full network path for the media. This field is required.

• Amazon AWS URL: The URL to the Amazon AWS server provided to the customer when they open their object storage hosted service account. Windows HTTP proxies cannot be used to connect to the Amazon AWS resources; however, HTTP proxies for accessing Amazon AWS URL V4 buckets can be configured using environment variables on the Archive server. See Amazon AWS URL and HTTP proxy connections.

• Azure Blob Storage: The path in the blob storage. Default is 2019/10/30/11. Maximum 24 characters. Value included here must be a valid path with a path separator, /, such as calls/video. Example: If the Path setting is calls/video, the blob storage uses the path hierarchy, calls/video/2019/10/30/11. If the Path setting is blank, the path used is 2019/10/30/11.

• Centera: The path must include the connection string. See EMC Centera Connection String examples for details.

• Hitachi HCP: The path is a URL in the following format:

  http(s)://namespace.tenant.HitachiserverFQDN

  For example: https://archive1.tenant1.hcp.labs.local

  In the example:

  • archive1 is the namespace to which the media is written
    

  • tenant1 is the tenant that owns the namespace

  • hcp.labs.local is the FQDN of the Hitachi server

• SAN/Hard Drive: The path can be a full UNC path including leading \\, or can start with a local or mapped drive letter. If you use a fileshare path, the archive processes need sufficient access and permissions to read/write/delete from that path. Run the Archive service under a named Windows account (not LocalRecording) with rights to the share.

• Google Cloud Storage: Enter the path on the GCS server to which the export results are uploaded. The path value entered here is a part of the full path.

  For example, a full path has the format gs://<Bucket name>/<Path>

  An example of a full path is gs://archive-export-verint/connect/chat-storage/ChatTranscripts.

  In this example, /connect/chat-storage/ChatTranscripts is the path. The bucket name is archive-export-verint.

Suspends the deletion of archived interactions on any Archive Drive defined with this media. Using the Override Expiry setting prevents all interactions from being deleted from the time it is set. This setting prevents all interactions from being deleted regardless of the value in the Days to Keep New Calls in Archive setting in the Archive Drive definition in Recorder Manager. Once the option is cleared, typical operation resumes and interactions are deleted based on the Days to Keep New Calls in Archive setting.

Trading Database Only. Archiver raises an alarm when Override Expiry is set. When Override Expiry is set on any media, call metadata is not purged from the database. Make sure that there is enough space for the database to grow.

Enter the name of the FTP server. Required for FTP.

• For FTP, enter a valid User Name to access the FTP server. This field is required

• For Hitachi HCP server, enter the user name of the tenant that has access to the namespace to which media is written. This field is required.

To display a dialog, click the icon to the right of the field. Enter theThe appropriate password for the FTP or Hitachi HCP server user name specified above, then enter it again to confirm it. Click Set. The password is masked. This field is required.

The authentication mode: V2 (AWS Signature Version 2) or V4 (AWS Signature Version 4).

The default is V2.

The Amazon S3 bucket (or vault) name. The name is provided at the time a user requests a new bucket. In some implementations, the term One to five words that are meaningful to a specific type of business, or phrases that stand out in interactions in Speech and Text Analytics. bucket and vault are synonymous.

When AWS Signature Version 4 is selected, you can choose the authentication type to use: Access Key or Role.

When AWS Signature Version 2 is selected, Access Key is the only authentication type allowed.

This field appears only when Access Key is the selected Authentication Type.

Enter the Access Key of the identity you are using to send the archiving request.

The Access Key ID is provided by the customer.

This field appears only when Access Key is the selected Authentication Type.

The S3 Access Key is used to calculate the signature of an archiving request.

The Secret Access Key is provided by the customer.

This field appears only when Role is the selected Authentication Type.

Name of the IAM role used to authenticate access to the media.

Name of the storage account from portal Home page or main UI access point for all WFO applications..azure.com. Value is 3–24 characters. Required.

Access key to use to authenticate the recorder when making requests to the storage account. The 108-character key is available in the Azure Portal at Settings/Access keys. Required.

Name of the container in which to archive. Maximum 63 characters. Required.

Protocol to use for the connection, http or https (recommended). Required.

The GCS bucket name to which interactions are exported. Buckets are the basic GCS containers that hold data. Everything stored in GCS must be contained in a bucket. You can use buckets to organize data and control access to data, but unlike directories and folders, you cannot nest buckets.

• Bucket names can only contain lower-case letters, numeric characters, dashes (-), underscores (_), and dots (.). Spaces are not allowed.

• Bucket names must start and end with a number or letter.

• Bucket names must contain from 3 to 63 characters. Names containing dots can contain up to 222 characters, but each dot-separated component can be no longer than 63 characters.

• Bucket names cannot be represented as an IP address in dotted-decimal notation (for example, 192.168.5.4.

• Bucket names cannot contain "google" or the prefix "goog".

You can choose between two authentication types: Service account authentication or Implicit authentication.

• Service account authentication - Provides accessing of private data on behalf of a service account outside Google cloud environments. To use this authentication, you must create a Google cloud platform Predefined logical group of server roles installed together on a physical server. service account and download its private key as a JSON file. A client passes the JSON file to Google Cloud Client Libraries to authenticate at run time.

• Implicit authentication - Provides accessing of private data on behalf of a service account inside Google Cloud environments.

  With this authentication type, when an application runs inside a Google cloud environment, the application uses the service account provided by the environment. Google Cloud Client Libraries automatically find and use the service account credentials by using the GOOGLE_APPLICATION_CREDENTIALS environment variable.

This field is used only when Service account is selected as the Authentication Type. This private key is a JSON file that is required for service account authentication.

The private key (JSON file) can be created and downloaded from a Google Cloud Platform service account.

Select this option if you want to allow a user(s) to authenticate into the system using the Google Cloud Platform service account that is specified in the Target principal field. Typically, the service account that is impersonated (specified in the Target principal field) has greater access to the system than the service accounts associated with individual users.

For example, you can have an account set up that has full access to the system that exists to support impersonation. A user can log in using their own account, and if impersonation is configured for that user, the user is granted full access to the system.

To configure impersonation for a user, the user must have their account specified in the service account that is impersonated. Users whose accounts are not specified in the service account that is impersonated cannot use this feature.

Impersonation is a security feature that allows you to limit high-level access to the system to a few selected users.