LiveKit SFU guide #763

Open
opened 2025-04-16 00:55:38 +00:00 by Jade · 3 comments
Owner

Now that Element have disabled the fallback SFU in call, it'd be good to have a setup guide, as this seems to be a FAQ.

Now that Element have disabled the fallback SFU in call, it'd be good to have a setup guide, as this seems to be a FAQ.
Jade changed title from SFU guide to LiveKit SFU guide 2025-04-16 00:55:58 +00:00

Whenever I figure this out myself, I'll try to leave some docs documenting how I did it :)

For anyone else in the same boat I suggest checking out this post (even though it's a lil old): https://blog.kimiblock.top/2024/12/24/hosting-element-call/

Whenever I figure this out myself, I'll try to leave some docs documenting how I did it :) For anyone else in the same boat I suggest checking out this post (even though it's a lil old): https://blog.kimiblock.top/2024/12/24/hosting-element-call/

Is Element Call supported? I tried to establish a call between Element Web (https://app.element.io) and Element X on Android but the call hangs indefinitely with "Waiting for media". I added this in /.well-known/matrix/client:

"org.matrix.msc4143.rtc_foci": [
    {
      "livekit_service_url": "https://jwt.call.element.io",
      "type": "livekit"
    }
  ]

The same setup works with synapse. I also tried to replace the continuwuity binary by the tuwunel one in the exact same docker image with the exact same config and it worked.

If Element Call is not supported, how can I track the implementation progress?

Is Element Call supported? I tried to establish a call between Element Web (https://app.element.io) and Element X on Android but the call hangs indefinitely with "Waiting for media". I added this in `/.well-known/matrix/client`: ```json "org.matrix.msc4143.rtc_foci": [ { "livekit_service_url": "https://jwt.call.element.io", "type": "livekit" } ] ``` The same setup works with synapse. I also tried to replace the continuwuity binary by the tuwunel one in the exact same docker image with the exact same config and it worked. If Element Call is not supported, how can I track the implementation progress?
Author
Owner

Element call is supported, and works well on desktop clients:

image

Unfortunately, there is a subtle bug in the Simplified Sliding Sync service used by the Element X clients that means that some of the data that EC needs to do end to end encryption isn't sent. We haven't had time to track down and fix that bug yet, but we'll include an update in teh changelog when we have fixed it & verified the fix. I'll also send an update here if you're interested.

Element call is supported, and works well on desktop clients: ![image](/attachments/ce874f59-1aff-4ef0-94f0-ba2eb5a0729e) Unfortunately, there is a subtle bug in the Simplified Sliding Sync service used by the Element X clients that means that some of the data that EC needs to do end to end encryption isn't sent. We haven't had time to track down and fix that bug yet, but we'll include an update in teh changelog when we have fixed it & verified the fix. I'll also send an update here if you're interested.
415 KiB
Sign in to join this conversation.
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity#763
No description provided.