I have a question, it seems if the meeting is not in the same account as the SDK, I cannot join it with the role = 1? It will return signature is invalid, on that case? Is this right now not supported?
Context:
- Added support for starting a webinar as host.
- Added support for panelists and hosts to join webinars.
As 1.8.0 seems added those functionalities above just want to make sure, what it actually means.
Do the SDK detect panelist emails and enable the panelist view automatically? Do we need to pass rote 1 for panelists?
Bumping this up because Iâm looking for a response to this as well. Currently joining the meeting with a role = 0 as panelist is not working. And trying role = 1 gives the old error of: cant start webinar from web (even though a host is able to; this is me trying to join as a panelist).
I have try also to start a webinar from websdk 1.8.0 and i get the following response
method: âjoinâ, status: false, result: âNot allow to start webinar from web.â, errorMessage: âNot allow to start webinar from web.â, errorCode: 3609
Hey @developer-whova, @hassan2,
Correct, you are only able to start meetings (use role 1) that you (the owner of the JWT App) own.
Now, you can use role 1 when generating a signature to start a Webinar with the Web SDK.
To have panelists join pass in role 0 to the signature, and the panelist email as the userEmail value. Make sure the panelist email is also added to the Webinar settings on the Zoom Web Portal.
Thanks,
Tommy
Hey @ldal,
Can you please provide steps to reproduce the issue and the version of the Web SDK you are using?
Thanks,
Tommy
@tommy for panelists to join, we can send the invites using the REST API too, right? Thatâs what Iâve done in my case. Add panelists to a webinar, and then use the host to start the webinar.
Iâm able to start the webinar as the host no problem, but joining as a panelist is where it doesnât work unfortunately.
The only way I can get it to work is if I promote a user to a panelist from within a meeting. Then when that user leaves and re-joins, they maintain their panelist status.
Hoping that helps get to the bottom of this issue!
Thanks again for your help.
@tommy This is exactly the same problem I encountered with web SDK 1.8.0. Reproduce steps:
- Add a webinar panelist on zoom dashboard
- Pass panelist email as userEmail and role=0 on joining the meeting in SDK
- The panelist can only have the view-only attendee view, not the panelist view.
zoom websdk 1.8.0
the signature below is calculated from the php (with role 1)
var meetConfig = {
apiKey: #####,
meetingNumber: ######,
userName: âtest nameâ,
userEmail: âtest@email.comâ,
passWord: #####,
leaveUrl: âhttps://www.zoom.usâ,
signature: ######,
role: 1,
};
ZoomMtg.preLoadWasm();
ZoomMtg.prepareJssdk();
ZoomMtg.init({
leaveUrl: meetConfig.leaveUrl,
screenShare: 1,
disableInvite: 0,
success: function(initResp) {
console.log(initResp);
ZoomMtg.join({
signature: response.data,
apiKey: meetConfig.apiKey,
meetingNumber: meetConfig.meetingNumber,
userName: meetConfig.userName,
userEmail: meetConfig.userEmail,
passWord: meetConfig.passWord,
success: function(joinResp){
console.log(joinResp);
$(â#nav-toolâ).hide();
console.log(âjoin meeting successâ);
},
error: function(joinResp) {
console.log(joinResp);
}
});
},
error: function(initResp) {
console.log(initResp);
}
});
thank you
Hi @ldal,
I can see that youâre correctly passing in role 1 to start a webinar, so that part looks good. Can you share a screenshot of this error message in action in the browser console? Can you also confirm that youâre using credentials from the JWT app under your account?
Thanks!
Will
Thanks for providing these details. I will escalate this to our team to help investigateâin the meantime, is it possible to share a screencast video or screenshot of these steps in action? This would be really helpful. (ZOOM-195352)
Thanks!
Will
we had to put the same email as the primary zoom zccount not user⌠thank you
Can you please let me know the Webinar ID or UUID that youâve run into this issue with?
Thanks,
Will
Thanks @hassan2! Weâre still looking into this. Hope to have an update for you shortly.
Best,
Will
Hey @hassan2,
We are still looking into this issue. We will provide you with an update as soon as we can.
Thanks,
Tommy
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.