RTMS connects to the meeting then immediately interrupted with reason 43

AhmetA · January 9, 2026, 12:39pm

Hi,
I was be able to test the RTMS previous months, perfectly working and able to receive the audio stream from zoom. I’m still successfully connected to the zoom rtms but it instantly interrupted. Got reason 43.

I have done a bit research and find out these can be the reasons;

Meeting has E2EE enabled (disable it)
App not authorized for RTMS meeting content
Account/user doesn’t have RTMS enabled
Wrong credentials (client ID/secret mismatch)

Could you help me on this regard, maybe my RTMS access deprecated, and what can cause this instant stopping rtms problem ?

Some more context:

webhook  | 2026-01-09T12:33:35.059Z | INFO  | Creating standard HTTP webhook server
webhook  | 2026-01-09T12:33:35.065Z | INFO  | Listening for webhook events at http://localhost:8080/
webhook  | 2026-01-09T12:33:45.835Z | DEBUG | Received webhook request: /
webhook  | 2026-01-09T12:33:45.836Z | INFO  | Received event: meeting.rtms_started

🎯 RTMS Meeting Started!
Stream ID: c7f2a13f315c4756961e63e906c76a3a
Meeting UUID: IjdZzxPhRHeQVQQ61Ng3wA==

👂 Listening for audio…

webhook  | event=meeting.rtms_started | payloadKeys=meeting_uuid,operator_id,rtms_stream_id,server_urls
{
“meeting_uuid”: “IjdZzxPhRHeQVQQ61Ng3wA==”,
“operator_id”: “RlQPsPtPSWOQYOqM5e7tyg”,
“rtms_stream_id”: “c7f2a13f315c4756961e63e906c76a3a”,
“server_urls”: “wss://zoomsjc144-195-19-81zssgw.sjc.zoom.us:443”
}
client   | 2026-01-09T12:33:45.840Z | DEBUG | Setting audio parameters: {“contentType”:2,“sampleRate”:1,“channel”:1,“dataOpt”:1,“duration”:20,“frameSize”:640}
client   | 2026-01-09T12:33:45.840Z | DEBUG | audio parameters set successfully
client   | 2026-01-09T12:33:45.841Z | DEBUG | Setting video parameters: {“contentType”:3,“codec”:7,“resolution”:1,“dataOpt”:3,“fps”:30}
client   | 2026-01-09T12:33:45.841Z | DEBUG | video parameters set successfully
client   | 2026-01-09T12:33:45.841Z | DEBUG | Setting deskshare parameters: {“contentType”:3,“codec”:7,“resolution”:1,“dataOpt”:3,“fps”:30}
client   | 2026-01-09T12:33:45.841Z | DEBUG | deskshare parameters set successfully
rtms     | 2026-01-09T12:33:45.842Z | DEBUG | Found system CA certificate: /etc/ssl/cert.pem
rtms     | 2026-01-09T12:33:45.842Z | INFO  | Initializing RTMS SDK with CA certificate: /etc/ssl/cert.pem
rtms     | 2026-01-09T12:33:45.894Z | INFO  | RTMS SDK initialized successfully
client   | 2026-01-09T12:33:45.895Z | INFO  | Joining meeting: IjdZzxPhRHeQVQQ61Ng3wA==
rtms     | 2026-01-09T12:33:45.896Z | DEBUG | Generating signature for client: OXtsVYoWSUqmAXfkF00OqA, uuid: IjdZzxPhRHeQVQQ61Ng3wA==, streamId: c7f2a13f315c4756961e63e906c76a3a
client   | 2026-01-09T12:33:45.900Z | INFO  | Successfully joined meeting: IjdZzxPhRHeQVQQ61Ng3wA==
client   | 2026-01-09T12:33:45.901Z | DEBUG | Starting polling with interval: 10ms
client   | Join confirm reason: 43
client   | ⚠️  Join FAILED with reason 43. Common causes:
client   |    - Meeting has E2EE enabled (disable it)
client   |    - App not authorized for RTMS meeting content
client   |    - Account/user doesn’t have RTMS enabled
client   |    - Wrong credentials (client ID/secret mismatch)
webhook  | 2026-01-09T12:33:46.464Z | DEBUG | Received webhook request: /
webhook  | 2026-01-09T12:33:46.465Z | INFO  | Received event: meeting.rtms_interrupted

