Package: rfc5766-turn-server
Version: 3.2.3.1-1
Architecture: amd64
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian VoIP Team <pkg-voip-maintainers@lists.alioth.debian.org>
Installed-Size: 943
Depends: libc6 (>= 2.14), libevent-core-2.0-5 (>= 2.0.10-stable), libevent-openssl-2.0-5 (>= 2.0.10-stable), libevent-pthreads-2.0-5 (>= 2.0.10-stable), libhiredis0.10 (>= 0.10.1), libmysqlclient18 (>= 5.5.24+dfsg-1), libpq5 (>= 8.4~), libssl1.0.0 (>= 1.0.1), adduser, telnet
Suggests: sip-router, xmpp-server
Conflicts: turnserver
Provides: stun-server, turn-server
Section: net
Priority: extra
Homepage: http://code.google.com/p/rfc5766-turn-server/
Description: 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.
