RT Socket connection requirements

Last Updated : Oct 29, 2025 |

To create and run skill-based campaigns, you must configure the RT_socket package, which provides a TCP stream socket real- time interface from CMS. Each POM node in the deployment requires at least one dedicated incoming RT-Socket connection from CMS.

While configuring the RT Socket to send CMS real time data to POM server, ensure you use the tvi1 report format and that there are enough rt_socket sessions configured to account for each reachable POM node on your deployment.

Note:

For High Availability deployments, the HACMS parameters must be set to true in the rta.conf file. You can configure all CMSs to use the same port. In the POM CMS configuration, you can configure using the same port for all connections.

The following are the few example scenarios for RT Socket connection configuration based on the default deployment types:

  • If your deployment only includes CMS High Availability:

    • Configure one connection between the primary CMS and each POM server in the data center

    • Configure one connection between the secondary CMS and each POM server in the data center

  • If your deployment only includes POM Geo-Redundancy:

    • Configure one connection between CMS and each POM server in Data Center 1

    • Configure one connection between CMS and each POM server in Data Center 2

  • If your deployment includes CMS High Availability and POM Geo-Redundancy:

    • Configure one connection between the primary CMS and each POM server in Data Center 1

    • Configure one connection between the secondary CMS and each POM server in Data Center 1

    • Configure one connection between the primary CMS and each POM server in Data Center 2

    • Configure one connection between the secondary CMS and each POM server in Data Center 2