Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Note

All the commands start with a # indicating that root user privileges are required to execute these commands. Trailing # is not a part of the command.

Requirements

  • Replay Server for HA

  • SQL Server 2019

  • Two SIP Trunk for HA

  • VRS solution on two separate machines for HA

  • EFCX Server (for KeyCloak)

  • Docker and Docker compose

  • Git

...

There are two types of installation: EFCX and Cisco (UCCX & UCCE). For EFCX, most of the steps are not required, as Keycloak, JtapiConnector, and Mixer are not required.

...

  1. For Non HA or HA (High Availability) Deployment follow these steps.

  2. Follow this guide to install and configure Freeswitch. The recording path in Free SWITCH and in docker compose volume must be same.

  3. Follow this guide to configure ESL. (for Pause and Resume Recording)

  4. Follow this guide to create an application user on CUCM for jtapi-connector.

  5. Create a database in SQL Server for VRS with the name vrs and run the SQL script (sqlserver.sql) located in recording-solution/data/scripts. This script will generate the required database tables.

  6. Open recording-solution/docker/config.env and update the environment variables given below.

...

  1. Save changes and exit.

  2. Run ./install-cisco.sh

  3. Check containers on both recorders using docker ps command

  4. Deploy the Recorder 2 in the same way.

  5. Deploy the replay server. For replay server just add the config.env file. and run the ./install-replay.sh command.

Section 2

Deployment for HA:

Requirements

  • Replay Server

  • SQL Server 2019

  • Two SIP Trunk (HA Mode)

  • VRS solution on two separate machines

  • EFCX Server (for KeyCloak)

  • Docker and Docker compose

  • Git

Follow these steps:

  1. Follow this guide for the creation of rsync job and follow next two steps.

Make sure mounting point of rsync is /var/vrs/recordings on all three VMs; two VRS, and a Replay Server. Grant full permission to this /var/vrs/recordings directory and its subdirectories created within it.

  1. Configure two SIP Trunks on Cisco Call Manager in HA Mode and set priorities for both Machines.

  2. Create a database in SQL Server for VRS with the name vrs and run the SQL script (sqlserver.sql) located in recording-solution/data/scripts. This script will generate the required database tables.

  3. Follow this guide to install and configure Freeswitch. The recording path should be /var/vrs/recordings/cucmRecording

  4. Follow this guide to create an application user on CUCM for jtapi-connector.

  5. Change the recording path and other variables as per your configuration. Open docker-compose-cisco inside /recording-solution/docker/

  6. Open recoding-solution/docker/docker-compose-cisco

  7. Inside docker-compose-cisco file, Uncomment the Consul Container.

  8. In container_name vairable set the name as consul1 for Recorder 1 and consult2 for recorder 2.

Make sure in docker-compose-cisco consul <container_name: consul1> name must be different for both VMs.

...

Now, run the install script. ./install-cisco.sh

...

After all Docker containers are up, go to this URL to access the VRS Web Application: https://IP-Address/#/login.

...

Since most of the configurations are the same. Clone the recording-solution folder on second Recorder and Replay Server

...

Adjust the consul container name in recoding-solution/docker/docker-compose-cisco and config.env on second Recorder.

...

Run the ./install-cisco.sh on the second recorder machine

...

Adjust the config.env on replay server. Database environment, recording directory path should be same on replay server as both Recorders have.

...

  1. .

...