14.12.1 14.12.0 14.11.0 14.10.0 14.9.0 14.8.0 14.7 14.6 14.5 14.4 14.3
14.12.1 14.12.0 14.11.0 14.10.0 14.9.0 14.8.0 14.7 14.6 14.5 14.4 14.3
Breadcrumbs

Release Limitations

Following are the limitations of the features in VRS 14.12.1 (carried forward from 14.12.0 where still true):

Supervisor Role:

  • Department membership is authoritative only when agents are placed in /Departments/<name> groups.

  • Agent usernames in Keycloak must match the recording agentId values used by VRS (same identifier convention as today).

  • Service account requires view-users; if revoked, supervisor resolution fails safe to empty allowed list (no elevated access).

  • Admin and agent workflows are intentionally unchanged for backward compatibility with existing VRS clients.

UCCX Informix CRA enrichment:

  • Opt-in only for Cisco UCCX deployments that use Informix CRA. Leave disabled for UCCE and for UCCX deployments that do not use Informix CRA.

  • Not supported for EFCX.

  • Requires mixer config.env settings (UCCX_DB_ENGINE=informix, UCCX_INFORMIX_SERVER, and UCCX_DB_*). Incorrect Informix connection settings fail enrichment for new calls; they do not change UCCE enrichment.

  • Enrichment applies to new calls after the mixer is configured and restarted. Pre-upgrade recordings are not backfilled from Informix CRA.

Recording compression:

  • Compression profile changes apply only to new mixed recordings after the mixer is recreated/restarted. Existing files keep the profile used when they were mixed.

  • GSM (~90%) trades size for quality; validate playback quality for your use case before production use.

Archival (SFTP / S3-compatible):

  • Only one archival mode can be active at a time (Archive Only or Copy and Archive).

  • S3-compatible archival was verified with Wasabi; other S3-compatible endpoints follow the same configuration but may need environment-specific validation.

  • Stamped archives (with archive_storage / archive_path) play and download from that stamp. Unstamped older archives play only via the current Archival Configuration — changing storage type does not migrate files automatically.

  • Older archives (before path stamping): Play follows whatever is saved now in Archival Configuration (host/endpoint, credentials, folder). To play those recordings, set Archival Configuration in the UI to the same details used when they were archived (or move the files to the current destination). After you save the matching configuration, you can play them.

  • One SFTP and one S3 profile only: Only one SFTP connection and one S3-compatible connection are kept. If you change SFTP IP/host or credentials, or switch cloud endpoint/account (for example Wasabi → AWS), the previous connection is overwritten. To play files still on the old server or old cloud account, open Archival Configuration, enter that previous connection again, save, then play — or migrate the files to the current destination.

  • Same host / same cloud account, different folders: After path stamping, you can change the folder on the same SFTP server or same S3 account without losing play for newer archives. Play uses the path saved on each recording. You do not need to switch the UI folder back for those stamped recordings.

  • Minimum Archive Days: Archive Days / retention must be at least 2. Values below 2 are skipped or rejected by archival (MIN_RETENTION_DAYS=2).

High Availability:

  • HA deployment is not tested for VRS 14.12.1 (see Release Notes — Not tested with). Existing HA product limitations still apply; do not treat this release as an HA validation cycle.

Session Timeout:

  • If the user has multiple VRS tabs open, an expiry in one tab eventually triggers a logout/refresh in the others.