Installation Steps
Internet should be available on the machine where the application is being installed and connections on port 9242 should be allowed in the network firewall to carry out the installation steps.
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.
Allow ports in the firewall
If there is an active firewall, allow following ports.
443/tcp 8088/tcp 5060/tcp 16386-32768/udp
Installation Steps
- Follow this guide to install and configure Freeswitch
- Please make sure that Solution Prerequisites are met for the desired deployment type.
- Download the deployment script deployment.sh and place it in the user home or any desired directory. This script will:
- delete the recording-solution directory if it exists.
- clone the required files for deployment
To execute the script, give it the execute permissions and execute it. This command will clone the skeleton project for recording solution. the recording-solution directory contains all the required files for deployment.
$ chmod 755 deployment.sh $ ./deployment.sh
- Create MySQL database schema for vrs using the script located in recording-solution/data/init.sql. This is an sql script which creates a database with name vrs and the required tables. Run this as an sql script/query in MySQL (For non-HA deployment)
- Open recording-solution/docker/config.env and update the following environment variable
Name Description 1 VRS_URL https://192.168.1.101 [IP of a local machine]
2 LOCAL_MACHINE_IP 192.168.1.101 [local machine IP since it is a non-HA deployment]
3 KC_HOSTNAME Keycloak hostname e.g 192.168.1.101 4 TZ Asia/Karachi 5 TRUST_STORE_PATH /app/ssl/truststore.jks
keep it same
6 TRUST_STORE_PASSWORD Expertflow464 7 CCX_PRIMARY_IP Primary UCCX IP e.g 192.168.1.33 8 CCX_SECONDARY_IP Secondary UCCX IP e.g 192.168.1.33 9 CCX_ADMIN_USERNAME CCX Admin username 10 CCX_ADMIN_PASSWORD CCX Admin password 11 FINESSE_URL https://uccx12-5p.ucce.ipcc:8445 12 DIRECTORY_PATH_TO_MONITOR The path for archival process to monitor, it should be the same path where sessions are kept, mostly /home/efadmin/cucmRecording/sessions/ OR /usr/share/freeswitch/cucmRecording/sessions/ 13 ARCHIVED_MEDIA_FILES_EXTENSION mp4 #keep it same 14 FILE_EXTENSION wav #keep it same 15 NO_OF_DAYS 1 16 SFTP_HOST SFTP host IP for archival e.g 192.168.1.106 17 SFTP_PORT 22 18 SFTP_USERNAME User name of the sftp server e.g expertflow 19 SFTP_PASSWORD SFTP password e.g Expertflow464 20 ARCHIVAL_JOB_INTERVAL 15 21 STEAM_DELETION_JOB_INTERVAL_HRS
24 22 RETRY_LIMIT 2 23 ARCHIVAL_PROCESS_NODE active 24 NO_OF_DEL_DAYS 2 25 KEYCLOAK_CLIENT_ID Name of the client e.g vrs 26 KEYCLOAK_CLIENT_SECRET
27 KEYCLOAK_REALM_NAME
Name of the realm e.g vrs 28 KEYCLOAK_PERMISSION_GROUP
Permission group e.g AGENT_GROUP Navigate to recording solution directory and execute the following commands:
# chmod 755 install.sh # ./install.sh
Verify all the containers are up and healthy
- Verify if keycloak container is healthy (docker ps), if it is on restarting, kill (docker kill keycloak) and remove (docker rm keycloak) the keycloak container then run ./install.sh. Wait for keycloak container to become healthy.
- Set up keycloak
Once keycloak is set up, update below environment variables in
recording-solution/docker/config.env
file.Name Description 1 KEYCLOAK_REALM_NAME Realm name created in step 4 of keycloak setup 2 KEYCLOAK_CLIENT_ID Keycloak client id from step 6 of keycloak setup 3 KEYCLOAK_CLIENT_SECRET Keycloak client secret from step 8 of keycloak setup 4 KEYCLOAK_PERMISSION_GROUP Keep it same - To update the self signed certificates for VRS, get the public authority or domain signed certificate .crt and .key files, name them server.crt and server.key and replace the files in /recording-solution/config/certificates with these two new files. Names should be exactly same.
- Run ./install.sh again
Run the following command to ensure that all the components are up and running.
# docker ps
- Go to https://VRS-IP/#/login to access the application.
- Configure SIP trunk to enable CUCM to send SIP events to VRS for call recordings. Two sip trunks should be configured in case of HA.