Recording Deployment

Prerequisites

No-Media Integration Deployment

EXEC deployment for No-Media Integration should be up and running before the configuration required for the Recording Injection is added to the environment. See No Media Deployment for more information.

Mandatory Environment Elements 

WebDAV

WebDAV is required only for the Recording Injection. EX Engage Connector supports any standard WebDAV server. Customers should plan to use 30 GB of WebDAV memory for contact centers with 1000 concurrent recording calls.

HTTP Load Balancer

HTTP Load Balancer is required only for the Recording Injection. EX Engage Connector supports any standard HTTP load balancer.

Important

Genesys does not deploy and operate databases, WebDAV servers, or load balancers in on-premises deployments. It is the responsibility of the customer. In a production deployment, data store components (Redis) and WebDAV must be deployed outside of the Docker network and managed by the customer's DBA team. The customer's DBA team is also responsible for ensuring that the data store components are configured with the appropriate scalability, resiliency, and data protection (backups).

Virtual Machines for the EXEC Components

• A minimum of 2 VMs (N+1) for EX Engage Connector Recording Provider (EXRP)

The EXEC VM must sync the system time at least once every 24 hours as the communication between the EXEC services and Genesys Cloud are very time-sensitive.

All VMs running EX Engage Connector components should belong to the same local network segment and be interconnected so that all components can communicate over the network. EXEC components can use either FQDNs or IP addresses to establish communication with each other. The connectivity table lists both incoming and outgoing connections required by the EXEC components. 

Service	Direction	Protocol	Local Port	Remote Peer	Remote Peer Port	Purpose
EXCS	Outgoing	TCP/TLS	Any	Engage Config DB	5432 (default RDBMS listening port)	Read Engage configuration.
EXAS	Outgoing	TCP	Any	Engage Primary Stat Server	2060 ( default Primary Stat Server listening port)	Obtain real-time agent state data.
EXAS	Outgoing	TCP	Any	Engage Backup Stat Server	Backup Stat Server listening port (2060) default	Obtain real-time agent state data
EXCP	Outgoing	TCP	Any	Engage SIP Servers (multiple)	8000 (default SIP Server default listening port)	To fetch real-time Call, DN, and VQ details from SIP Server.
EXCP/EXAS	Outgoing	TCP	Any	EXCS	3640 (default)	Use EXCS REST API.
EXCS	Inbound	TCP	3640 (default)	EXCP/EXAS/Prometheus	Any	Use EXCS REST API and scrape metrics.
EXAS	Inbound	TCP	3630 (default)	Prometheus	Any	Scrape metrics.
EXCP	Inbound	TCP	3650 (default)	Prometheus	Any	Scrape metrics.
HTTP Load Balancer	Outgoing	HTTP	ANY	EXCP	3650 (default)	HTTP POST proxied by HTTP Load Balancer for delivering recording metadata.
EXCS/EXAS/EXCP	Outgoing	TCP/TLS	Any	Redis	6379 (default)	Store config data to provide ID mapping services
EXCS/EXAS/EXCP	Outgoing	HTTPS	Any	Genesys Cloud	443	Call GC REST API.

High-Level Deployment Plan

1. Execute the procedure described in the Configuring hybrid_integration transaction in CME section.
2. Download the EXRP component from Genesys FTP:
   • EXRP (exrp-100.0.100.XX.tgz) - EXRP container
3. Deploy the EXRP container to the local container registry
4. Execute the procedure described in the Configuring .env file section.
5. Execute the procedure described in the Deploying EXEC for Recording Injection page.
6. Execute the procedure described in the Starting EXEC Services section.