Show only results for:












Setup ICE Server

The ICE Server help the client connect to the renderserver. This is done by passing setting up a TURN/STUN server for address/port resolution and proxying for the WebRTC protocol.

Requirements

  • Ensure that ports 3478TCP/UDP are open to clients and renderservers
    • It is possible to use different ports
  • Ensure that ports 50000-51000UDP are open to clients and renderservers
    • It is possible to use different port ranges
  • Windows host for CAXturn

Setup

During the installation CAXturn will be provided to you with a sample configuration file.

Configuration

{
    "publicIp": "1.1.1.1",
    "username": "1234",
    "password": "5678",
    "realm": "caxnet",
    "minPort": 50000,
    "maxPort": 51000,

    "enableTCP": true,
    "tcpPort": 3478,

    "enableUDP": true,
    "udpPort": 3478,
}
Key Description
publicIp The public IP address of the server or service.
username The username used for authentication.
password The password used for authentication.
realm The authentication realm, typically representing a domain or service name. value not important but needs to be specified
minPort The minimum port number for dynamic UDP port allocation.
maxPort The maximum port number for dynamic UDP port allocation.
enableTCP Enables TCP protocol for initial communication if set to true.
tcpPort The port number used for initial TCP communication.
enableUDP Enables UDP protocol for initial communication if set to true.
udpPort The port number used for initial UDP communication.

Running

By default running CAXturn.exe is enough as it already searches for a config.json file. a manuel file can be configured via -config

It is recommended to setup a scheduled task to run CAXturn on reboot.

Turn URLs

To use in Portal the URLs need to be specified in the format

turn::
turn::?transport=tcp

Alternatives

The are alternatives to CAXturn. It is possible to use cloud turn hosting providers or tools like coturn.