Skip to content

Commit 993fd04

Browse files
authored
Update jitsi.md
Updated Element Android section
1 parent d0e1d60 commit 993fd04

File tree

1 file changed

+16
-1
lines changed

1 file changed

+16
-1
lines changed

docs/jitsi.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,22 @@ default, and you are using riot-web 1.6 or newer, set the following on your home
5050
}
5151
```
5252

53-
## Mobile app support
53+
## Element Android
54+
55+
Element Android (1.0.5+) supports custom jitsi domain.
56+
57+
1:1 calls, or calls between you and one other person, do not use Jitsi. Instead, those
58+
calls work directly between clients or via TURN servers configured on the respective
59+
homeservers.
60+
61+
For rooms with more than 2 joined members, when creating a jitsi conference via call/video buttons of the toolbar (not via integration manager), Element Android will create a widget using app.element.io [wrapper](https://github.com/vector-im/element-web/blob/develop/docs/jitsi-dev.md) as url.
62+
The domain used is the one specified by the `/.well-known/matrix/client` endpoint, and if not present it uses the fallback defined in `confix.xml` (jitsi.riot.im)
63+
64+
For active jitsi widgets in the room, a native jitsi widget UI is created and points to the instance specified in the `domain` key of the widget content data.
65+
66+
Element android manages allowed native widgets permissions a bit differently than web widgets (as the data shared are different, and never shared with the widget url). For jitsi widgets permissions is asked only once per domain (consent saved in account data).
67+
68+
## Element IOS
5469

5570
Currently the Element mobile apps do not support custom Jitsi servers and will instead
5671
use the default `jitsi.riot.im` server. When users on the mobile apps join the call,

0 commit comments

Comments
 (0)