element-call icon indicating copy to clipboard operation
element-call copied to clipboard

Error Code: MISSING_MATRIX_RTC_FOCUS

Open s0div opened this issue 1 month ago • 2 comments

Steps to reproduce

  1. Where are you starting? What can you see? Element-web, dm with user.
  2. What do you click? Voice call button

It seems that voice-call option stopped to work with new Element version: 1.12.5. Is there any way to change where the Element client reads the homeserver name from? Everything else works — every request uses the correct FQDN — but when the Element client tries to fetch the /.well-known file, it uses not FQDN "example" instead of "example.com" to reach the endpoint. In my homeserver.yaml I have server_name set to "example".

I saw a similar issue here: https://github.com/element-hq/element-call/issues/3566

Outcome

What did you expect?

Working element-call feature

What happened instead?

Image

Operating system

Ubuntu

Browser information

Firefox 145.0.2

URL for webapp

app.element.io

Application version

Element version: 1.12.5

Homeserver

No response

Will you send logs?

No

s0div avatar Dec 03 '25 11:12 s0div

I'm having the same error using Element for Windows. It was working before the latest element update.

versão do Element: 1.12.5 Versão Crypto: Rust SDK 0.14.0 (c3b7918), Vodozemac 0.9.0

Server: Dendrite docker matrixdotorg/dendrite-monolith:latest

deoliveiraedu avatar Dec 03 '25 13:12 deoliveiraedu

Yep, it's known. We're working on a fix.

Half-Shot avatar Dec 03 '25 13:12 Half-Shot

Hi folks, so an update on what we did and how we fixed it.

In Element Web v1.12.5, we made a change that allowed Element Call to be used for voice calls for the first time, in DMs.

Because Element Web did not allow you to pick a platform for voice calls, this meant that it would pick the preferred supported platform. However because Element Web does not do a great job at detecting support for Call, users were presented with MISSING_MATRIX_RTC_FOCUS errors. Unless you were very eagle-eyed, you would not notice that you were now using EC rather than legacy calling.

In Element Web v1.12.6, we've now allowed users to pick a preferred calling platform so users can still pick legacy calling for the previous behaviour.

In the future we'd like to make the change so that if your environment does not support EC, it will not be listed as an option.

Half-Shot avatar Dec 22 '25 15:12 Half-Shot

I'm going to close this in favor of https://github.com/element-hq/element-web/issues/31405.

Half-Shot avatar Dec 22 '25 15:12 Half-Shot