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.0 14.11.0 14.10.0 14.9.0 14.8.0 14.7 14.6 14.5 14.4 14.3
Breadcrumbs

VRS Upgrade Guide from 14.11.0 to 14.12.0

Upgrade Cisco VRS from 14.11.0 to 14.12.0

Follow these steps in order.

This guide is for Cisco VRS. The same image-tag steps apply when you use the EFCX compose profile for your deployment. Operations Dashboard department scoping and Informix CRA enrichment apply to Cisco UCCE / UCCX (not EFCX).

Before you start

  • You have SSH/login access to the VRS server

  • You know your database type: PostgreSQL 14+ or SQL Server (Cisco vrs), or Media Server fusionpbx access (EFCX)

  • You have already completed the 14.10.0 → 14.11.0 upgrade (including Keycloak evaluatetag and supervisor /Departments setup if you use those features)

Step 1 — Backup your settings and database

  1. Back up config.env and any custom compose overrides.

  2. Take a full database backup before you change image tags: Cisco — PostgreSQL or SQL Server database vrs; EFCX — Media Server database fusionpbx.

Step 2 — Stop VRS

Stop the running VRS stack with your usual compose/stop procedure for this deployment.

Step 3 — Get the 14.12.0 files

Update the VRS image tags in docker-compose.yml (and related compose files) to 14.12.0 for the components your deployment uses (front-end, APIs, mixer, archival-process, and other services as shipped for this release).

Step 4 — Keycloak (supervisors)

No new realm roles are required for 14.12.0.

  • Keep supervisor assigned to supervisor users.

  • Keep supervisors and agents in the same /Departments/<name> groups.

  • Keep service-account view-users (and typically query-users / query-groups) on the vrs client — required for Media Recordings and Operations Dashboard department scoping from 14.12.0.

Details: Setup Keycloak for VRS.

Step 5 — UCCX Informix CRA (optional)

If this is a UCCX deployment and you want wrap-up, CSQ/queue, hold time, and call variables enriched from Informix CRA, set the opt-in mixer variables in docker/config.env:

  • UCCX_DB_ENGINE=informix

  • UCCX_INFORMIX_SERVER (same INFORMIXSERVER as cisco-connector CC_SERVER)

  • UCCX_DB_HOST, UCCX_DB_NAME, UCCX_DB_USER, UCCX_DB_PASSWORD (and optional UCCX_DB_PORT, default 1504 for informix)

Full descriptions: Installation Guide — UCCX Informix CRA enrichment section. Leave these unset / leave UCCX_DB_ENGINE at the sqlserver default for UCCE or when Informix CRA is not used. Recreate/restart the mixer after changes.

Step 6 — Recording compression (optional)

If you want a compression profile other than the previous ~50% default, set the profile in docker/config.env, then recreate/restart the mixer. See Recording Compression — Operator Guide.

Step 7 — Archival storage (optional)

Cisco

Dual archival columns for Cisco are already in the recording-solution skeleton (data/scripts/postgres.sql / sqlserver.sql on vrs). If you use archival, keep SFTP or configure S3 / MinIO (S3-compatible; verified with Wasabi) in Archival Configuration, then restart archival-process. See Archival Service.

EFCX

EFCX dual archival schema is not in the skeleton. Before restarting archival-process, run the fusionpbx SQL on the Media Server (same commands as the Installation Guide EFCX deploy step). Full connect steps and SQL: Archival Process Configuration for EFCX (section Dual archival schema on fusionpbx), or the EFCX-gated step in the Installation Guide.

Then configure SFTP or S3-compatible settings for the EFCX archival process and restart archival-process.

Step 8 — Start VRS again

Start the stack and confirm containers are healthy.

Step 9 — Open VRS in the browser

  • As a supervisor, open Operations Dashboard and confirm metrics match only your department agents (not the full tenant).

  • For UCCX with Informix enabled, place a test call and confirm wrap-up / queue / hold / call variables after the usual sync delay.

  • If you changed compression, place a new test call and confirm size/quality.

  • If you configured archival, confirm the next archival run uploads to the selected destination and that play/download still work.

What this upgrade gives you

  • Operations Dashboard scoped to supervisor departments

  • UCCX Informix CRA enrichment when enabled; formal UCCX testing

  • Configurable recording compression (~50% / ~75% PCM, or ~90% GSM)

  • Archival to SFTP or S3-compatible cloud (S3 / MinIO / Wasabi)

  • EFCX: manual fusionpbx dual-archival schema (Cisco uses skeleton SQL on vrs)

Rollback

Restore the previous image tags and database backup, then start the stack again.

See also: Release Notes.