docs(calls): Small fixup of wordings

* Use indirect links and fix them
* Make Livekit's TURN configuration optional
This commit is contained in:
stratself authored and Ellis Git committed 2026-11-10 23:00:08 +00:00
1 parent dd11fc5a25
commit bbf3bd1294
1 file changed
+6 -3
+6 -3
View File
@@ -2,12 +2,15 @@
Matrix supports two types of calls:
- Element Call powered by [MatrixRTC](https://half-shot.github.io/msc-crafter/#msc/4143) and [LiveKit](https://github.com/livekit/livekit)
- Element Call powered by [MatrixRTC][MSC4143] and [LiveKit][livekit-server-github]
- Legacy calls, supported by a STUN/TURN server.
[MSC4143]: https://github.com/matrix-org/matrix-spec-proposals/pull/4143
[livekit-server-github]: https://github.com/livekit/livekit
Both types of calls are supported by different sets of clients, but most clients are moving towards MatrixRTC / Element Call.
For either one to work correctly, you have to do some additional setup:
- For legacy calls to work, you need to set up a TURN/STUN server. [Read the TURN guide for tips on how to set up coturn](./calls/turn.mdx)
- For MatrixRTC / Element Call to work, you have to set up the LiveKit backend. LiveKit also uses TURN/STUN to increase reliability - you can set up its built-in TURN server, or integrate with an existing one. [Read the LiveKit guide](./calls/livekit.mdx)
- For legacy calls to work, you need to set up a TURN/STUN server. [Read the TURN guide for instructions on how to set up coturn](./calls/turn.mdx)
- For MatrixRTC / Element Call to work, you have to set up the LiveKit backend, and optionally configure a TURN server for increased reliability. [Read the LiveKit guide](./calls/livekit.mdx)