On server startup the configuration files are loaded as normal. NATS is connected first and if enabled, additional configuration is loaded with a NATS request. This makes it possible to provide additional configuration from other services. NATS configuration is only loaded on startup. So whenever the NATS configuration provider changes the webrtc configuration, it has to trigger a restart of Spreed WebRTC externally.
Chrome 52 started to send rtx support with their SDP which is not supported on Chrome 38 which is the lowest supported version. This change removes rtx from the remote SDP before setting it as remote description when run on Chrome <= 38.
Chrome 52 started to send rtx support with their SDP which is not supported on Chrome 38 which is the lowest supported version. This change removes rtx from the remote SDP before setting it as remote description when run on Chrome <= 38.
For backwards compatibility we return the first in list TURN server directly. This allows clients which do not implement any selection still use TURN and lets the TURN service control which one it should be (first in list is used).
Use this script for TURN testing. Make sure Spreed WebRTC has a TURN server configured which also supports tcp. Make a call and check chrome://webrtc-internals or about:webrtc to see if TURN is actually in use (also make sure that audio and video is coming through in both directions).
https://github.com/strukturag/docker-webrtc-turnserver/issues/5
To provide peer to peer support for users with a firewall, a TURN
service might be required. Not everyone can/wants to setup a self-hosted
TURN server. This change adds support to consume a remote TURN service
which usually requires authentication. Spreed WebRTC received TURN
credentials using this service in regular intervals and provides them to
all Spreed WebRTC sessions.
If the remote TURN service provides multiple zones and a GEO location
endpoint, the web client will also directly connect to that TURN service
GEO endpoint to let the TURN service select preferred zones based on the
clients information.
The advanced settings provide a way to control the TURN service zone
directly and to disable the client side GEO call. By default the
selection is auto if the TURN service provides a GEO endpoint. If no
such endpoint is required, the zone with the highest priority is used by
default (as sent by the TURN credentials service).
Simon Eisenmann
Simon Eisenmann
Leon Klingele
Olivier Paroz
felipe
Simon Eisenmann
Florent BEAUCHAMP