Server and network requirements

This topic summarizes the host server and network requirements when deploying Pexip Infinity.

Host servers

The Management Node and Conferencing Nodes are virtual machines (VMs) that run on industry-standard host servers. A Management Node can run on the same host server as a Conferencing Node. Other Conferencing Nodes can run on host servers in the same or different locations, allowing you to create a globally distributed system.

Our Server design guidelines help you choose and configure appropriate servers on which to host your Management Node and Conferencing Nodes.

Network requirements

Depending on your network deployment scenario, you may have to configure your system to operate behind a static NAT and to ensure that traffic can be routed between nodes. See Network deployment options and Network routing and addressing options for Conferencing Nodes for more information about the requirements and implications of your deployment scenario.

Note that in all Pexip Infinity deployment scenarios:

  • The Management Node must be able to reach all Conferencing Nodes (Proxying Edge Nodes and Transcoding Conferencing Nodes) and vice versa.
  • Each Conferencing Node must be able to reach every other Conferencing Node (Proxying Edge Nodes and Transcoding Conferencing Nodes), except:
    • When a location contains Proxying Edge Nodes, those nodes only require IPsec connectivity with:

      • any other proxying nodes in that location
      • all nodes in the transcoding location, and the primary and secondary overflow locations that are associated with that location
      • the Management Node.

      This means that the proxying nodes in one location do not need to have a direct network connection to other proxying nodes in other locations.

  • Any internal firewalls must be configured to allow UDP port 500 and traffic using IP protocol 50 (ESP) in both directions between all Pexip nodes.
  • There cannot be a NAT between any Pexip nodes.

NTP servers

Pexip Infinity uses NTP servers to obtain accurate system time. This is necessary to ensure correct operation, including configuration replication and log timestamps.

All host servers must be synchronized with accurate time before you install the Management Node or Conferencing Nodes on them.

NTP must be enabled on the Management Node VM before you deploy any Conferencing Nodes (this is done during installation of the Management Node).

We strongly recommend that you configure at least three distinct NTP servers or NTP server pools on all your host servers and the Management Node itself. This ensures that log entries from all nodes are properly synchronized.

The VMs hosting the Management Node and Conferencing Nodes use the UTC timezone, and all logs are in UTC. Do not attempt to change the timezone on these systems. Note however that the administrator web interface uses your local time. For more information, see Timezones.

DNS servers

Pexip Infinity uses DNS to resolve the hostnames of external system components including NTP servers, syslog servers, SNMP servers and web proxies. It is also used for call routing purposes — SIP proxies, gatekeepers, external call control and conferencing systems and so on. The address of at least one DNS server must be added to your system.

After configuring the DNS servers available to your system, you should assign appropriate DNS servers to each location (Platform > Locations). Each Conferencing Node in that location will then use those DNS servers.

Using a VPN to connect to Pexip Infinity

Pexip Infinity is designed to remove the need for Virtual Private Networks (VPNs). We recommend that you deploy Proxying Edge Nodes to enable external connectivity to your enterprise deployment, instead of asking users to connect to internally-located nodes over a VPN. In most cases, connections to Pexip Infinity over a VPN work successfully, but in some cases a lower MTU may be required, or it could lead to UDP media being TCP encapsulated which can cause additional latency.

Call control

If your deployment includes a call control system, it must be configured to route calls to Pexip Infinity appropriately. The exact configuration will depend on your deployment and dial plan, but in general calls placed from an endpoint to a Virtual Meeting Room alias should be routed to the endpoint's local Conferencing Nodes. For more information, see Implementing a dial plan.

Skype for Business server

If your deployment includes on-premises Skype for Business, you must set up static routes to domains used by Pexip Infinity aliases. For more information, see Skype for Business with Pexip Infinity.