I’m building a bot that needs participant-separated audio without being able to get the app pre-approved from the IT Admins of the Meeting Organizer. I’m deciding between two paths and need advice on which one hits more “Admin Brick Walls”:
RTMS: Blocked if the admin blocks the “in-meeting app approval” flow.
Linux SDK: Blocked if the admin disables “Local Recording” permissions for participants.
Questions:
In your experience, which setting is more commonly locked down by default in Enterprise?
What are the default settings?
Does anyone foresee Zoom deprecating the “Local Recording” route for bots (using ZAK or OBF token) in favor of RTMS?
Trying to avoid a high-churn architecture. Thanks!
You can not get separate audio from Zoom. Zoom only sends the combined.
Zoom allows recording separate audio, but the admin must approve it.
You could use RTMS to get some audio, but you have to pay for usage and be approved for use.
I am concerned why you want the audio and do not want permissions to block you.
You will need to explain a legitimate use case for this.
For the local recording permissions, is it the Admin or the Meeting Organizer/Host?
For RTMS, I am fine with paying for the usage and getting the app published on the marketplace after Zoom’s review.
I have a done a POC for both of these but Zoom does not allow scenarios where the app developer is not the Meeting Organizer without publishing the app, so I cannot test the above configs.
I can help add some clarity on the local recording piece. Local recording can be blocked by both admin settings, as well as host-level settings in a Zoom meeting. If local recording is blocked at either level, your Linux Meeting SDK bot will not be able to request recording permission from the meeting host. By default, local recording is not disabled for new Zoom accounts, though it’s more likely to be blocked in an enterprise setting.