-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
setup element call as an alternative to jitsi #3559
Comments
I have created a PR to try and add Element call to the playbook. |
@wjbeckett I tried both element-web and element-call and I see a blank screen in the call window |
Failed to get JWT from RTC session's active focus URL of https://sfu-jwt.example.com. Error: SFU Config fetch failed with exception Error: SFU Config fetch failed with status code 500 |
@wjbeckett
|
@saket424 yes, ita because it's expecting to lookup a user in Matrix Authentication Service (MAS), which isn't implement in this playbook yet. MAS is a requirement of Element Call Sonita can perform user lookups. You'll notice the error in your last comment references openID (openIDSFU.ts:71:23). |
@wjbeckett Here is another blog post I cam across related to MAS just as a reference https://sspaeth.de/2024/08/matrix-server-with-nextcloud-login/ |
@wjbeckett I've downloaded your version and applied it to my server. I've even seen |
Element recently announced that element call is enabled by default in element x and element desktop https://element.io/blog/we-have-lift-off-element-x-call-and-server-suite-are-ready.
There is documentation available about how to setup element call with the latest LTS version of ESS
https://ems-docs.element.io/books/element-on-premise-documentation-lts-2404/page/setting-up-element-call.
Maybe we can track progress in this issue?
The text was updated successfully, but these errors were encountered: