# RTMS Interrupts And Disconnects (stop\_reason: 19)

**URL:** <https://devforum.zoom.us/t/rtms-interrupts-and-disconnects-stop-reason-19/144768>\
**Category:** Realtime Media Streams\
**Tags:** events\
**Created:** [July 14, 2026, 3:29pm UTC](https://devforum.zoom.us/t/rtms-interrupts-and-disconnects-stop-reason-19/144768 "2026-07-14T15:29:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alejandro4](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Alejandro4](https://devforum.zoom.us/u/Alejandro4)\
**Post date:** [July 14, 2026, 3:29pm UTC](https://devforum.zoom.us/t/rtms-interrupts-and-disconnects-stop-reason-19/144768/1 "2026-07-14T15:29:40Z")

</div>

#### Summary:

We are testing RTMS to join Zoom meetings, and from time to time (after 10-15min into the meeting) we are getting disconnects from Zoom. Tese are meeting.rtms\_interrupted where our client will successfully reconnect, but after the reconnect we are getting meeting.rtms\_stopped with stop\_reason: 19

Details:  
We did successfully receive a meeting.rtms\_interrupted event in this session and reconnected correctly. However, shortly after reconnecting, we received meeting.rtms\_stopped with stop\_reason: 19. The meeting was still active at this point (it had not ended), so we expected at minimum a documented stop reason explaining why the stream was permanently terminated.

Questions

- What does stop\_reason: 19 indicate?
- What specific platform condition triggers it?
- Is there a recommended way to recover from this condition?
- Should our application automatically attempt to reconnect the RTMS session, and if so, what is the recommended reconnection flow?

#### Here the logs fro two examples:

Example 1 (this was on our Staging env):  
Full Event Timeline  
[14:30:03 UTC] meeting.started  
meeting\_uuid: ZruXO4ZMS1OaTsvay2Af5A==  
host: avaquero@xxx

[~14:30–14:44] Multiple meeting.participant\_joined events received

[14:44:43 UTC] meeting.rtms\_started  
rtms\_stream\_id: 556c676c68ea49a3bb9e601aa9b2612c  
server: wss://zoomsjc144-195-19-85zssgw.sjc.zoom.us:443

[~14:44–14:49] RTMS streaming running normally  
Additional participant events received

[14:49:30 UTC] meeting.rtms\_interrupted ← transient disruption  
Same rtms\_stream\_id and server\_urls

[~14:49] Reconnected successfully, streaming resumed

[14:53:17 UTC] meeting.rtms\_stopped ← unexpected terminal stop  
stop\_reason: 19 (undocumented)  
Meeting was still active at this time

Events:  
{“event”:“meeting.started”,“payload”:{“account\_id”:“p27RYjvyRdORRB7dhHn6oQ”,“object”:{“duration”:60,“start\_time”:“2026-07-08T14:30:03Z”,“timezone”:“America/New\_York”,“topic”:“Google Calendar Meeting (not synced)”,“id”:“99984599214”,“type”:2,“uuid”:“ZruXO4ZMS1OaTsvay2Af5A==”,“host\_id”:“UVucMlfuSq2vHTCn1teMww”,“host\_email”:"avaquero@pindrop.com"}},“event\_ts”:1783521003528}

Multiple meeting.participant\_joined events received:  
{“event”:“meeting.rtms\_started”,“event\_ts”:1783521883942,“payload”:{“account\_id”:“p27RYjvyRdORRB7dhHn6oQ”,“is\_original\_host”:true,“meeting\_id”:99984599214,“meeting\_uuid”:“ZruXO4ZMS1OaTsvay2Af5A==”,“operator\_id”:“UVucMlfuSq2vHTCn1teMww”,“rtms\_stream\_id”:“556c676c68ea49a3bb9e601aa9b2612c”,“server\_urls”:“wss://zoomsjc144-195-19-85zssgw.sjc.zoom.us:443”}}

RTMS streaming running normally:  
{“event”:“meeting.rtms\_interrupted”,“event\_ts”:1783522970497,“payload”:{“meeting\_uuid”:“ZruXO4ZMS1OaTsvay2Af5A==”,“rtms\_stream\_id”:“556c676c68ea49a3bb9e601aa9b2612c”,“server\_urls”:“wss://zoomsjc144-195-19-85zssgw.sjc.zoom.us:443”}}

Reconnected successfully, streaming resumed

{“event”:“meeting.rtms\_stopped”,“payload”:{“meeting\_uuid”:“ZruXO4ZMS1OaTsvay2Af5A==”,“rtms\_stream\_id”:“556c676c68ea49a3bb9e601aa9b2612c”,“stop\_reason”:19},“event\_ts”:1783523197399}

Example 2 (this in our Production env):  
{  
“event”: “meeting.rtms\_stopped”,  
“event\_ts”: 1783521392132,  
“payload”: {  
“meeting\_uuid”: “ZruXO4ZMS1OaTsvay2Af5A==”,  
“rtms\_stream\_id”: “abd6c6f432c04cc8b6a63ec6c88a5d9d”,  
“stop\_reason”: 19  
}  
}

---

<div class="post-metadata">

**Author:** ![amanda-recallai](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amanda-recallai/32/44747_2.png) [@amanda-recallai](https://devforum.zoom.us/u/amanda-recallai)\
**Post date:** [July 14, 2026, 10:42pm UTC](https://devforum.zoom.us/t/rtms-interrupts-and-disconnects-stop-reason-19/144768/2 "2026-07-14T22:42:35Z")

</div>

`stop_reason: 19` maps to `STOP_BC_AWAIT_RECONNECTION_TIMEOUT`. Zoom ended the stream because it was still waiting for reconnection when the allowed window expired, as defined in the [RTMS stop-reason enum](https://developers.zoom.us/docs/rtms/data-types/#rtms_stop_reason). Zoom allows approximately 60 seconds to restore a dropped signaling connection.

On `meeting.rtms_interrupted`, close both signaling and media sockets, then rebuild the complete connection using the webhook’s current `server_urls` and exponential backoff, following Zoom’s [failover and reconnection flow](https://developers.zoom.us/docs/rtms/meetings/failover-reconnection/). A WebSocket reopening isn’t enough. Confirm the new signaling handshake succeeds, reconnect media using the returned media URLs, complete each media handshake, and resume keep-alives. Your timeline suggests Zoom did not recognize the reconnection as fully completed.

Treat `meeting.rtms_stopped` as terminal for that `rtms_stream_id`. Don’t reconnect the stopped stream. If the meeting remains active and your app has the required scope and participant eligibility, send a fresh [RTMS start request](https://developers.zoom.us/docs/rtms/meetings/quickstart-rest-api/#manually-start-rtms) and wait for a new `meeting.rtms_started` event.

Recall.ai is a [Zoom RTMS Preferred Partner](https://docs.recall.ai/docs/meeting-direct-connect-for-zoom-rtms?utm_source=zoom&utm_medium=forum_answer), and you can get further RTMS implementation support through us.

---

<div class="post-metadata">

**Author:** ![Alejandro4](https://avatars.discourse-cdn.com/v4/letter/a/bbce88/32.png) [@Alejandro4](https://devforum.zoom.us/u/Alejandro4)\
**Post date:** [July 16, 2026, 10:19pm UTC](https://devforum.zoom.us/t/rtms-interrupts-and-disconnects-stop-reason-19/144768/3 "2026-07-16T22:19:56Z")

</div>

Thanks Amanda. We’ll check this out.
