LiveKit SFU guide #763
Labels
No labels
Blocked
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#763
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
SFU guideto LiveKit SFU guideWhenever 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: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?
Element call is supported, and works well on desktop clients:
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.