@@ -55,17 +55,17 @@ This allows a distinct set of rooms to be provided with phone dial-in.
55
55
56
56
Here's the setup:
57
57
58
- | Room Name | Dialin Suffix |
59
- | --------------- | ------------- |
60
- | SCS-Tech | 611 |
61
- | SCS-Governance | 612 |
62
- | Open-Operations | 613 |
63
- | SCS-OSISM | 614 |
64
- | SCS-Project | 615 |
65
- | SCS-Forum | 616 |
66
- | SCS-Kurt | 617 |
67
- | SCS-Taskforce | 618 |
68
- | SCS-ProjectTeam | 619 |
58
+ | Room Name | Dial-in Suffix |
59
+ | --------------- | -------------- |
60
+ | SCS-Tech | 611 |
61
+ | SCS-Governance | 612 |
62
+ | Open-Operations | 613 |
63
+ | SCS-OSISM | 614 |
64
+ | SCS-Project | 615 |
65
+ | SCS-Forum | 616 |
66
+ | SCS-Kurt | 617 |
67
+ | SCS-Taskforce | 618 |
68
+ | SCS-ProjectTeam | 619 |
69
69
70
70
Dial +49-221-292772-Suffix to connect.
71
71
@@ -94,7 +94,7 @@ By enabling experimental `media.webrtc.codec.video.av1.experimental_preferred` y
94
94
or AV1 encoding support and on whether that is exposed by your graphics driver stack, this may or may
95
95
not create high CPU usage which you may not consider welcome as mobile user.
96
96
97
- ## Limitations
97
+ ## Limitations and issues
98
98
99
99
### Firewalls blocking UDP traffic
100
100
@@ -103,18 +103,7 @@ video is transmitted via UDP (port 10000+). Some corporate and many public secto
103
103
that outgoing(!) UDP traffic is dangerous and needs to be intercepted. This means that our Jitsi
104
104
setup will not work for participants behind such firewalls.
105
105
(We do not currently have a [ COTURN] ( https://github.com/coturn/coturn ) server to work around this;
106
- instead we use other VC tools such as BB or OpenTalk or the tool of the partner.))
107
-
108
- ### Large conferences
109
-
110
- For large conferences, it is recommended that participants stay muted and raise their hand
111
- in order to talk, so a moderator can ensure a somewhat structured discussion. While Jitsi can route
112
- a few dozens of video streams without trouble, the combines bandwidth may become a challenge for
113
- some of the participants and it is recommended to only switch on videos for the active participants.
114
- We have not tested much above 50 participants in the SCS community, so we don't know the precise limits
115
- of the server connection or capacity we use.
116
-
117
- ## Known Issues
106
+ instead we use other VC tools such as BB or OpenTalk or the tool of the partner.)
118
107
119
108
### Local audio
120
109
@@ -123,15 +112,24 @@ On Linux systems, the `pavucontrol` mixer may be the best starting point to reso
123
112
124
113
### Selective Stream forwarding failure
125
114
126
- Jitsi receives one or several audio and video streams from every participiant and selectively
115
+ Jitsi receives one or several audio and video streams from every participant and selectively
127
116
forwards those to all recipients that have subscribed to these streams. (Typically, a low-res video
128
117
stream is sent in addition to a medium-res and a high-res one — if any high-res subscribers exist).
129
118
This approach to video-conferencing is called
130
119
[ selective forwarding unit (SFU)] ( https://bloggeek.me/webrtcglossary/sfu/ ) .
131
120
Occasionally, one of the participants can not hear one other (out of many) participants but everyone
132
- else can hear echa other - a subscription to an audio (or video) stream may have gotten lost.
121
+ else can hear each other - a subscription to an audio (or video) stream may have gotten lost.
133
122
In this case, a reconnect by the one not hearing is the best remedy.
134
123
124
+ ### Large conferences
125
+
126
+ For large conferences, it is recommended that participants stay muted and raise their hand
127
+ in order to talk, so a moderator can ensure a somewhat structured discussion. While Jitsi can route
128
+ a few dozens of video streams without trouble, the combined bandwidth may become a challenge for
129
+ some of the participants and it is recommended to only switch on videos for the active participants.
130
+ We have not tested much above 50 participants in the SCS community, so we don't know the precise limits
131
+ of the server connection or capacity we use.
132
+
135
133
### Screen sharing frame rate
136
134
137
135
Some browsers seem to ignore the FPS setting and try to transmit a shared window (or a shared
0 commit comments