![]() We do not recommend running a TURN server behind NAT, and are not aware of Traffic (remember to allow both TCP and UDP traffic), and ports 49152-65535 You've configured it to listen on (By default: 34 for TURN We recommend that you only try to set up TLS/DTLS once you have set up aĮnsure your firewall allows traffic into the TURN server on the ports In this case, replace the turn: schemes in the turn_uri settings below # For Let's Encrypt certificates, use `fullchain.pem` here. To nf: # TLS certificates, including intermediate certs. User-quota=12 # 4 streams per video call, so 12 streams = 3 simultaneous relayed calls per user.Īlso consider supporting TLS/DTLS. # consider whether you want to limit the quota of relayed streams per user (or total) to avoid risk of DoS. # special case the turn server itself so that client->TURN->TURN->client flows work # given the turn server is likely behind your firewall, remember to include any privileged public IPs too.ĭenied-peer-ip=192.168.0.0-192.168.255.255 # don't let the relay ever try to connect to private IP address ranges within your network (if any) There is no reason to let users connect to arbitrary TCP endpoints via the relay. Suggested as a minimum starting point: # VoIP traffic is all UDP. TURN lets users request a relay which willĬonnect to arbitrary IP addresses and ports. Logfile - check the example config file supplied with coturn.Ĭonsider your security settings. Alternatively, coturn can be configured to write to a (in which case, the logs will be available via journalctl -u coturn on a TheĮasiest way is normally to send them to the syslog: syslog You will most likely want to configure coturn to write logs somewhere. Sent to clients as part of the authentication flow.) It is conventional to The static-auth-secret is with pwgen: pwgen -s 64 1Ī realm must be specified, but its value is somewhat arbitrary. Lines, with example values, are: use-auth-secret Warnings about lack of database support: a database is unnecessaryĬreate or edit the config file in /etc/nf. The way recommended by your operating system. You may need to install libevent2: if so, you should do so in Source installationĭownload the latest release from github. This will install and start a systemd service called coturn. ![]() Just install the debian package: apt install coturn The TURN daemon coturn is available from a variety of sources such as native package managers, or installation from source. Hosting TURN behind a NAT (even with appropriate port forwarding) is known to cause issuesĪnd to often not work. Requirementsįor TURN relaying with coturn to work, it must be hosted on a server/endpoint with a public IP. The following sections describe how to install coturn (which implements the TURN REST API) and integrate it with synapse. TURN server through the use of a secret shared between the Home Server and the The synapse Matrix Home Server supports integration with TURN server via theĪllows the Home Server to generate credentials that are valid for use on the This document explains how to enable VoIP relaying on your Home Server with
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |