Skip to content

Commit e102bda

Browse files
jmcrthrsdamencho
authored andcommitted
Advanced configuration should be a header under Install Jitsi Meet instead of Access Control
1 parent f772845 commit e102bda

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/devops-guide/quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@ If you want to limit the ability to start a conference to registered users, foll
202202
The access control for conferences/rooms is managed in the rooms, you can set a password on the webpage of the specific room after creation.
203203
See the User Guide for details: https://jitsi.github.io/handbook/docs/user-guide/user-guide-start-a-jitsi-meeting
204204

205-
#### Advanced configuration
205+
### Advanced configuration
206206

207207
If the installation is on a machine [behind NAT](https://jitsi.github.io/handbook/docs/faq#how-to-tell-if-my-server-instance-is-behind-nat) jitsi-videobridge should configure itself automatically on boot. If three way calls do not work, further configuration of jitsi-videobridge is needed in order for it to be accessible from outside.
208208

0 commit comments

Comments
 (0)