⚠️  RTMS stream interrupted

webhook  | event=meeting.rtms_interrupted | payloadKeys=meeting_uuid,rtms_stream_id
{
“meeting_uuid”: “IjdZzxPhRHeQVQQ61Ng3wA==”,
“rtms_stream_id”: “c7f2a13f315c4756961e63e906c76a3a”
}
client   | 2026-01-09T12:33:47.975Z | INFO  | Leaving meeting: IjdZzxPhRHeQVQQ61Ng3wA==
client   | 2026-01-09T12:33:47.976Z | DEBUG | Stopping polling
client   | 2026-01-09T12:33:47.976Z | INFO  | Successfully left meeting

Thank you,
Ahmet.

Abdullah4 · January 9, 2026, 1:06pm

That instant interruption and Reason 43 strongly suggest an authorization failure specifically for accessing the media stream, rather than a credential issue, since your client successfully initiated the join process. I think the absolute first step is confirming that End-to-End Encryption (E2EE) is still disabled for that particular meeting, as this is the most common cause for immediate failure 43. If E2EE is confirmed off, I suggest checking if the Zoom account associated with the API key still has active RTMS licensing, as deprecated access often presents this exact denial of service.

Hope this helps!

AhmetA · January 9, 2026, 1:21pm

Thank you for your reply. I have check the E2EE again, and its still disabled.

I guess I lost my RTMS access, any help how can I authenticate again ?
Thanks

amanda-recallai · January 9, 2026, 10:22pm

Hi @Ahmet, since you receive meeting.rtms_started and then immediately hit Join confirm reason: 43 followed by meeting.rtms_interrupted, this usually points to a server-side rejection (permissions/policy) rather than a connectivity problem

First thing to confirm is the meeting is not using E2EE, because RTMS meeting content access will fail fast if the meeting is end-to-end encrypted. I see you’ve already confirmed this wasn’t the case but wanted to call it out to cover all bases

Next, have a Zoom admin re-check that RTMS and “apps access real-time meeting content” are still enabled for the account/group/user on the host account and that your app is allowed. You can find this under settings > zoom apps > meeting > " Share realtime meeting content with apps" in the Zoom dashboard

Also double-check you’re generating the join signature with the correct client ID/secret for the same app that is authorized, and that you’re passing the exact meeting_uuid and rtms_stream_id from the webhook without transforming them

AhmetA · January 10, 2026, 9:00pm

Thank you for your reply. Yes, E2EE is disabled, and ‘Share realtime meeting content with apps’ is enabled as you can see here:

The app is under auto start also. I have checked the client ID/secret, they are correct, as well as sending the meeting_uuid and rtms_stream_id. I have even printed them all to double check and they seem correct to me.

Any other ideas to solve the issue ?

(base) ahmetkaragoz@Eng-Int rtms-quickstart-js % node --env-file=.env index-test-audio-only.js
webhook  | 2026-01-10T20:51:57.649Z | INFO  | Creating standard HTTP webhook server
webhook  | 2026-01-10T20:51:57.658Z | INFO  | Listening for webhook events at http://localhost:8080/
webhook  | 2026-01-10T20:52:08.391Z | DEBUG | Received webhook request: /
webhook  | 2026-01-10T20:52:08.392Z | INFO  | Received event: meeting.rtms_started

🎯 RTMS Meeting Started!
Stream ID: 45f92c38756a47a18af97a8fef2bba40
Meeting UUID: eM6HDx44QJeXQDZOyzgLtw==

👂 Listening for audio…

