mom040267 4b2be8adae third-party authetorization option is mandatory with oauth 10 years ago
..
basic 702b29bc22 initial code import 11 years ago
loadbalance 702b29bc22 initial code import 11 years ago
longtermsecure 5cd0d33c31 1) working on https; 2) SSLv2 support removed. 10 years ago
longtermsecuredb 4b2be8adae third-party authetorization option is mandatory with oauth 10 years ago
mobile 5cd0d33c31 1) working on https; 2) SSLv2 support removed. 10 years ago
oauth 4b2be8adae third-party authetorization option is mandatory with oauth 10 years ago
restapi 5cd0d33c31 1) working on https; 2) SSLv2 support removed. 10 years ago
selfloadbalance 5cd0d33c31 1) working on https; 2) SSLv2 support removed. 10 years ago
peer.sh 702b29bc22 initial code import 11 years ago
readme.txt 01e2364a7d docs updated 11 years ago
rfc5769.sh 702b29bc22 initial code import 11 years ago

readme.txt

This directory contains various example scripts for the TURN server
functionality illustration.

1) peer.sh starts the "peer" application that serves as a peer for all examples.

2) "basic" directory contains set of scripts which works together to demonstrate
very basic anynymous functionality of the TURN server. The "peer.sh" must be used, too.

3) "longtermsecure" directory contains set of scripts demonstrating the long-term authentication
mechanism (peer.sh to be used, too).

4) "longtermsecuredb" shows how to start TURN server with database. The clients from the
directory "longtermsecure" can be used with the relay scripts in the "longtermsecuredb"
directory. Of course, the database (SQLite, PostgreSQL, MySQL, Redis or MongoDB) must
be set for these scripts to work correctly.

5) "restapi" shows how to use TURN REST API.

6) "shorttermsecure" shows how to use the short-term authentication mechanism. The short term
mechanism is always used with the database.

7) "loadbalance" shows how to use the simple load-balancing mechanism based upon the
ALTERNATE-SERVER functionality.