A pure rust-implemented turn server, different from coturn, provides a more flexible external control API and provides the same performance and memory footprint, this project is most compatible with the scenario of using stun/turn server in webrtc.

Who uses it?

• Psyai
• Faszialespecialist

Table of contents

• features
• crates
• usage
  • docker
  • linux service
• building
• benchmark

Features

• external controller api. ^(http)
• webhooks api. ^(http)
• only long-term authentication is supported.
• static identity in configuration file.
• only use udp protocol.
• virtual port support. ^{(allocate request does not allocate real udp ports)}

Crates

• stun, fast and zero-cost stun message decoder and encoder. ^(crate).
• turn, a library for handling turn sessions. ^(crate).
• turn-server, implementation of turn server based on turn library. ^(api)

Usage

cargo install turn-server

Start with configuration file:

turn-server --config=/etc/turn_server/config.toml

Please check the example configuration file for details: turn_server.toml

Docker

docker pull quasipaa/turn-server

The custom configuration file overrides the /etc/turn-server/config.toml path inside the image through -v.

Linux service

./install-service.sh

This will compile the project and install and start the service.

Building

Prerequisites

You need to install the Rust toolchain, if you have already installed it, you can skip it, Install Rust, then get the source code:

git clone https://github.com/mycrl/turn-rs

Build workspace

Compile the entire workspace in release mode:

cd turn-rs
cargo build --release

After the compilation is complete, you can find the binary file in the "target/release" directory.

Benchmark

stun_decoder/channel_bind ...[time: 20.606 ns] ...[thrpt: 4.8812 GiB/s]
stun_decoder/binding_request ...[time: 20.862 ns] ...[thrpt: 4.2856 GiB/s]

License

GPL Copyright (c) 2022 Mr.Panda.