Failed call 5th Feb
Open
Nobody has claimed this yet.
bug
feature: call 📹
feature: frontend 🖌️
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
- Check readyState on video and reconnect (with increasing delay) if state is 0 check of speakers
- Check how janus behaves if publisher connection is closed, what happens with the receiver connections
- Allow to access chrome://webrtc in desktop client
- show avatar with loading spinner instead of empty/black space
- @ShGKme resumed his websocket connection
- 30s later he created a new publisher connection
- there were no force reconnects
- the timing strangely aligned with daniel joining the room (talk php word)
- Selecting the video element in DOM and afterwards cehck various HTML attributes on
$0 - Re-requesting the offer with
OCA.Talk.SimpleWebRTC.connection.requestOffer("PUT_SESSIONID_HERE", "video")made audio and video work
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the failed-call timeline and the listed checks for video readyState, speaker state, and Janus behavior when a publisher connection closes. Use the desktop client's chrome://webrtc access and the mentioned SimpleWebRTC.connection.requestOffer call to reproduce or inspect the failure. Done means the reconnection behavior, receiver handling, and loading avatar state are defined and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100