Hi! We encountered a problem when reconnecting a host with poor connection quality.
Create a conference.
Turn off the Internet at the host (in-flight mode or devtools->network->offline).
Reload the page, then turn on the internet.
Reconnect to the same conference.
The host role remains with the participant who left the meeting, but his connection is no longer relevant. At the same time, the second connection is forced to wait until the socket connection on the side of your server is closed.
This is a problem in our application (probably not only in ours) since our host is the teacher leading the lesson. And when reconnecting, he loses his privileges.
The role_type parameter in both connections is 1
zoom web sdk 1.5.0.
Thank you for your post! Video SDK v. 1.6.0 has been released. Could you try updating the package in your application and let me know if the issue still persists?
I’ve already done that. The problem remains. You can easily reproduce it yourself and check it out.
@rehema.zoom , @vic.yang
I found some forum posts that seem to directly address our problem. But they do not give an answer how to get rid of the host waiting.
The state:'Fail',reason:'connection error') return value indicates the video sdk cannot reach any available servers. It usually occurs when the network is disconnected.
And for why others can still see the disconnected user in the session, our server has a hearbeat detection mechanism, when the disconnection exceeds two minutes, the user will be shown as leaving(disappeared in the user list).
We do this so that others don’t see you rejoining the session due to a short-term network…
After 3 minutes, if the host still does not join the session, the server will re-assign the host to another participant.
It looks like this behavior was originally intended, and it’s your developers who don’t consider it a bug. However, there must be parameters to regulate this, because it causes problems.
Thanks for your feedback.
We will add the ‘reclaim host’ function in the next release. Maybe it can solve your problems.
The original host can reclaim the host privilege if he/she is not the host in a session.
role_type =1 → original host.
Is the next release planned, which will include this feature, within a month?
It will be included in the next release. The release date will be around the end of February.
Providing an update here. We had to push back this feature to our March release schedule due to some additional dependencies.
You can subscribe to release updates via email here to be notified when this is released in March:
@vic.yang @tommy !
When is it planned to release a release with this fix ? For us, this problem is critical, because customers regularly encounter it.
We will release the next version around the end of March.
Release 1.7.0. fixed the problem. I used reclaimHost() and everything works fine. Thank you =)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.