msgbyte / msgbyte/tailchat

在用版本1.11.8时,音频、视频会话超时,不能进入room(偶尔成功,双方能正常视频通话,概率10%左右)。监控docker“service-core-1”的日志,总是报告如下错误。 || When using version 1.11.8, the audio and video sessions time out and cannot enter the room (occasionally it succeeds and both parties can have normal video calls, the probability is about 10%). Monitoring the logs of docker "service-core-1", the following error is always reported.

Open
#269 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
3.6k
Forks
398
Avg merge
1h 14m
Merged PRs (30d)
2

Description

(1)在双方视频会话时,偶尔会成功,双方可以正常通话,
(2)但是基本上都是报告如下错误,在一方呼叫另一方时,或者,另一方收到请求进入时(都是一直在链接状态,无法进入room),查看日志报如下错误。
ERROR 2e1c16389b1f-29/GATEWAY: [gateway] Request error! RequestTimeoutError : Request is timed out when call 'plugin:com.msgbyte.livekit.roomMembers' action on '73fb1729c372-29' node.
RequestTimeoutError: Request is timed out when call 'plugin:com.msgbyte.livekit.roomMembers' action on '73fb1729c372-29' node.
(3)我的环境是:
在本地搭建了livekit/livekit-server v1.7.2或v1.5.3(使用内嵌turn服务,问题一样的)版本,通过https://meet.livekit.io/custom?liveKitUrl=wss://live.xxx.com&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MzIwMDg1NDgsImlzcyI6IkFQSW40Y3dXWCIsIm5hbWUiOiJ1c2VyMSIsIm5iZiI6MTczMTkyMjE0OCwic3ViIjoidXNlcjEiLCJ2aWRlbyI6eyJyb29tIjoibXlyb290Iiwicm9vbUpvaW4iOnRydWV9fQ.BkCvGOl06DKCeYzfInXar4EaK2k7cFtJI....
可以正常查看


(1) During the video conversation between the two parties, it occasionally succeeds and the two parties can talk normally.
(2) But basically the following errors are reported. When one party calls the other party, or when the other party receives a request to enter (both are always in the link state and cannot enter the room), the following error is reported when checking the log.
ERROR 2e1c16389b1f-29/GATEWAY: [gateway] Request error! RequestTimeoutError : Request is timed out when call 'plugin:com.msgbyte.livekit.roomMembers' action on '73fb1729c372-29' node.
RequestTimeoutError: Request is timed out when call 'plugin:com.msgbyte.livekit.roomMembers' action on '73fb1729c372-29' node.
(3) My environment is:
Livekit/livekit-server was built locally v1.7.2 or v1.5.3 (using the embedded turn service, the problem is the same) version, through https://meet.livekit.io/custom?liveKitUrl=wss://live.xxx.com&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MzIwMDg1NDgsImlzcyI6 IkFQSW40Y3dXWCIsIm5hbWUiOiJ1c2VyMSIsIm5iZiI6MTczMTkyMjE0OCwic3ViIjoidXNlcjEiLCJ2aWRlby I6eyJyb29tIjoibXlyb290Iiwicm9vbUpvaW4iOnRydWV9fQ.BkCvGOl06DKCeYzfInXar4EaK2k7cFtJI....
Can be viewed normally

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the service-core-1 logs and reproduce the failed call or room-entry flow using the reported Tailchat 1.11.8 setup. Compare behavior with the listed livekit-server versions and trace the plugin:com.msgbyte.livekit.roomMembers RequestTimeoutError; done means participants can enter rooms reliably without this timeout.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
audio-video-rtc, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.