You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| API (Calls plugin) | 80,443 | TCP (incoming) | Mattermost clients (web/desktop/mobile) | Mattermost instance (Calls plugin) | To allow for HTTP and WebSocket connectivity from clients to Calls plugin. This API is exposed on the same connection as Mattermost, so there's likely no need to change anything. |
46
-
| RTC (Calls plugin or `rtcd`) | 8443 | UDP (incoming) | Mattermost clients (Web/Desktop/Mobile) | Mattermost instance or `rtcd` service | To allow clients to establish connections that transport calls related media (e.g. audio, video). This should be open on any network component (e.g. NAT, firewalls) in between the instance running the plugin (or `rtcd`) and the clients joining calls so that UDP traffic is correctly routed both ways (from/to clients). |
47
-
| RTC (Calls plugin or `rtcd`) | 8443 | TCP (incoming) | Mattermost clients (Web/Desktop/Mobile) | Mattermost instance or `rtcd` service | To allow clients to establish connections that transport calls related media (e.g. audio, video). This should be open on any network component (e.g. NAT, firewalls) in between the instance running the plugin (or `rtcd`) and the clients joining calls so that TCP traffic is correctly routed both ways (from/to clients). This can be used as a backup channel in case clients are unable to connect using UDP. It requires `rtcd` version >= v0.11 and Calls version >= v0.17. |
48
-
| API (`rtcd`) | 8045 | TCP (incoming) | Mattermost instance(s) (Calls plugin) |`rtcd` service | To allow for HTTP/WebSocket connectivity from Calls plugin to `rtcd` service. Can be expose internally as the service only needs to be reachable by the instance(s) running the Mattermost server. |
49
-
| STUN (Calls plugin or `rtcd`) | 3478 | UDP (outgoing) | Mattermost Instance(s) (Calls plugin) or `rtcd` service | Configured STUN servers | (Optional) To allow for either Calls plugin or `rtcd` service to discover their instance public IP. Only needed if configuring STUN/TURN servers. This requirement does not apply when manually setting an IP or hostname through the [ICE Host Override](https://docs.mattermost.com/configure/plugins-configuration-settings.html#ice-host-override) config option. |
<td>To allow for HTTP and WebSocket connectivity from clients to Calls plugin. This API is exposed on the same connection as Mattermost, so there's likely no need to change anything.</td>
86
+
</tr>
87
+
<tr>
88
+
<td>RTC (Calls plugin or <code>rtcd</code>)</td>
89
+
<td>8443</td>
90
+
<td>UDP (incoming)</td>
91
+
<td>Mattermost clients (Web/Desktop/Mobile)</td>
92
+
<td>Mattermost instance or <code>rtcd</code> service</td>
93
+
<td>To allow clients to establish connections that transport calls related media (e.g. audio, video). This should be open on any network component (e.g. NAT, firewalls) in between the instance running the plugin (or <code>rtcd</code>) and the clients joining calls so that UDP traffic is correctly routed both ways (from/to clients).</td>
94
+
</tr>
95
+
<tr>
96
+
<td>RTC (Calls plugin or <code>rtcd</code>)</td>
97
+
<td>8443</td>
98
+
<td>TCP (incoming)</td>
99
+
<td>Mattermost clients (Web/Desktop/Mobile)</td>
100
+
<td>Mattermost instance or <code>rtcd</code> service</td>
101
+
<td>To allow clients to establish connections that transport calls related media (e.g. audio, video). This should be open on any network component (e.g. NAT, firewalls) in between the instance running the plugin (or <code>rtcd</code>) and the clients joining calls so that TCP traffic is correctly routed both ways (from/to clients). This can be used as a backup channel in case clients are unable to connect using UDP. It requires <code>rtcd</code> version >= v0.11 and Calls version >= v0.17.</td>
102
+
</tr>
103
+
<tr>
104
+
<td>API (<code>rtcd</code>)</td>
105
+
<td>8045</td>
106
+
<td>TCP (incoming)</td>
107
+
<td>Mattermost instance(s) (Calls plugin)</td>
108
+
<td><code>rtcd</code> service</td>
109
+
<td>To allow for HTTP/WebSocket connectivity from Calls plugin to <code>rtcd</code> service. Can be expose internally as the service only needs to be reachable by the instance(s) running the Mattermost server.</td>
110
+
</tr>
111
+
<tr>
112
+
<td>STUN (Calls plugin or <code>rtcd</code>)</td>
113
+
<td>3478</td>
114
+
<td>UDP (outgoing)</td>
115
+
<td>Mattermost Instance(s) (Calls plugin) or <code>rtcd</code> service</td>
116
+
<td>Configured STUN servers</td>
117
+
<td>(Optional) To allow for either Calls plugin or <code>rtcd</code> service to discover their instance public IP. Only needed if configuring STUN/TURN servers. This requirement does not apply when manually setting an IP or hostname through the <ahref="https://docs.mattermost.com/configure/plugins-configuration-settings.html#ice-host-override">ICE Host Override</a> config option.</td>
118
+
</tr>
119
+
</tbody>
120
+
</table>
50
121
51
122
#### Air-gapped deployments
52
123
@@ -136,31 +207,212 @@ Here are the results from internally conducted performance and ceiling tests on
136
207
137
208
#### Results
138
209
139
-
```{tip}
140
-
Scroll horizontally to see additional columns in the table below.
- The tests focused on a single, vertically scaled RTCD instance to understand the processing limits within a single node. Scaling the RTCD service horizontally should be sufficient to support a higher number of calls.
0 commit comments