Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable 1-to-1 calls in favor of Jitsi #19249

Closed
maxkratz opened this issue Oct 1, 2021 · 3 comments
Closed

Disable 1-to-1 calls in favor of Jitsi #19249

maxkratz opened this issue Oct 1, 2021 · 3 comments

Comments

@maxkratz
Copy link
Contributor

maxkratz commented Oct 1, 2021

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:

  • 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:
location /.well-known/matrix/client {
	default_type "text/plain";
	add_header Access-Control-Allow-Origin *;
	return 200 '
	{
	        "m.homeserver": {
	                "base_url": "https://my-server.tld"
		},
		"im.vector.riot.jitsi": {
			"preferredDomain": "my-jitsi.tld"
		},
                "im.vector.riot": {
                         "disable_direct_calls": "true"
                }
        }';
}

Have you considered any alternatives?

No response

Additional context

No response

@SimonBrandner
Copy link
Contributor

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.

Duplicate of #16700

@maxkratz
Copy link
Contributor Author

maxkratz commented Oct 1, 2021

@SimonBrandner Thank you, I didn't manage to find the other issue 😵.

@SimonBrandner
Copy link
Contributor

@SimonBrandner Thank you, I didn't manage to find the other issue dizzy_face.

No worries :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants