...
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.
Run ./install-efcx.sh for EFCX Or run ./install-cisco.sh for Cisco UCCX and UCCE.
Run the following command to ensure all the components are running.
Code Block # docker ps
In case of Cisco go to https : //VRS-IP/#/login to access the application, whereas for EFCX go to https://VRS-IP:444/#/login.
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)
Section 2
For HA (High Availability).Deployment for HA:
Requirements
NFS Server
Database with SqlServer
HA sip trunk
Two VRS on separate VMs
EFCX Server
Docker and Docker compose
Git
Follow the guide for the deployment of High Availability (HA) VRS.these steps:
Ask IPCC team for the creation of NFS server.
Mounting point of NFS on both VRS VMs is /var/vrs/recordings.
Grant full permission to this directory and any files or subdirectories created within it.
Ask the IPCC team for the configuration of HA Sip trunk and set priorities to both VRS.
Ask the IPCC team for the creation of Database (sqlserver). And add sqlcmd to the path.
Navigate to data/scripts/ inside recording-solution directory.
Run pwd command and copy the path of sqlserver.sql script
Run the following command with correct credentials. It will initialize the database.
...
Name | Description | |
---|---|---|
1 | VRS_URL | IP Address of Server at which solution is being deployed, https: //192.168.1.101 * |
2 | LOCAL_MACHINE_IP | Same IP Address as given in VRS_URL. example 192.168.1.101 * |
3 | KC_HOSTNAME | Keycloak hostname where keycloak is hosted. e.g 192.168.1.101, give FQDN in case of EFCX Keycloak |
4 | TZ | Time Zone. e.g Asia/Karachi |
5 | DEPLOYMENT_PROFILE | “CISCO“ as HA is only available for Cisco CC |
6 | PEER_ADDRESS | Address of the second VM wehre VRS is deployed |
7 | HA_MODE | Keep it true. As we are deploying high avaliability |
8 | SCREEN_RECORDING | Keep it true if you want to enable screen recording, otherwise false it |
9 | KEYCLOAK_URL | Url of the keycloak deployed for fetching user details FQDN of EFCX Server |
10 | CISCO_TYPE | Either UCCE or UCCX |
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. e.g /var/vrs/recodings/cucmRecording/sessions/ |
13 | ARCHIVED_MEDIA_FILES_EXTENSION | mp4 [keep it same] |
14 | FILE_EXTENSION | wav [keep it same] |
15 | NO_OF_DAYS | No of days before which all the files will be archived. If set 2, then except for last 2 days from the date and time of service started or triggered all the files will be archived. |
16 | SFTP_HOST | SFTP host IP for archival e.g 192.168.1.106 |
17 | SFTP_PORT | 22 |
18 | SFTP_USERNAME | Username of the SFTP server e.g expertflow |
19 | SFTP_PASSWORD | SFTP password e.g Expertflow464 |
20 | ARCHIVAL_JOB_INTERVAL | It is a duration that tells the service to trigger again. This value is in hours. For example, if set 24 the service would be triggered after 24 hrs to get the desired job done. |
21 | STEAM_DELETION_JOB_INTERVAL_HRS | Time in hours before which all the stream is to be deleted. e.g 24 |
22 | RETRY_LIMIT | limit to retry in case the connection fails. e.g 2 |
23 | ARCHIVAL_PROCESS_NODE | active |
24 | NO_OF_DEL_DAYS | No of days before which all the streams will be deleted. If set 2, then except for last 2 days from the date and time of service started or triggered all the files will be deleted. |
25 | CUCM_APPLICATION_USER_NAME | CUCM User's username that has been created in step 3. |
26 | CUCM_APPLICATION_USER_PASSWORD | Password for the CUCM Application User. |
27 | CUCM_IP | IP address where CUCM has been Deployed |
...
Name | Description | |
---|---|---|
1 | DB_DRIVER | Driver on which database is running i.e postgres or mysql drive |
2 | DB_ENGINE | Engine on which database is running i.e postgres or mysql |
3 | DB_HOST | Name or ip of the host on which database is active |
4 | DB_NAME | Name of the database |
5 | DB_USER | Username for database |
6 | DB_PASSWORD | Password for the database |
7 | DB_PORT | Port of the Database |
Update the keycloak variables
Names | ||
---|---|---|
1 | KEYCLOAK_REALM_NAME | Realm name from keycloak |
2 | KEYCLOAK_CLIENT_ID | KeyCloak client id from keycloak |
3 | KEYCLOAK_CLIENT_SECRET | Add the client secret from keycloak |
4 | KEYCLOAK_PERMISSION_GROUP | AGENT_GROUP |
5 | KEYCLOAK_URL | FQDN of CX |
6 | EFCX_FQDN | FQDN of CX |
8 | VRS_URL | Url of VRS machine |
9 | LOCAL_MACHINE_IP | IP of the local machine |
Navigate to HA directory inside recording-solution directory.
Open keep.env file and set values to environment variables
Code Block KEEPALIVED_UNICAST_PEERS=192.168.1.126 (IP address of the Second VRS) KEEPALIVED_VIRTUAL_IPS=192.168.1.245 (Assign any IP-Address which not in use) KEEPALIVED_PRIORITY=100 (Assign 100 for priority 1 and 90 for priority 2)
On the terminal run command ip addr
and find your network interface card and assign the value. Add the network interface card value keep.env.
...