Using Infinity Connect from outside your network
In most cases, your Pexip Infinity deployment will be located inside a private network. If this is the case and you wish to allow Infinity Connect users who are located outside your network (for example on another organization's network, from their home network, or the public internet) to connect to your deployment, note that:
- Internet Explorer and Safari browsers use the RTMP protocol and can connect via a reverse proxy, but they cannot establish audio/video paths to Pexip Infinity via a TURN server. To establish audio/video media connectivity, RTMP clients need a direct TCP connection to a Conferencing Node. The Web App will attempt an encrypted RTMPS connection first. For a secure RTMP connection to be established, the SIP TLS FQDN must be configured on the Conferencing Node (via ) and it must match the Common Name of its TLS server certificate. If RTMPS fails, it will use an unencrypted connection for media.
- Chrome, Firefox and Opera browsers use the WebRTC protocol and can connect to privately-addressed "on-premises" nodes via a reverse proxy and route their media through a TURN server.
Note that Microsoft Edge browsers (which are WebRTC-compatible) cannot currently use STUN and thus cannot send media to Pexip Infinity via a TURN server.
This means that Internet Explorer, Edge and Safari users connecting from outside your network will not be able to send or receive media. These users should connect over a VPN, or use another browser.
For more information, see Pexip Reverse Proxy and TURN Server.