@@ -0,0 +52,4 @@
+#      - "50100-50200:50100-50200/udp"
+```
+
+Next, we need to configure LiveKit. In the same directory, create `livekit.yaml` with the following content - rememvering to replace `LK_MATRIX_KEY` and `LK_MATRIX_SECRET` with the values you generated!

@@ -0,0 +72,4 @@
+
+You will need to allow ports `7881/tcp` and `50100:50200/udp` through your firewall. If you use UFW, the commands are: `ufw allow 7881/tcp` and `ufw allow 50100:50200/udp`.
+
+

@@ -0,0 +79,4 @@
+
+Unfortunately Continuwuity doesn't yet provide an easy way to do this (We're working on it). You'll need to serve this file using your web server.
+
+Check the existing contents, and add the following (remembering to replace the URL with your one!)

@@ -0,0 +15,4 @@
+:::warning
+
+Element X is known to not be able to do calls on Continwuity. [Track this bug to get updated when the issue is fixed](https://forgejo.ellis.link/continuwuation/continuwuity/issues/1306)
+

@@ -0,0 +10,4 @@
+
+LiveKit should live on its own domain or subdomain. In this guide we use `livekit.example.com` - this should be replaced with a domain you control.
+
+Make sure the DNS record for the (dub)domain you plan to use is pointed to your server.

@@ -0,0 +112,4 @@
+- `/sfu/get`
+- `/healthz`
+- `/get_token`
+

@@ -0,0 +154,4 @@
+
+Livekit includes a built in TURN server which can be used in place of an external option. This TURN server will only work with Livekit, so you can't use it for legacy Matrix calling - or anything else.
+
+

@@ -0,0 +14,4 @@
+
+### 2. Services
+
+Using LiveKit with matrix requires two services - Livekit itself, and a service that grants Matrix users permission to connect to it.

@@ -0,0 +16,4 @@
+
+Using LiveKit with matrix requires two services - Livekit itself, and a service that grants Matrix users permission to connect to it.
+
+You must generate a key and secret to allow the Matrix service to authenticate with LiveKit. `LK_MATRIX_KEY` should be around 20 random characters, and `LK_MATRIX_SECRET` should be around 64. Remember to replace these with the actual values!

@@ -0,0 +120,4 @@
+## Additional Configuration
+
+### TURN Integration
+

@@ -0,0 +2,4 @@
+
+Matrix supports two types of calls:
+
+- Element Call powered by MatrixRTC

@@ -0,0 +10,4 @@
+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 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)

@@ -0,0 +35,4 @@
+      - LIVEKIT_URL=wss://livekit.example.com
+      - LIVEKIT_KEY=LK_MATRIX_KEY
+      - LIVEKIT_SECRET=LK_MATRIX_SECRET
+      - LIVEKIT_FULL_ACCESS_HOMESERVERS=yourdomain.com

@@ -0,0 +80,4 @@
+
+To tell clients where to find LiveKit, we need to modify the file served at `https://example.com/.well-known/matrix/client` (for example https://continuwuity.org/.well-known/matrix/client).
+
+Unfortunately Continuwuity doesn't yet provide an easy way to do this (We're working on it). You'll need to serve this file using your web server.

@@ -0,0 +110,4 @@
+
+```
+
+### 4. Configure your Reverse Proxy

@@ -0,0 +181,4 @@
+- "50300-50400:50300-50400/udp"
+```
+
+### Related Documentation

@@ -0,0 +19,4 @@
+:::tip Generating a secure secret
+A common way to generate a suitable alphanumeric secret key is by using:
+```bash
+pwgen -s 64 1

@@ -0,0 +72,4 @@
+
+### Security Recommendations
+
+For security best practices, see Synapse's [Coturn documentation](https://element-hq.github.io/synapse/latest/turn-howto.html), which includes important firewall and access control recommendations.

@@ -0,0 +120,4 @@
+```
+
+:::warning
+Static credentials are less secure than shared secrets because they don't expire and must be configured in coturn separately. Use shared secret authentication.

@@ -0,0 +132,4 @@
+```
+
+:::caution
+This is not recommended as it allows unauthenticated users to access your TURN server, potentially enabling abuse by bots. All major Matrix clients support authenticated TURN access.

@@ -0,0 +112,4 @@
+
+### 4. Configure your Reverse Proxy
+
+Reverse proxies can be configured in many different ways - so we can't provide a step by step for this.

@@ -0,0 +14,4 @@
+
+### 2. Services
+
+Using LiveKit with matrix requires two services - Livekit itself, and a service (`lk-jwt-service`) that grants Matrix users permission to connect to it.

@@ -0,0 +82,4 @@
+
+Unfortunately Continuwuity doesn't yet provide an easy way to do this (We're working on it). You'll need to serve this file using your web server.
+
+Check the existing content and add the following lines, remembering to replace the URL with your own matrix-rtc-jwt deployment:

@@ -0,0 +182,4 @@
+```
+
+### Related Documentation
+

@@ -0,0 +184,4 @@
+### Related Documentation
+
+- [LiveKit GitHub](https://github.com/livekit/livekit)
+- [LiveKit Connection Tester](https://livekit.io/connection-test) - use with the token returned by `/sfu/get` or `/get_token`

@@ -0,0 +12,4 @@
+- 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 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)
+
+:::warning