mad-star-studio/element-web
2
0
Fork 0
Code Pull requests Activity

Update jitsi doc to specify minimum version (#20737)

Browse source 
and also rephrase a bit I was failing to understand
This commit is contained in:
David Baker 2022-01-25 14:42:02 +00:00 • committed by GitHub
parent 397e2b53d1
commit 433542010b
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/jitsi.md
View file

@ -16,6 +16,10 @@ provide their own approaches for adding Jitsi widgets.
## Configuring Element to use your self-hosted Jitsi server ## Configuring Element to use your self-hosted Jitsi server
You can host your own Jitsi server to use with Element. It's usually advisable to use a recent
version of Jitsi. In particular, versions older than around 6826 will cause problems with
Element 1.9.10 or newer.
Element will use the Jitsi server that is embedded in the widget, even if it is not the Element will use the Jitsi server that is embedded in the widget, even if it is not the
one you configured. This is because conference calls must be held on a single Jitsi one you configured. This is because conference calls must be held on a single Jitsi
server and cannot be split over multiple servers. server and cannot be split over multiple servers.
@ -30,8 +34,8 @@ to your [config](./config.md) the following:
} }
``` ```
The default is `meet.element.io` (a free service offered by Element), and the demo site for Element's default is `meet.element.io` (a free service offered by Element). `meet.jit.si`
Jitsi uses `meet.jit.si` (also free). is an instance hosted by Jitsi themselves and is also free to use.
Once you've applied the config change, refresh Element and press the call button. This Once you've applied the config change, refresh Element and press the call button. This
should start a new conference on your Jitsi server. should start a new conference on your Jitsi server.