Hey there,
I have built a but that joins meeting s and transcribed them, but when I test it on another account I don’t get the window to ask for permission to record the meeting. This means that the bot never gets the audio and therefore never transcribes it. I should note that the account is recording the meeting with the built-in recording feature.
Also note that the bot is working perfectly on my account.
@noahviktorschenk, .
What SDK are you using for your bot ? Linux ?
Can you provide more details about what you’re looking to achieve? Is the user in your account when testing the bot experience?
@donte.zoom Ah, yeah, I am using the Meeting SDK for Linux. Technically I am using the py-zoom bindings, but they build on the Linux SDK. Also, I am using the latest version of the SDK.
Hey @noahviktorschenk ,
We run meeting bots at scale using the Linux SDK and have definitely encountered this issue, so hopefully I can point you in the right direction here!
It sounds like this is likely related to how Zoom’s recording consent works through the meeting SDK, specifically as it pertains to meeting hosts.
In order for the bot to record, it must prompt the host of the meeting for recording permission. The confusing thing here is that it’s not always obvious who the host of the meeting is, since even a non-host can have host controls depending on the settings of the meeting.
One common scenario we run into is when there is a mismatch between the account the meeting is created from and the one that the attendee is signed into when joining the meeting. For instance, if the meeting is created from the Zoom Google Calendar add-on, when the connected Zoom account is different than the account you’re actually joining the meeting with.
Another that we often see is when the Zoom meeting is being created programmatically, in which case the host would be a different account than the one you’re testing on.
One easy way to debug this is to add some logging when a participant joins. Specifically, logging the IsHost
property on the IUserInfo class instance. This should help confirm whether or not this is the specific issue.
Hopefully this helps!
Hey Amanda
Thank you so much for the detailed breakdown. We will add a bit more debugging to make it clearer.
Is there any way to send the permission popup to someone else, or is only the actual host able to do that? Also is there a way to give permission after having closed the popup? Or to programmatically ask for permission again after it has been declined once?
Thanks
Hi @noahviktorschenk, unfortunately only hosts are able to grant permissions
Following this thread, it doesn’t look like there’s a programatic way to give host permissions to other participants
One other option is to set all other participants as co-hosts where participants will get the same meeting management permissions as the host. In this case, all participants will be able to let in participants and grant recording permissions but gives other participants full access to control the meeting
Best of luck!
Hey @amanda-recallai Thanks again.
Just tested it another time, this time making sure I was using the account that is connected to the Zoom Google Calendar add-on and it still does not pop up.
We do record all our tours using Zooms built-in recording feature. I get the popup when I join the meeting for this reason, but at that time the bot hasn’t joined yet. Then I don’t get another popup when the bot Joins. Is this expected?
Also, sadly making the participants co-hosts does not work in our case.
Thanks
@donte.zoom
So it turns out we have local recording turned off on the account. Could that be the reason?
If so, is there any way to circumvent this, as we do not want to turn local recording on, on this account?
Thanks.
@noahviktorschenk ,
Perhaps, as a test, you can create a Zoom test account enable local recording, then have a bot join the meeting to see if the host is prompt as expected.
@donte.zoom
Yes, it seems to work when I turn it on, but I cannot turn it on for my usecase
@donte.zoom Any thoughts on this?