1
Fork 0

Add sample coturn configuration to README.

This commit is contained in:
Juliusz Chroboczek 2021-01-14 19:37:35 +01:00
parent 6098d4af9d
commit 10ebe0e433
1 changed files with 11 additions and 6 deletions

17
README
View File

@ -54,11 +54,16 @@ In practice, some of your users will be on restrictive networks: many
enterprise networks only allow outgoing TCP to ports 80 and 443; enterprise networks only allow outgoing TCP to ports 80 and 443;
university networks tend to additionally allow outgoing traffic to port university networks tend to additionally allow outgoing traffic to port
1194. For best performance, your TURN server should be located close to 1194. For best performance, your TURN server should be located close to
Galène and close to your users, so you will want to run your own (I use Galène and close to your users, so you will want to run your own. If you
*coturn*, but other implementations of TURN should work too). use *coturn*, your `/etc/turnserver.conf` could look like this:
Your `ice-servers.json` should look like this, where `username` and listening-port=443
`secret` are identical to the ones in your TURN server's configuration: lt-cred-mech
user=galene:secret
realm=galene.example.org
syslog
Your `ice-servers.json` should look like this:
[ [
{ {
@ -71,8 +76,8 @@ Your `ice-servers.json` should look like this, where `username` and
} }
] ]
If you use coturn's `use-auth-secret` option, then your `ice-servers.json` If you prefer to use coturn's `use-auth-secret` option, then your
should look like this: `ice-servers.json` should look like this:
[ [
{ {