3 Install the RTP Proxy
After installing the Media Flow Engine, next install the RTP Proxy.
Before installing the RTP Proxy, verify your system matches the requirements.
| Hypervisor | KVM/QEMU |
| Host OS | Oracle Linux 9 (UEK kernel recommended) |
| Guest OS | Oracle Linux 9 (x86_64) |
| Host NICs | Intel (E810/X710/XL710) or Mellanox/NVIDIA (ConnectXâ5/6) with SR-IOV |
| Guest NICs | 1 (virtio) |
| Access | Root access |
| vCPUs per VM | 12 (16 recommended) |
| RAM per VM | 16 - 48GB |
| Storage per VM | 40GB |
| SR-IOV VFs per VM | 2 |
| Java | JDK 25 |
- NTP or chrony must be enabled on both the hosts and guests VMs.
- There must not be any layer 3 device between the active and standby RTP proxy nodes; L2 adjacency is required for VIP failover and gratuitous ARP propagation.
In failover scenarios, the standby node takes over the virtual IP and sends GARP (Gratuitous ARP) announcements. These GARP messages update the MAC/IP association of the VIP on the network, ensuring continuity of RTP stream delivery. Switches and connected infrastructure must not block or filter GARP messages, and should support fast MAC address table updates. Port security mechanisms (such as sticky MAC or dynamic ARP inspection) must allow legitimate MAC moves and GARP updates to prevent disruption during failover.
Receiver Side Scaling (RSS) must be enabled on every NIC to ensure performance.