Hi @Jermaine - If the tester account doesn’t have Pro or an RTMS trial, that doesn’t necessarily prevent them from using apps that leverage RTMS. It depends on whether the app is published.
Published apps on the Zoom App Marketplace can be installed and used by anyone, regardless of whether their account has RTMS enabled.
Unpublished apps (maybe this is the case for yours?) can only be used by users within the same account that owns the app. So if a user without an RTMS trial tries to use an unpublished app, they’ll be able to install it but won’t actually be able to use its RTMS features.
TLDR; users without Pro or RTMS trials can use RTMS-powered apps only if those apps are published on the Marketplace.
Do you know how to submit your app to be published on the Marketplace?
I’m still having trouble resolving the issue I mentioned in my previous comment. I followed the guide you provided, but the connection keeps dropping, and it’s difficult to identify the exact cause.
Even in a test environment, I’m unable to pinpoint the root of the problem. Despite following your instructions, I’m currently stuck and waiting for your reply without any progress.
Could you please provide a way to debug this so I can at least identify the cause in the test environment?
You are correct that published apps are widely installable. To tie this back to the Error 1000 issue, while the app installation is separate from licensing, the successful generation of a functional rtms_stream_id—which is critical for preventing the 1000 error during WebSocket initialization—is governed by whether the host user’s account has the active RTMS entitlement provisioned. If the originating user context lacks this entitlement, the API will fail to provision the necessary stream resources, resulting in immediate connection termination regardless of a valid signature.
Hey @Jangwon
I just looked into your account and this issue could have been related to RTMS being disabled in your account.
I went ahead and submitted a request and we updated the RTMS trial
Can you please try again
I have checked the issue you mentioned and tried again.
The meeting.started event is being received normally, but I cannot attempt to connect because the meeting.rtms_started event is not being received via the webhook.
As I understand it, if microphone audio is being picked up after receiving the meeting.started event without any separate processing, the meeting.rtms_started event should arrive immediately. Is there something I am missing?
Hi @Jangwon
The issue you are having might have been caused because your trial expired.
I went ahead and extended it.
Please make sure to fill up this form here to buy the developer pack so you can continue using RTMS
@Jangwon Can you confirm that you are creating the signature that your app will use to securely connect to the RTMS as follows: Working with streams - RTMS - Zoom Developer Docs ? If so, try the signaling and media handshakes in parallel and not sequentially.
If the media handshake waits for signaling to complete, the RTMS gateway may close the socket after 60 seconds of inactivity causing this error.
I have verified the process as you suggested and actually checked the results online, confirming that the signature was generated without any issues.
Additionally, the connection closes immediately with a 1000 rating as soon as the connection is established and sent (rather than waiting 1 minute). I suspect this might be an authentication issue.
I have been requesting assistance with this issue for a long time, but there has been no progress yet.