EN
Español
English
Português
    Configuring the STUN/TURN WebRTC Server

    ↩ External TURN Server

    After you install the service Aranda Turn Stun WebRTC Server, the configuration is necessary for it to work properly.

    1. File Validation turn-server.toml

    Before making changes, verify that the turn-server.toml is located in the service installation path (by default: C:\Program Files (x86)\Aranda\Aranda Remote Control\Stun Server).



    To configure the STUN/TURN WebRTC service, use the turn-server.toml:

    • Section [turn]: Specifies the domain where the server is located.
    • Section [[turn.interfaces]]: Indicates the listening interfaces. Describes the interface to which the STUN/TURN server is linked. Various interfaces can be indicated.
    • Section [turn.interfaces.transport]: Defines the type of transport of the interface, which can be udp or tcp.
    • Section [turn.interfaces.bind]: IP address and binding port of the internal socket.
    • Section [turn.interfaces.external]: It is used to link to the address of your local NIC. For example, if you have two NICs, A and B, on your server, and the IP address of NIC A is 192.168.1.2 and that of NIC B is 192.168.1.3, if bound to IAS A, you must bind to the address 192.168.1.2. Link to 0.0.0.0 It means that you listen to all interfaces at the same time. The word external means that your network card for the customer can “see” the IP address. Continuing with the previous example, if your network card A communicates with the outside, the other clients will see your LAN address (i.e., 192.168.1.2). However, in reality, the network topology where the server is deployed might have another public IP, such as 1.1.1.1, which is the IP address seen by other clients. The reason why they are needed bind and external is that, for the STUN protocol, the server needs to report its own external IP address, thus allowing the STUN client to connect to the specified address using the IP reported by the server.
    • Section [api.bind]: Listening to the API for queries, for example: http://127.0.0.1:3000/info.
    • Section [log.level]: Log level. Valid values: error, warn, info, debug, trace.
    • Section [auth]: Username and password to access the server.

    2. Start of Service

    Start the STUN Server service (Aranda Turn Stun WebRTC Server) for the configuration changes to take effect.

    3. Firewall Settings

    Open the port or ports configured in step 1 in the local firewall inbound rules and in the network controllers present in the client infrastructure, for the protocols TCP and UDP. This step is essential to allow traffic through the new port and ensure that the STUN server can receive incoming connections on the configured port.

    On workstations (AVS Agent) and on specialist computers (Specialist Agent), they must allow egress through the ports that are configured.

    Additionally, if you require it to operate as TURN WebRTC, you must open the port range 49152-65535 for the protocol UDP.

    STUN/TURN Service Configuration Example and Scenarios

    ↩ External TURN Server