Ubuntu
rfc5766-turn-server package

rfc5766-turn-server 2.6.5.2-1 source package in Ubuntu

Changelog

rfc5766-turn-server (2.6.5.2-1) unstable; urgency=low


  * Redis memory leak fixed.

 -- Oleg Moskalenko <email address hidden>  Tue, 08 Oct 2013 22:56:59 -0700

Upload details

Uploaded by:
Debian VoIP Team
Uploaded to:
Sid
Original maintainer:
Debian VoIP Team
Architectures:
any
Section:
misc
Urgency:
Low Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
rfc5766-turn-server_2.6.5.2-1.dsc 2.2 KiB 4f72f76b0b75036724cfb99f4932e175150a37649dda8c2f0b61fc2e7286a52d
rfc5766-turn-server_2.6.5.2.orig.tar.gz 225.2 KiB ea8cc850d52384c43092d6813c6a9006e725fef6ba9db3550864b00866bdcd87
rfc5766-turn-server_2.6.5.2-1.debian.tar.gz 8.3 KiB 0246a6479691c7574932a99ab8ece53e25884b4fa8e67f8dd3d292eead879296

Available diffs

No changes file available.

Binary packages built by this source

rfc5766-turn-server: TURN and STUN server for VoIP

 STUN (Session Traversal Utilities for NAT) and TURN (Traversal Using Relays
 around NAT) are protocols that can be used to provide NAT traversal for VoIP
 and WebRTC. This package provides a VoIP media traffic NAT traversal server
 and gateway.
 .
 Supported RFCs:
 TURN specs:
  * RFC 5766 - base TURN specs;
  * RFC 6062 - TCP relaying TURN extension;
  * RFC 6156 - IPv6 extension for TURN;
  * DTLS support as client protocol
    http://tools.ietf.org/html/draft-petithuguenin-tram-turn-dtls-00;
  * Mobile ICE (MICE) support
    http://datatracker.ietf.org/doc/draft-wing-mmusic-ice-mobility.
 .
 STUN specs:
  * RFC 3489 - obsolete "classic" STUN specs;
  * RFC 5389 - base "new" STUN specs;
  * RFC 5769 - test vectors for STUN protocol testing;
  * RFC 5780 - NAT behavior discovery support.
 .
 The implementation fully supports UDP, TCP, TLS, and DTLS as protocols between
 the TURN client and the TURN server. Both UDP and TCP relaying are supported.
 .
 Flat files, MySQL, PostgreSQL, or Redis are all supported for the user
 repository (if authentication is required).
 Both short-term and long-term credentials mechanisms are supported.
 For WebRTC applications, the TURN server REST API for time-limited
 secret-based authentication is implemented.
 .
 Load balancing can be implemented either by DNS round-robin mechanism, or with
 the external networking tools, or by
 the built-in ALTERNATE-SERVER mechanism.
 .
 The implementation is intended to be simple to install and configure.
 The project focuses on performance, scalability, and simplicity.
 The aim is to provide an enterprise-grade TURN solution.