Group voice and video calls with MatrixRTC and LiveKit
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
CI / Admin panel (push) Canceled after 0s
CI / Web client (push) Canceled after 0s
CI / Test (ubuntu-latest) (push) Canceled after 0s
CI / Test (windows-latest) (push) Canceled after 0s
CI / Storage tests on PostgreSQL (push) Canceled after 0s
CI / Complement (federation off) (push) Canceled after 0s
CI / golangci-lint (push) Canceled after 0s
CI / Smoke test the binary (push) Canceled after 0s
CI / Admin panel (push) Canceled after 0s
CI / Web client (push) Canceled after 0s
Every call in the web client now goes through MatrixRTC with a LiveKit
SFU, the model Element Call and Element X use; the legacy 1:1 m.call.*
calls are gone. In a room of two the other person is rung and can answer
or decline; in a bigger room a banner offers to join the call. Calls show
a grid of participant tiles with mute, camera, screen sharing and leave,
and media is end-to-end encrypted in encrypted rooms.
Server:
- MSC4140 delayed events (send/state with a delay, plus the
delayed_events list/restart/cancel/send API), stored and scheduled, so
a member whose client drops off is taken out of the call.
- POST /user/{userId}/openid/request_token, which lk-jwt-service uses to
hand out LiveKit tokens.
- org.matrix.msc4143.rtc_foci in /.well-known/matrix/client, configured
under client_api.rtc.
- Room presets let members send call membership state.
- Migration 0014 for both SQL dialects.
Deploy: LiveKit and lk-jwt-service in compose (calls.yml) and the helm
chart. Docs: docs/calls.md, configuration and deployment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
325431a5be
commit
76dfc98a86
49 files changed
+3849
-432
No files matched your search
+23
-3
@@ -103,9 +103,11 @@ client_api:
|
||||
# 0 means no expiry. WARP_REFRESH_TOKEN_LIFETIME
|
||||
refresh_token_lifetime: 0s
|
||||
|
||||
# Relay servers for voice and video calls, handed to clients by
|
||||
# GET /voip/turnServer. With no uris, calls only connect where the two
|
||||
# browsers can reach each other directly (the same network, mostly).
|
||||
# Relay servers for Matrix 1:1 VoIP, handed to clients by
|
||||
# GET /voip/turnServer. Warp's web client doesn't use them: its calls go
|
||||
# through LiveKit (rtc below), which needs no TURN of its own here. This
|
||||
# is for other Matrix clients that still place legacy 1:1 calls; with no
|
||||
# uris, theirs only connect where the two can reach each other directly.
|
||||
#
|
||||
# With shared_secret (coturn's `use-auth-secret` + `static-auth-secret`)
|
||||
# every user gets credentials that expire after user_lifetime. username
|
||||
@@ -120,6 +122,24 @@ client_api:
|
||||
username: "" # WARP_TURN_USERNAME
|
||||
password: "" # WARP_TURN_PASSWORD
|
||||
|
||||
# Group calls (MatrixRTC). Warp carries no call media itself: clients
|
||||
# publish to a LiveKit SFU and get a token for it from the LiveKit JWT
|
||||
# service (lk-jwt-service), which checks who they are with an OpenID
|
||||
# token from this server. Its URL is advertised to clients in
|
||||
# /.well-known/matrix/client; leave it empty for no group calls.
|
||||
# See docs/calls.md.
|
||||
rtc:
|
||||
livekit_service_url: "" # WARP_RTC_LIVEKIT_SERVICE_URL
|
||||
# e.g. "https://livekit-jwt.example.org"
|
||||
|
||||
# Delayed events (MSC4140): events a client schedules now for the server
|
||||
# to send later unless it pushes them back. A group call member's "left
|
||||
# the call" is one, so someone whose browser crashes still leaves.
|
||||
# max_delay 0 turns them off.
|
||||
delayed_events:
|
||||
max_delay: 24h # WARP_DELAYED_EVENTS_MAX_DELAY
|
||||
max_per_user: 100 # WARP_DELAYED_EVENTS_MAX_PER_USER
|
||||
|
||||
# Per-endpoint rate limiting. Each bucket allows `burst` requests back
|
||||
# to back and returns one slot every `interval`, per client address.
|
||||
# Login and registration get their own, tighter, buckets because they
|
||||
|
||||
Reference in new issue
Block a user