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
{{ message }}
This repository was archived by the owner on Oct 23, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: doc/servermd/Server.md
+1-43Lines changed: 1 addition & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,48 +123,6 @@ Before installing the OWT server, make sure your login account has sys-admin pri
123
123
124
124
If you run OWT server on CentOS, configure the system firewall well to make sure all ports required by OWT server components are open.
125
125
126
-
In order for the OWT server to deliver the best performance on video conferencing, the following system configuration is recommended:
127
-
128
-
1. Add or update the following lines in /etc/security/limits.conf, in order to set the maximum numbers of open files, running processes and maximum stack size to a large enough number:
129
-
130
-
* hard nproc unlimited
131
-
* soft nproc unlimited
132
-
* hard nofile 163840
133
-
* soft nofile 163840
134
-
* hard stack 8192
135
-
* soft stack 8192
136
-
137
-
If you only want to target these settings to specific user or group rather than all with "*", please follow the configuration rules of the /etc/security/limits.conf file.
138
-
139
-
2. Make sure pam_limits.so appears in /etc/pam.d/login as following:
140
-
141
-
session required pam_limits.so
142
-
143
-
So that the updated limits.conf takes effect after your next login.
144
-
145
-
3. If you run OWT server on CentOS, add or update the following two lines in /etc/security/limits.d/xx-nproc.conf as well:
146
-
147
-
* soft nproc unlimited
148
-
* hard nproc unlimited
149
-
* hard nofile 163840
150
-
* soft nofile 163840
151
-
152
-
4. Add or update the following lines in /etc/sysctl.conf:
153
-
154
-
fs.file-max=200000
155
-
net.core.rmem_max=16777216
156
-
net.core.wmem_max=16777216
157
-
net.core.rmem_default=16777216
158
-
net.core.wmem_default=16777216
159
-
net.ipv4.udp_mem=4096 87380 16777216
160
-
net.ipv4.tcp_rmem=4096 87380 16777216
161
-
net.ipv4.tcp_wmem=4096 65536 16777216
162
-
net.ipv4.tcp_mem=8388608 8388608 16777216
163
-
164
-
5. Now run command /sbin/sysctl -p to activate the new configuration, or just restart your OWT server machine.
165
-
166
-
6. You can run command "ulimit -a" to make sure the new setting in limits.conf is correct as you set.
167
-
168
126
### 2.3.3 Install the OWT server package {#Conferencesection2_3_3}
169
127
170
128
On the server machine, directly unarchive the package file.
@@ -345,7 +303,7 @@ Follow the steps below to set up a OWT server cluster:
345
303
346
304
13. Choose a worker machine to run conference-agent and/or webrtc-agent and/or streaming-agent and/or recording-agent and/or audio-agent and/or video-agent and/or sip-agent. This machine must be visible to other agent machines. If webrtc-agent or sip-agent is running on it, it must be visible to clients.
347
305
348
-
- If you want to use Intel<sup>®</sup> Visual Compute Accelerator (VCA) to run video agents, please follow section [Configure VCA nodes](#Conferencesection2_3_10) to enable nodes of Intel VCA as a visible separated machine.
306
+
- If you want to use Intel<sup>®</sup> Visual Compute Accelerator (VCA) to run video agents, please follow section [Configure VCA nodes](#Conferencesection2_3_11) to enable nodes of Intel VCA as a visible separated machine.
349
307
350
308
14. Edit the configuration items in Release-<Version>/{audio, video, conference, webrtc, streaming, recording, sip}_agent/agent.toml.
351
309
- Make sure the [rabbit.port] and [rabbit.host] point to the RabbitMQ server.
0 commit comments