From ef089c18009fc1b95fd272b8cb500e9f70472127 Mon Sep 17 00:00:00 2001 From: stratself Date: Tue, 17 Mar 2026 14:03:00 +0000 Subject: [PATCH] docs(livekit): Put livekit+coturn port clash notice in a tip box * reworded first part of external TURN integration * add restart/recreate instructions to apply final TURNs changes --- docs/calls/livekit.mdx | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/calls/livekit.mdx b/docs/calls/livekit.mdx index a493c48fe..fd79de409 100644 --- a/docs/calls/livekit.mdx +++ b/docs/calls/livekit.mdx @@ -210,18 +210,22 @@ ports: ### if you're using `network_mode: host`, you can skip this part ``` -Remember to allow the new `3478/udp` and `50100:50200/udp` ports through your firewall. +Recreate the LiveKit container (with `docker-compose up -d livekit`) to apply these changes. Remember to allow the new `3478/udp` and `50100:50200/udp` ports through your firewall. ### Integration with an external TURN server -If you've already set up coturn, there may be a port clash between the two services. To fix this, make sure coturn's `min-port` and `max-port` do not overlap with LiveKit's range: +If you've already [set up coturn](./turn), you can configure Livekit to use it. + +:::tip Avoid port clashes between the two services + +Before continuing, make sure coturn's `min-port` and `max-port` do not overlap with LiveKit's port range: ```ini +# in your coturn.conf min-port=50201 max-port=65535 ``` - -To improve LiveKit's reliability, you can configure it to use your coturn server. +::: Generate a long random secret for LiveKit, and add it to your coturn config under the `static-auth-secret` option. You can add as many secrets as you want, so set a different one for LiveKit to use. @@ -245,6 +249,8 @@ rtc: secret: "COTURN_SECRET" ``` +Restart LiveKit and coturn to apply these changes. + ## Testing To test that LiveKit is successfully integrated with Continuwuity, you will need to replicate its [Token Exchange Flow](https://github.com/element-hq/lk-jwt-service#%EF%B8%8F-how-it-works--token-exchange-flow).