You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disable 1-to-1 calls in all Element clients that are connected to the homeserver, e.g., via a configuration option and use Jitsi instead.
Why would you like to do it?
We are running a Synapse/Element combination at our department at the technical university of Darmstadt with a large number of public rooms for different courses for students. Currently, the UX for calls is very different in personal rooms and in group rooms. It would be nice to be able to completely disable the 1-to-1 call feature for all element clients on our instance to also use Jitsi in personal rooms.
How would you like to achieve it?
Two configuration options:
For the web-based version, via a configuration option, e.g.:
"disable_direct_calls": true,
For all other clients (desktop app, mobile apps, etc.), via a homeserver well-known directive, e.g. with nginx:
It seems you're not the only one to have come across this bug, as it's been reported previously. I'm going to close this issue now so we can focus on the older issue. Please watch, vote or comment on that issue if there is any additional information you can provide.
Your use case
What would you like to do?
Disable 1-to-1 calls in all Element clients that are connected to the homeserver, e.g., via a configuration option and use Jitsi instead.
Why would you like to do it?
We are running a Synapse/Element combination at our department at the technical university of Darmstadt with a large number of public rooms for different courses for students. Currently, the UX for calls is very different in personal rooms and in group rooms. It would be nice to be able to completely disable the 1-to-1 call feature for all element clients on our instance to also use Jitsi in personal rooms.
How would you like to achieve it?
Two configuration options:
Have you considered any alternatives?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: