Element Call
summary
Element Call is a decentralized, federated video conferencing stack built on Matrix RTC using a LiveKit-based SFU deployed alongside Home Servers, with an election that adapts to emerging state and seamless failover. Synapse implements reliable RTC room state with heartbeats and delayed events to avoid split-brain. Clients embed the web widget or integrate natively (CallKit, picture‑in‑picture). Guest access works by spinning temporary accounts on a guest Home Server and guest access via knock approval. Measured scale: ~500 participants per machine with HD streams; media routing by LiveKit SFU.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:37Matrix RTC overview
- 2:05Matrix ecosystem
- 3:13History of Matrix calling
- 4:32Jitsi vs Matrix calling
- 5:23Lessons learned in VoIP
- 6:42Introduction to Matrix RTC
- 8:19RTC backend design
- 10:46Matrix RTC technical details
- 12:21Reliable room state
- 13:53Element Call scenarios
- 15:21Federated backend model
- 17:36SFU efficiency
- 20:11Embedding strategies
- 22:14Single implementation model
- 22:48Call ringing and integration
- 25:47Guest access functionality
- 28:16Live demo and features
- 34:31Native mobile demo
- 35:59Talk summary
- 37:02Q&A session
related talks
53mAn Open Source, Cross-platform Communications Layer for the Metaverse
23mMoQ: Not Another Tech Demo
06mApplication Chats
27mMembrane SFU: Bringing WebRTC to Elixir
32mBuilding Real-Time Audio/Video Apps with Flutter and WebRTC
38mReal-time Communication on Mobile
16mDePIN Evolution
11mKeynote: Real-time Communication for Today and Future Experiences