webhook  | event=meeting.rtms_started | payloadKeys=meeting_uuid,operator_id,rtms_stream_id,server_urls
{
“meeting_uuid”: “eM6HDx44QJeXQDZOyzgLtw==”,
“operator_id”: “RlQPsPtPSWOQYOqM5e7tyg”,
“rtms_stream_id”: “45f92c38756a47a18af97a8fef2bba40”,
“server_urls”: “wss://zoomsjc144-195-46-185zssgw.sjc.zoom.us:443”
}
client   | 2026-01-10T20:52:08.396Z | DEBUG | Setting audio parameters: {“contentType”:2,“sampleRate”:1,“channel”:1,“dataOpt”:1,“duration”:20,“frameSize”:640}
client   | 2026-01-10T20:52:08.396Z | DEBUG | audio parameters set successfully
client   | 2026-01-10T20:52:08.396Z | DEBUG | Setting video parameters: {“contentType”:3,“codec”:7,“resolution”:1,“dataOpt”:3,“fps”:30}
client   | 2026-01-10T20:52:08.396Z | DEBUG | video parameters set successfully
client   | 2026-01-10T20:52:08.396Z | DEBUG | Setting deskshare parameters: {“contentType”:3,“codec”:7,“resolution”:1,“dataOpt”:3,“fps”:30}
client   | 2026-01-10T20:52:08.396Z | DEBUG | deskshare parameters set successfully
🔐 Environment check:
ZM_RTMS_CLIENT: OXtsVYoWSUqmAXfkF00OqA
ZM_RTMS_SECRET: ***O3pR
meeting_uuid: “eM6HDx44QJeXQDZOyzgLtw==”
rtms_stream_id: “45f92c38756a47a18af97a8fef2bba40”
server_urls: “wss://zoomsjc144-195-46-185zssgw.sjc.zoom.us:443”
rtms     | 2026-01-10T20:52:08.397Z | DEBUG | Found system CA certificate: /etc/ssl/cert.pem
rtms     | 2026-01-10T20:52:08.397Z | INFO  | Initializing RTMS SDK with CA certificate: /etc/ssl/cert.pem
rtms     | 2026-01-10T20:52:08.423Z | INFO  | RTMS SDK initialized successfully
client   | 2026-01-10T20:52:08.423Z | INFO  | Joining meeting: eM6HDx44QJeXQDZOyzgLtw==
rtms     | 2026-01-10T20:52:08.423Z | DEBUG | Generating signature for client: OXtsVYoWSUqmAXfkF00OqA, uuid: eM6HDx44QJeXQDZOyzgLtw==, streamId: 45f92c38756a47a18af97a8fef2bba40
client   | 2026-01-10T20:52:08.428Z | INFO  | Successfully joined meeting: eM6HDx44QJeXQDZOyzgLtw==
client   | 2026-01-10T20:52:08.428Z | DEBUG | Starting polling with interval: 10ms
✅ Join request initiated successfully
client   | Join confirm reason: 43
client   | ⚠️  Join FAILED with reason 43. Common causes:
client   |    - Meeting has E2EE enabled (disable it)
client   |    - App not authorized for RTMS meeting content
client   |    - Account/user doesn’t have RTMS enabled
client   |    - Wrong credentials (client ID/secret mismatch)
webhook  | 2026-01-10T20:52:09.102Z | DEBUG | Received webhook request: /
webhook  | 2026-01-10T20:52:09.103Z | INFO  | Received event: meeting.rtms_interrupted

⚠️  RTMS stream interrupted

webhook  | event=meeting.rtms_interrupted | payloadKeys=meeting_uuid,rtms_stream_id
{
“meeting_uuid”: “eM6HDx44QJeXQDZOyzgLtw==”,
“rtms_stream_id”: “45f92c38756a47a18af97a8fef2bba40”
}
client   | 2026-01-10T20:52:10.611Z | INFO  | Leaving meeting: eM6HDx44QJeXQDZOyzgLtw==
client   | 2026-01-10T20:52:10.612Z | DEBUG | Stopping polling
client   | 2026-01-10T20:52:10.612Z | INFO  | Successfully left meeting

Topic		Replies	Views
Enable RTMS for organization Realtime Media Streams	45	768	December 22, 2025
Enable RTMS (startRTMS) for App ID: hBgpAVvSk6w2_H9ytSx_w Zoom Apps	1	20	December 11, 2025
My rtms client connects successfully but then immediately disconnects with stop reason 18 Realtime Media Streams	6	259	September 2, 2025
Unable to start the RTMS Realtime Media Streams	9	470	July 21, 2025
Broken RTMS Websocket Realtime Media Streams	12	136	December 9, 2025

RTMS connects to the meeting then immediately interrupted with reason 43

Related topics