| Name : turnserver
| |
| Version : 4.5.1.0
| Vendor : Firewall-Services < http://www_firewall-services_com>
|
| Release : 0.beta2.git.2.1fd8c02.el7.fws
| Date : 2019-02-22 11:21:55
|
| Group : System Environment/Libraries
| Source RPM : turnserver-4.5.1.0-0.beta2.git.2.1fd8c02.el7.fws.src.rpm
|
| Size : 1.38 MB
| |
| Packager : Firewall-Services < http://www_firewall-services_com>
| |
| Summary : Coturn TURN Server
|
Description :
The TURN Server is a VoIP media traffic NAT traversal server and gateway. It
can be used as a general-purpose network traffic TURN server/gateway, too.
This implementation also includes some extra features. Supported RFCs:
TURN specs:
- RFC 5766 - base TURN specs
- RFC 6062 - TCP relaying TURN extension
- RFC 6156 - IPv6 extension for TURN
- Experimental DTLS support as client protocol.
STUN specs:
- RFC 3489 - \"classic\" STUN
- RFC 5389 - base \"new\" STUN specs
- RFC 5769 - test vectors for STUN protocol testing
- RFC 5780 - NAT behavior discovery support
The implementation fully supports the following client-to-TURN-server protocols:
- UDP (per RFC 5766)
- TCP (per RFC 5766 and RFC 6062)
- TLS (per RFC 5766 and RFC 6062); SSL3/TLS1.0/TLS1.1/TLS1.2
- DTLS (experimental non-standard feature)
Supported relay protocols:
- UDP (per RFC 5766)
- TCP (per RFC 6062)
Supported user databases (for user repository, with passwords or keys, if
authentication is required):
- SQLite
- MySQL
- PostgreSQL
- Redis
Redis can also be used for status and statistics storage and notification.
Supported TURN authentication mechanisms:
- long-term
- TURN REST API (a modification of the long-term mechanism, for time-limited
secret-based authentication, for WebRTC applications)
The load balancing can be implemented with the following tools (either one or a
combination of them):
- network load-balancer server
- DNS-based load balancing
- built-in ALTERNATE-SERVER mechanism.
|
RPM found in directory: /vol/rzm5/linux-smeserver/contribs/fws/repo.firewall-services.com/centos-testing/7/x86_64 |
