在用版本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.

[zhudemiao]

（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

[zhudemiao]

我把vi ./server/plugins/com.msgbyte.livekit/web/plugins/com.msgbyte.livekit/package.json
升级到：
"dependencies": {
"@livekit/components-core": "^0.6.15",
"@livekit/components-react": "^1.0.8",
"@livekit/components-styles": "^1.0.12",
"livekit-client": "^1.15.13",
"lodash": "^4.17.21",
"zustand": "4.3.9"
},
"devDependencies": {
"@types/lodash": "^4.14.196",
"@types/styled-components": "^5.1.26",
"react": "18.2.0",
"react-router": "^6.8.2",
"styled-components": "^5.3.6"
}
}
错误是同样的。

---

I put vi ./server/plugins/com.msgbyte.livekit/web/plugins/com.msgbyte.livekit/package.json
Upgrade to:
"dependencies": {
"@livekit/components-core": "^0.6.15",
"@livekit/components-react": "^1.0.8",
"@livekit/components-styles": "^1.0.12",
"livekit-client": "^1.15.13",
"lodash": "^4.17.21",
"zustand": "4.3.9"
},
"devDependencies": {
"@types/lodash": "^4.14.196",
"@types/styled-components": "^5.1.26",
"react": "18.2.0",
"react-router": "^6.8.2",
"styled-components": "^5.3.6"
}
}
The error is the same.

[zhudemiao]

此外，在https://meet.livekit.io/custom?liveKitUrl=wss://live.xxx.com&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MzIwMDg1NDgsImlzcyI6IkFQSW 40Y3dXWCIsIm5hbWUiOiJ1c2VyMSIsIm5iZiI6MTczMTkyMjE0OCwic3ViIjoidXNlcjEiLCJ2aWRlbyI6e yJyb29tIjoibXlyb290Iiwicm9vbUpvaW4iOnRydWV9fQ.BkCvGOl06DKCeYzfInXar4EaK2k7cFtJI....测试时，用如下方法
docker run -d --rm livekit/livekit-cli:v2.1.5 load-test --url wss://live.xxx.com --api-key A**4cwWX --api-secret plcygaRnfnnYcCdXUDPC -room myroot --video-publishers 50
是正常的。能够增加人员

---

Additionally, at https://meet.livekit.io/custom?liveKitUrl=wss://live.xxx.com&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MzIwMDg1NDgsImlzcyI6IkFQSW 40Y3dXWCIsIm5hbWUiOiJ1c2VyMSIsIm5iZiI6MTczMTkyMjE0OCwic3ViIjoidXNlcjEiLCJ2aWRlbyI6e yJyb29tIjoibXlyb290Iiwicm9vbUpvaW4iOnRydWV9fQ.BkCvGOl06DKCeYzfInXar4EaK2k7cFtJI.... When testing, use the following method
docker run -d --rm livekit/livekit-cli:v2.1.5 load-test --url wss://live.xxx.com --api-key A**4cwWX --api-secret plcygaRnfnnYcCdXUDPC -room myroot - -video-publishers 50
is normal. Able to add personnel

[moonrailgun]

it looks microservice can not call each.

please make sure your plugin is run success and connected into tailchat network.

you can visit http://your-instance/health to check all connected node and available service. make sure com.msgbyte.livekit is in it