From fd807ff1f6cc11bde34bdd03453ea72e643024c0 Mon Sep 17 00:00:00 2001 From: stratself Date: Sat, 21 Feb 2026 03:07:23 +0000 Subject: [PATCH] docs: specify both inbuilt + external options for livekit TURN in calls page --- docs/calls.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/calls.mdx b/docs/calls.mdx index 681783ca9..1038b9e46 100644 --- a/docs/calls.mdx +++ b/docs/calls.mdx @@ -10,4 +10,4 @@ Both types of calls are supported by different sets of clients, but most clients 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 (foci). LiveKit also uses TURN/STUN to increase reliability, so you might want to configure your TURN server first. [Read the LiveKit guide](./calls/livekit.mdx) +- For MatrixRTC / Element Call to work, you have to set up the LiveKit backend (foci). LiveKit also uses TURN/STUN to increase reliability - you can setup its inbuilt TURN server, or integrate with an existing one. [Read the LiveKit guide](./calls/livekit.mdx)