RTMS+Meeting start/stop control flow

[LiveVoice]

Hello there

We started developing an RTMS App that should allow our customers to import audio of their Zoom Meetings (and Webinars) into our system.

The basic idea is: the customer registers the meeting ID he wants to import with us and installs our Zoom RTMS app; when he starts a meeting, we receive the meeting_started callback and if the meeting id is registered with us, we send a patch request to /v2/live_meetings/#{meeting_id}/rtms_app/status to enable RTMS. I’d then expect to get back an rtms_started event and then can negotiate to get media via the websockets.

I’ve got a basic prototype up and running in “Local Test” mode, and basically it works; however I get rtms_started for every meeting I start, not just the ones i do (or would) explicitely call the Zoom API with the patch request to enable rtms.

I did turn off autostart both in the app config itself (Marketplace → The app → Features → Surface “allow auto-start for rtms” is unchecked) as well as in the account (Profile → My Account → Account Management → Account Settings → Zoom apps: “Auto-open an app in meetings” is unchecked, Meeting>“Auto-start apps that access shared realtime meeting content” is empty. Meeting>“Share realtime meeting content with apps” is checked however, but that should not trigger auto-starting anything.)

So, why do I get an rtms_started event for EVERY meeting I start, not only for those where I explicitely call to enable it via API?

And, follow-up question: I now send an RTMS stop request to meeting ID that sends rtms_started but is not registered and get back an rtms_stopped event with reason “stop_bc_user_triggered”; if I don’t do that, I get an rtms_stopped event after about a minute with reason “stop_bc_connection_timeout”.
So that led me to the question: are RTMS credits consumed for the time a media (WS) connection is actually open or in general for the time between rtms_started and rtms_stopped events?
(And: does the extra stop API call cost something?)

Thank you for reading and I’m glad for all hints, explanations, improvement suggestions and solutions!
Best, Chris

[chunsiong.zoom (Chun Siong)]

@LiveVoice

I did turn off autostart both in the app config itself (Marketplace → The app → Features → Surface “allow auto-start for rtms” is unchecked) as well as in the account (Profile → My Account → Account Management → Account Settings → Zoom apps: “Auto-open an app in meetings” is unchecked, Meeting>“Auto-start apps that access shared realtime meeting content” is empty. Meeting>“Share realtime meeting content with apps” is checked however, but that should not trigger auto-starting anything.)

@LiveVoice you need to make sure this is disabled at the user settings level as well.

@LiveVoice

And, follow-up question: I now send an RTMS stop request to meeting ID that sends rtms_started but is not registered and get back an rtms_stopped event with reason “stop_bc_user_triggered”; if I don’t do that, I get an rtms_stopped event after about a minute with reason “stop_bc_connection_timeout”.

API does not cost anything. RTMS starts charging and stop when you use the API to call start RTMS API, and stops when you end the meeting, or when you call the end RTMS API.

[LiveVoice]

thank you very much for your prompt response!

@chunsiong.zoom

@LiveVoice you need to make sure this is disabled at the user settings level as well.

sorry for the stupid question: where do i find this? i thought “Profile → My Account → Account Management → Account Settings → Zoom apps: “Auto-open an app in meetings” is unchecked” is exactly that?

@chunsiong.zoom

API does not cost anything. RTMS starts charging and stop when you use the API to call start RTMS API, and stops when you end the meeting, or when you call the end RTMS API.

thank you! so to make sure i understand correctly: the paid time is between rtms_started and rtms_stopped, not actually the media consumption, yes?

again, thank you very much for your reply!