Deploy a load balancer

Deploy a load balancer to manage traffic and to improve the availability and scalability of your recording solution. A load balancer forwards the audio streaming requests from Twilio Flex to the Verint Recorder Adapter Proxy Service servers.

You can use any load balancer that meets the following general requirements:

Get a public IP or host name for the load balancer, which can be set to the Connection URI when you are setting up a new recording solution integration on the Twilio Flex portal. The Twilio Flex client can then connect to this public IP (or host name).
Get an SSL certificate signed by a public Certificate Authority (CA), which is required on the load balancing server. Twilio Flex then only allows connections to the public IP or host name through TLS and to any host that presents a certificate signed by a public CA.
Add target RAPS servers to the pool of servers to which the load balancer can forward traffic.
Provide a way to make requests for a health check on each node. Use the path /twilio/v1/health. Only one healthy node in the pool can receive each WebSocket connection and requests that follow.

The Verint Cloud system provides load balancing using the AWS load balancing service. If you have a Verint on-premises deployment, you can use an on-premises balancer, or a cloud balancer, such as the Azure Application Gateway, or Amazon Web Services load balancing.