You are here: Integration > Microsoft Lync / Skype for Business > Configuring nodes to work behind NAT

Configuring Pexip Infinity nodes to work behind a NAT device

To configure your Pexip Infinity deployment to work behind a static NAT device (from the perspective of clients located on the Internet) you must:

  1. Configure the NAT device / firewall with the static, publicly-reachable IP address of each Conferencing Node that you want to be accessible from devices in the internet, and then map the public address to the node's corresponding internal IP address. Note that it must be a 1:1 NAT.
  2. Configure each publicly-reachable Conferencing Node with its IPv4 static NAT address (Platform configuration > Conferencing Nodes) i.e. the public address of the node that you have configured on the NAT device.

Note that:

  • Any Conferencing Nodes that are configured with a static NAT address must not be configured with the same System location as nodes that do not have static NAT enabled. This is to ensure that load balancing is not performed across nodes servicing external clients and nodes that can only service private IP addresses.
  • Any internal systems such as Cisco VCSs or endpoints that will send signaling and media traffic to Pexip Infinity nodes that are enabled for static NAT should send that traffic to the public address of those nodes. You must ensure that your local network allows this.
  • We do not recommend that you allow the Management Node to be accessible from devices in the public internet. However, if you want to do this, you must assign and configure the Management Node with its static NAT address. You should also configure your firewall to only allow access to the Management Node from the specific IP addresses from where you want to allow management tasks to be performed.
  • There cannot be a NAT device between any Pexip Infinity nodes.