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).
This also refactors the channelling API for better clarity
as well as introducing the following functional changes:
* All Hello requests will now receive a Welcome or Error return.
* The message sent in response to a successful authentication
request now uses the Iid provided with the originating request.
* Responses to requests for the Self document now use the Iid
provided with the originating request.
* Failed authentication requests now receive an error return.
* Malformed requests for the Hello, Authentication, Sessions,
and Rooms documents will now receive an error return.
* Requests for the Sessions document which cannot be processed
now receive an error return.
* Requests for the Users document will receive an error return
if the requesting session has not joined a room.
Simon Eisenmann
Joachim Bauch
Simon Eisenmann
Lance Cooper
Yuriy Shevchuk