Project

General

Profile

WebRTC Conference » History » Version 14

Dan Pascu, 07/07/2017 02:39 PM

1 3 Adrian Georgescu
h1. SylkServer WebRTC Managed Conference
2 2 Adrian Georgescu
3 4 Adrian Georgescu
4 2 Adrian Georgescu
h2. Design
5
6 12 Dan Pascu
Two types of conferences are being supported: ad-hoc conferences and moderated conferences.
7
8
h3. Ad-hoc conferences
9
10
An ad-hoc conference is a conference where all participants have the same status and no one is controlling what other are participants are doing. The participants are rendered in a matrix or up to 3x3 depending of how many participants are in the room. The layout switches automatically for everybody as participants join or leave.
11
12
The conference room has a fixed total bitrate configured by the server, that can be specified per room or globally with the max_bitrate setting in webrtcgateway.ini (see below). This bitrate is shared by all participants in the room, meaning that the more participants are in the room, the less bitrate each participant will use for the video stream they send, keeping the total room usage constant to the value configured by max_bitrate. The bitrate adjustment per participant is done automatically by sylkserver as participants join or leave the room, by diving the available bitrate among the number of participants. The end result of this is that each participant will send a fraction of max_bitrate (which is determined by the number of participants in the room) and will always receive a total combined of max_bitrate from all the participants in the room, no matter how many participants are in the room. The formula to compute the bitrate per participant is shown below:
13
14
<pre>
15
participant_send_bitrate = max_bitrate / max(number_of_participants - 1, 1)
16
</pre>
17
18
Using this formula we can make sure that each participant always receives max_bitrate traffic in incoming video streams, independent of the number of participants. The traffic send/received by each party can be expressed like (considering N to be the number of participants and N>1):
19
20
<pre>
21
participant_sent_traffic     = max_bitrate / (N - 1)
22
participant_received_traffic = max_bitrate
23
24
sylkserver_sent_traffic     = max_bitrate * N            (participant_received_traffic * N)
25
sylkserver_received_traffic = max_bitrate * N / (N - 1)  (participant_sent_traffic     * N)
26
</pre>
27
28 14 Dan Pascu
h3. Moderated conferences
29
30
A moderated conference is a conference where a moderator can decide the flow of the conference. The moderator is the first participant to join the conference. The moderator has the ability to see a list with all the participants, can select 1 or 2 of them to be the active speakers and also has the ability to mute other participants (audio and/or video). The moderator can also change the active speakers at any time.
31 12 Dan Pascu
32 2 Adrian Georgescu
h2. Features
33
34 11 Adrian Georgescu
h3. Ad-hoc conference
35 1 Adrian Georgescu
36 11 Adrian Georgescu
All participants are rendered in a matrix where each participants has the same size. The conference room has a fixed total bandwidth set by the server, which is divided between the participants, which means the more participants are in the room, the less bandwidth each participant will use keeping the bandwidth usage per conference room constant.
37
38
h3. Managed conference
39
40
The first participants becomes the manager. He can add/remove mute participants and also decide which one is the active speaker(s).
41 7 Adrian Georgescu
42 2 Adrian Georgescu
h2. Configuration
43
44 10 Dan Pascu
Sylkserver allows the maximum bitrate and video codec to be configured, globally or per room with the following settings in webrtcgateway.ini file:
45
46
<pre>
47
; Maximum video bitrate allowed per sender in a room in bits/s. This value is
48
; applied to any room that doesn't define its own. The value is any integer
49
; number between 64000 and 4194304. Default value is 2016000 (~2Mb/s).
50
; max_bitrate = 2016000
51
52
; The video codec to be used by all participants in a room. This value is
53
; applied to any room that doesn't define its own.
54
; Possible values are: h264, vp8 and vp9. Default is vp9.
55
; video_codec = vp9
56
</pre>
57
58
59 1 Adrian Georgescu
h2. Client support
60
61
h2. Measurements
62
63 10 Dan Pascu
This measurement was done on a Macbook Pro 15" with a 2.3GHz Intel Core I7 CPU, while having 7 participants in the room with each using 336Kb/s. The measurement shows the CPU usage in Firefox with the aforementioned conditions, for the specified video codecs and resolutions which are used by all participants:
64 1 Adrian Georgescu
65 10 Dan Pascu
<pre>
66
 * H264/VGA - 150% CPU
67
 * H264/HD  - 250% CPU
68
 * VP9/VGA  - 220% CPU
69
 * VP9/HD   - 350% CPU
70
</pre>
71 6 Adrian Georgescu
72
73
h2. Remaining tasks
74
75
 * sylkserver: control interface for moderator
76 1 Adrian Georgescu
 * janus: patch to request full frames when a paused video is resumed