element-hq / element-hq/element-web

Group calls don't respect the matrix.org STUN fallback option

Open
#25,439 0 comments 0 reactions 0 assignees View on GitHub
A-Element-Call O-Uncommon S-Major T-Defect Z-Labs
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

1. Use a homeserver with no STUN or TURN server configured
2. Enable the matrix.org STUN fallback option in voice/video settings, allowing you to talk to people on other homeservers that do have TURN
3. Try the same with an Element Call call

### Outcome

#### What did you expect?

To connect to the other participant

#### What happened instead?

Unless they have publicly routable IPv6 adresses, I get an ICE failure, because even though the other participant is providing a TURN allocation for both of us to use, I'm only sending them my private IPv4 adresses as candidates, and so they can't CreatePermission on the TURN server with my actual public IPv4 address. This wouldn't happen if group calls with Element Call respected the matrix.org STUN fallback option.

### Operating system

NixOS unstable

### Browser information

Firefox 112.0.2

### URL for webapp

develop.element.io

### Application version

Element version: 0a5173f25802-react-269a3481772d-js-a2d1dee0a1ae Olm version: 3.2.14

### Homeserver

Not relevant

### Will you send logs?

No

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.