element-hq / element-hq/element-call
Reconnection after disconnect due to bad network connectivity ended up with one-way video call
- Dominant language
- TypeScript
- Stars
- 996
- Forks
- 213
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 54
Description
### Steps to reproduce
1. Using call.element.io with a legacy room (no e2e secret provided in the URL) with two people in the call.
2. Have a call on a network with some problems: voice and video were occasionally interrupted.
3. I saw the remote video freeze, associated with a total network issue on my machine (element-web cut off, etc)
4. I returned by refreshing the browser
5. I could see the voice and video of the other party, but they could only see a black screen from me.
6. Refreshing on my side again did not help
7. Moving to a new call URL (now with e2e secret) fixed it.
### Outcome
#### What did you expect?
Reconnection should get back to two way sound & video
#### What happened instead?
Reconnection caused one-way sound & video
### Operating system
_No response_
### Browser information
_No response_
### URL for webapp
call.element.io
### Will you send logs?
Yes
Contributor guide
Research direction
The issue names no source files or tests; start by reproducing the steps at call.element.io with a legacy room and an interrupted network connection. Verify that refreshing after the disconnect restores two-way voice and video, rather than leaving the reporter's video black to the other participant.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100