coturn TURN server project
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
coturn/debian
Mészáros Mihály 6fa2d712d1 Update changelog for 4.5.1.3-1 release 6 years ago
..
etc/ufw/applications.d sync to 4.2.3.1 11 years ago
patches Remove patch for CVE 2020 6061+6062 6 years ago
source updated debian package 7 years ago
tests move examples to doc 7 years ago
upstream Update metadata 6 years ago
README.Debian Add info about systemd to README 7 years ago
changelog Update changelog for 4.5.1.3-1 release 6 years ago
control Change Debian VoIP Team mailinglist 6 years ago
copyright updated debian package 7 years ago
coturn.default Initial Debian packaging 12 years ago
coturn.doc-base new scripts and license added 12 years ago
coturn.docs move examples to doc 7 years ago
coturn.examples updated debian package 7 years ago
coturn.init Initial Debian packaging 12 years ago
coturn.install Import Debian changes 4.5.1.1-1.1 6 years ago
coturn.links migrate bin from turnserver to coturn, symlink 6 years ago
coturn.lintian-overrides Initial Debian packaging 12 years ago
coturn.manpages wrap-and-sort -an 7 years ago
coturn.postinst Import Debian changes 4.5.1.1-1.1 6 years ago
coturn.postrm Import Debian changes 4.5.1.1-1.1 6 years ago
coturn.service Add full path to sleep (for backward compatibility). 7 years ago
gbp.conf Adopt DEP-14 repo structure 7 years ago
rules exclude CA from examples and docs 6 years ago
watch updated debian package 7 years ago

README.Debian

Coturn TURN Server for Debian
------------------------------

1) The turnserver has reasonable default option values and can work in many
simple environments without extra configuration. But more complex meaningful
usage requires setting options specific to your particular environment.
For example, WebRTC requires long-term credentials and some extra stuff.
To set the turnserver parameters:

a) Edit /etc/turnserver.conf file.

b) For user accounts settings, the default SQLite TURN database location
is /var/db/turndb. If you do not set any database and if you do not set
any TURN server database options, then the TURN server
will try to create an empty SQLite database in that default location.
Or you can set up PostgreSQL or MySQL or Redis database for
user accounts. Use /usr/share/coturn/schema.sql as SQL database schema,
or use /usr/share/coturn/schema.userdb.redis as Redis
database schema explanation for the user authentication data, and
(optionally) use /usr/share/coturn/schema.stats.redis as
Redis database schema explanation for status and statistics data.

2) You can start/stop the turnserver "manually", using the "/usr/bin/turnserver"
executable with appropriate options (see the documentation).
If you want the turnserver to be an automatically started system service,
then you have to un-comment the line "TURNSERVER_ENABLED=1" in
the /etc/default/coturn file.

3) If you are using UFW, then run the command after the installation:

$ ufw add turnserver

You can inspect and adjust the UFW turnserver settings in the file
/etc/ufw/applications.d/turnserver.

4) For additional information, run:

$ man turnserver
$ man turnadmin
$ man turnutils

5) During installation, no TURN user accounts are created.
Coturn does not recognize UNIX accounts and requires accounts
to be defined in it's own config file. By default, the TURN server
uses anonymous access.

6) Systemd:
In some configurations you may need to add the

After=network-online.target

line to the/etc/systemd/system/coturn.service.d/network.conf or
simillar systemd config file.


Traditional STUN doesn't require an account. For TURN relay
purposes, several accounting options are possible:
- anonymous access (the default option);
- traditional long-term credentials mechanism (see RFC5766);
- TURN REST API shared-secret-based long-term credentials mechanism
(see TURN REST API docs);
- Third-party authorization extension for the
long-term credentials mechanism;

If you are installing the TURN server for WebRTC usage, then you must set
the long term credentials mechanism option and add user accounts -
either with the default SQLite database, or with PostgreSQL
database, or with MySQL database, or with Redis database. Optionally,
you can add TURN REST API on top of long-term credentials mechanism.

Please see the README.* files for details.

-- Mészáros Mihály <misi@majd.eu> Tue, 27 Nov 2018 12:32:02 +0000
-- Oleg Moskalenko <mom040267@gmail.com> Wed, 29 Oct 2014 11:47:00 -0700