Since FF 49, the call to gUM only succeeds if both audio and video constraints
can be satisfied, i.e. without a webcam the request fails. This is now handled
gracefully, the available devices enumerated and the gUM request is retried
with updated constraints (fixes#394).
Nothing _really_ serious though, as the message was still auto-
filtered by Angular. This would not allow to load remote scripts.
As we still need to show some un-sanitized messages, we can't fix
this in alertify.js directly to force-sanitize all texts.
This avoids having to update the `uicontroller.js` manually each time the
sprite changes. The JSON file is automatically copied by the `_encode.sh`
script.
Any adjustments are done during building, so we can keep the source files
unmodified. With that, updated the build script to sort the list of sounds
in the sprite by name so further changes are consistent.
This fixes#377 where no ringing sound was played back because the call
was not seen as "outgoing" (and also fixes the missing timeout if the
called peer does not pick up).
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.
Joachim Bauch
Joachim Bauch
mrktt
Leon Klingele
Simon Eisenmann
Simon Eisenmann
Olivier Paroz