RocketChat / RocketChat/Rocket.Chat
1:1 calls sometimes not working correctly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
We're dealing with the problem, that sometimes 1:1 can not be initiated correctly.
Sometimes, if a user calls, the incoming or outgoing call pop-up window doesn't appear.
Sometimes the pop-up does appear and we can click to answer the call, but nothing happens and an error toast-message appears (e.g. No repsonse).
Sometimes the calling person sees the popup and hears the ringtone, but the called person does not see the popup.
It's instantly resolved after refreshing Rocket.Chat (Command + R) on one or sometimes both sides and than it works for a certain amount of time without any issue. But after one or two days (or maybe after app inactivity) the symptoms happen again.
We're using the Rocket.Chat Electron-App.
We're using authentication tokens with an expiration setting of now + 1hour.
Steps to reproduce:
- Go into a 1:1 direct message.
- Click the video call button
Expected behavior:
Call popup should appear for both persons involved in the direct message.
Actual behavior:
Call popup sometimes does not appear or if it appears, there is an error message. Sometimes it works correctly.
Server Setup Information:
- Version of Rocket.Chat Server: 7.4.1
- License Type: Starter
- Number of Users: 24
- Operating System: Ubuntu
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: active
- NodeJS Version: v22.13.1
- MongoDB Version: 6.0.13
Client Setup Information
- Desktop App or Browser Version: 4.3.0
- Operating System: macOS
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
No files, tests, or code entry points are named. Start in the Electron app by reproducing a 1:1 video call after the reported inactivity or token-expiration period, then compare both participants' popup and error-toast behavior before and after refreshing. Done means calls reliably show the popup and can be answered for both users without a refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- audio-video-rtc, desktop-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100