#  RTMS chat stream connects successfully (state ACTIVE) but no MEDIA\_DATA\_CHAT (msg\_type 18) frames ever arrive

**URL:** <https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217>\
**Category:** Realtime Media Streams\
**Created:** [June 15, 2026, 7:16am UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217 "2026-06-15T07:16:47Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Federico2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/federico2/32/75033_2.png) [@Federico2](https://devforum.zoom.us/u/Federico2)\
**Post date:** [June 15, 2026, 7:16am UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/1 "2026-06-15T07:16:47Z")

</div>

Hi, I’m building a local integration that consumes **in-meeting chat via RTMS** (media\_type 16). The whole pipeline connects successfully, but **no chat data frames (msg\_type 18) are ever delivered**, regardless of who sends the message (host, co-host from another device, or participant).

**Setup:**

- Pro account with **Developer Pack active** (pay-as-you-go)
- General App (user-managed) with scope `meeting:read:meeting_chat`, RTMS events subscribed, app installed/authorized
- RTMS started via `PATCH /v2/live_meetings/{meetingId}/rtms_app/status` with `{"action":"start","settings":{"client_id":"<general app id>"}}` → **HTTP 204** ✓
- `meeting.rtms_started` received via WebSocket event subscription ✓
- Signaling handshake (msg\_type 1, media\_type 16) → status\_code 0, media server URL returned under `media_server.server_urls.chat` ✓
- Media handshake (msg\_type 3, media\_type 16, payload\_encryption false, media\_params `{chat:{content_type:5}}`) → msg\_type 4, status\_code 0, response echoes `media_params.chat.content_type: 5` ✓
- CLIENT\_READY\_ACK (msg\_type 7) sent on signaling ✓
- STREAM\_STATE\_UPDATE state **1 (ACTIVE)**, SESSION\_STATE\_UPDATE state **2 (STARTED)** ✓
- In-meeting panel “Apps accessing meeting content” shows the app with **“Access in progress — Access: Chat”** ✓
- KEEP\_ALIVE handled on both sockets ✓

**Problem:** after this, the media socket stays silent forever: no msg\_type 18, no msg\_type 27, nothing — while chat messages are being sent in the meeting (tested host-only, host+phone participant, co-host). Meeting runs 5+ minutes.

Also tried subscribing the webhook/WS event **“In-meeting chat message received”** on a Server-to-Server app subscription: the event never fires either (other meeting events like meeting.started/ended arrive fine on the same connection).

**Questions:**

1. Is there an account-level setting (e.g., advanced chat encryption, continuous meeting chat / Team Chat-based meeting chat) that blocks RTMS chat delivery?
2. Does RTMS chat require any additional enablement beyond the Developer Pack?
3. Is `meeting.chat_message_received` deliverable over WebSocket subscriptions, and does it require extra scopes?

Account ID available via DM if needed. Thanks!

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [June 15, 2026, 7:34am UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/2 "2026-06-15T07:34:23Z")

</div>

@Federico2 chat message for RTMS is coming soon

---

<div class="post-metadata">

**Author:** ![Federico2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/federico2/32/75033_2.png) [@Federico2](https://devforum.zoom.us/u/Federico2)\
**Post date:** [June 15, 2026, 10:14am UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/3 "2026-06-15T10:14:37Z")

</div>

super thanks for your answer…I have an issue…

I have a headless Windows Meeting SDK bot (custom UI, `ENABLE_CUSTOMIZED_UI_FLAG`) that joins my own meetings to manage spotlight / participants. It **was working** until about **June 13, 2026**. Since around June 14–15 it **authenticates fine but never enters the meeting** — it stays in `MEETING_STATUS_CONNECTING` indefinitely. No code changed on my side (same .exe).

**Setup**

- Windows Meeting SDK **7.0.5.39292** (latest Windows build)
- C++ bot; `InitSDK` with `ENABLE_CUSTOMIZED_UI_FLAG`, `enableLogByDefault = true`, `strWebDomain = "https://zoom.us"`
- App: General App with **Meeting SDK** enabled, **Development** credentials, on **my own Pro account**
- Joining **my own Personal Meeting Room** (meeting on the **same account** as the app)
- Anonymous join: `SDK_UT_WITHOUT_LOGIN` + `JoinParam4WithoutLogin` (meetingNumber, userName, psw, isVideoOff=true, isAudioOff=true, **no** userZAK, **no** onBehalfToken)
- JWT signed with SDK Client ID/Secret, role=0, iat/exp/tokenExp per spec

**What happens**

- `onAuthenticationReturn` → `AUTHRET_SUCCESS` ✓
- `Join(JoinParam)` → returns `SDKERR_SUCCESS` ✓
- `onMeetingStatusChanged` → `MEETING_STATUS_CONNECTING` (1)
- …then **nothing**. Never reaches `MEETING_STATUS_INMEETING` (3), never `MEETING_STATUS_FAILED` (6), no `iResult`. Stays at CONNECTING for 2+ minutes and indefinitely. The bot never appears in the participant list.

**Meeting security**

- Passcode-protected (passcode `0000`). Tried both the plain passcode and the `pwd=` token from the join URL → **same** CONNECTING hang, never a password error / FAILED.
- Waiting Room: **OFF**
- “Only authenticated users can join”: **OFF**

**Already ruled out**

- Firewall/AV: Norton Smart Firewall + Intrusion Prevention disabled → no change; nothing in Norton’s blocked-connections log.
- Network: wired Ethernet, no VPN, no system proxy. The normal Zoom desktop client (6.7.8) connects fine to the **same meeting on the same PC**.
- A clean PC reboot did not help.

**One clue:** on **June 13** the SDK wrote **plaintext** logs (`jump_maestro.exe_N.log` in `%APPDATA%\ZoomSDK\logs`). Since June 14–15 it only writes **encrypted** logs (`zoom_memlog_*.log.zenc`). Looks like the SDK runtime updated itself in between.

**Questions**

1. What can cause a Meeting SDK join to stay at `MEETING_STATUS_CONNECTING` **forever** , with no timeout and no `MEETING_STATUS_FAILED`?
2. Was there a recent (June 2026) change affecting **same-account anonymous joins** on the Windows SDK, or a new join-flow callback the app must implement that, if unhandled, leaves the join stuck at CONNECTING?
3. How can I get **plaintext** SDK logs again (or submit the encrypted `.zenc` logs) so the exact connection failure can be diagnosed?
4. For an anonymous join to the **app owner’s own** meeting, is it now required to enable **“Request Anonymous Join Exception”** and/or the **“programmatic join use case”** toggle?

Account ID and encrypted SDK logs available via DM. Thanks!

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [June 16, 2026, 3:47am UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/4 "2026-06-16T03:47:11Z")

</div>

@Federico2 I’ll PM you for the logs

---

<div class="post-metadata">

**Author:** ![Amit11](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amit11/32/50555_2.png) [@Amit11](https://devforum.zoom.us/u/Amit11)\
**Post date:** [July 15, 2026, 12:59pm UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/5 "2026-07-15T12:59:40Z")

</div>

@chunsiong.zoom I am also interested in the chat feature. Any tentative date for feature to be available for testing ?  
Apart from RTMS, is there any other option currently available to capture the in-meeting chat messages ?

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [July 15, 2026, 2:09pm UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/6 "2026-07-15T14:09:01Z")

</div>

@Amit11 chat should be out now

> **[RTMS June release - Zoom Developer Changelog](https://developers.zoom.us/changelog/rtms/july-04-2026/)**
>
> Add REST API support for starting RTMS for meeting participants, add chat message media data support with 5 new event types for meetings and webinars, updates to protocol definitions including new and updated enums, improve PSTN user identification...

---

<div class="post-metadata">

**Author:** ![Amit11](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amit11/32/50555_2.png) [@Amit11](https://devforum.zoom.us/u/Amit11)\
**Post date:** [July 15, 2026, 3:04pm UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/7 "2026-07-15T15:04:21Z")

</div>

Thanks @chunsiong.zoom  
I could not find the MEDIA\_DATA\_CHAT payload documentation. Could you please share the reference doc for the MEDIA\_DATA\_CHAT payload ?

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [July 16, 2026, 3:13am UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/8 "2026-07-16T03:13:52Z")

</div>

@Amit11 refer to this [Data type definitions - RTMS - Zoom Developer Docs](https://developers.zoom.us/docs/rtms/data-types)

and this [Event reference - RTMS - Zoom Developer Docs](https://developers.zoom.us/docs/rtms/event-reference/#chat-data)

---

<div class="post-metadata">

**Author:** ![Amit11](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amit11/32/50555_2.png) [@Amit11](https://devforum.zoom.us/u/Amit11)\
**Post date:** [July 16, 2026, 2:51pm UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/9 "2026-07-16T14:51:41Z")

</div>

Thanks @chunsiong.zoom !  
It helps.

---

<div class="post-metadata">

**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\
**Post date:** [July 20, 2026, 12:27pm UTC](https://devforum.zoom.us/t/rtms-chat-stream-connects-successfully-state-active-but-no-media-data-chat-msg-type-18-frames-ever-arrive/144217/10 "2026-07-20T12:27:58Z")

</div>

Closed on July 20, 2026, 12:27pm UTC


