Add matrix_rtc.transports support for Synapse (MSC4143)

Enabling the MSC4143 experimental feature without configuring any transports makes Synapse serve an empty response on the RTC transports API. Clients treat that response as authoritative and do not fall back to the org.matrix.msc4143.rtc_foci property in the client well-known, breaking Element Call with a MISSING_MATRIX_RTC_TRANSPORT error.

This makes the playbook wire the LiveKit JWT service URL into the new matrix_rtc.transports Synapse setting, matching what continuwuity, tuwunel and the client well-known already advertise.

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/5522

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Slavi Pantaleev
2026-08-16 08:44:09 +03:00
co-authored by Claude Fable 5
parent df66f1f0b0
commit 4d98ca54a6
3 changed files with 37 additions and 0 deletions
+2
View File
@@ -5191,6 +5191,8 @@ matrix_synapse_delayed_events_enabled: "{{ matrix_rtc_enabled }}"
matrix_synapse_experimental_features_msc4143_enabled: "{{ matrix_rtc_enabled }}"
matrix_synapse_matrix_rtc_transports_livekit_url: "{{ matrix_livekit_jwt_service_public_url if matrix_livekit_jwt_service_enabled else '' }}"
matrix_synapse_experimental_features_msc4222_enabled: "{{ matrix_rtc_enabled }}"
matrix_synapse_experimental_features_msc4354_enabled: "{{ matrix_rtc_enabled }}"