Page Comparison

...

443/tcp
8088/tcp
5060/tcp (only for Cisco)
16386-32768/udp (only for Cisco)

Installation Steps

1. Please make sure that Solution Prerequisites are met for the desired deployment type. 

2. Download the deployment script

   View file
   name deployment.sh

    and place it in the user’s home or any desired directory. This script will:

   1. delete the recording-solution directory if it exists.

   2. clone the required files for deployment

3. To execute the script, give it the execute permissions and execute it. This command will clone the skeleton project for the recording solution. the recording-solution directory contains all the required files for deployment.

   Code Block
   language bash
   $ chmod 755 deployment.sh $ ./deployment.sh

4. Follow step 5 to 8 for deployment with Cisco UCCX or UCCE

5. Follow this guide to install and configure Freeswitch. The recording path should be /usr/share/freeswitch/cucmRecording

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

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

...

6. Navigate to the recording solution directory and execute the following commands:

   Code Block
   chmod 755 install.sh #for UCCX and UCCE run ./install-cisco.sh

   Verify all the containers are up and healthy 

7. Verify if the 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.

8. Set up keycloak

9. Once keycloak is set up, update the below environment variables in the 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

10. 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 the same.

11.  Run ./install-efcx.sh for EFCX Or run ./install-cisco.sh for UCCX and UCCE.

12. Run the following command to ensure all the components are running. 

    Code Block
    # docker ps

13. Go to https : //VRS-IP/#/login to access the application.

14. Configure the SIP trunk to enable CUCM to send SIP events to VRS for call recordings. Two sip trunks should be configured in case of HA. (Not for EFCX)
    
    

...