# The client server is not receiving any media data

**URL:** <https://devforum.zoom.us/t/the-client-server-is-not-receiving-any-media-data/131464>\
**Category:** Realtime Media Streams\
**Created:** [April 14, 2025, 4:32pm UTC](https://devforum.zoom.us/t/the-client-server-is-not-receiving-any-media-data/131464 "2025-04-14T16:32:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![xgantan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/xgantan/32/66215_2.png) [@xgantan](https://devforum.zoom.us/u/xgantan)\
**Post date:** [April 14, 2025, 4:32pm UTC](https://devforum.zoom.us/t/the-client-server-is-not-receiving-any-media-data/131464/1 "2025-04-14T16:32:20Z")

</div>

I’m testing the media data handling using a Javascript app. So far, the app is receiving the initial signaling handshake and can connect to an all/audio/video server URL from the data handshake response. Then, it can receive the media data handshake response that looks like the following:

```auto
{
  media_params: {
    audio: {
      channel: 1,
      codec: 1,
      content_type: 2,
      data_opt: 1,
      sample_rate: 1,
      send_rate: 20
    },
    video: { codec: 5, content_type: 3, data_opt: 3, fps: 5, resolution: 2 }
  },
  msg_type: 4,
  payload_encrypted: false,
  protocol_version: 1,
  status_code: 0
}

```

However, there is no data being sent to the `ws.on('message', (data) => {...})` handler after the media data handshake response. There is also no media data keep alive requests coming into the media web socket. In the meantime, there are signaling keep alive requests coming into the signaling web socket and they are being handled properly.

Please advise what’s preventing the media data packets from being sent to the media web socket.

Thank you.

---

<div class="post-metadata">

**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\
**Post date:** [April 14, 2025, 8:08pm UTC](https://devforum.zoom.us/t/the-client-server-is-not-receiving-any-media-data/131464/2 "2025-04-14T20:08:35Z")

</div>

@xgantan are you sending the client acknowledgement message?

After receiving the successful media handshake response (msg\_type: 4), you need to send a CLIENT\_READY\_ACK (msg\_type: 7) message to the signaling WebSocket to initiate the media streaming. This message tells the RTMS server that your client is ready to receive media data.

The CLIENT\_READY\_ACK message should look like this:

```auto
{

msg_type: 7, // CLIENT_READY_ACK

rtms_stream_id: "your_stream_id"

}

```

---

<div class="post-metadata">

**Author:** ![xgantan](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/xgantan/32/66215_2.png) [@xgantan](https://devforum.zoom.us/u/xgantan)\
**Post date:** [April 15, 2025, 2:38pm UTC](https://devforum.zoom.us/t/the-client-server-is-not-receiving-any-media-data/131464/3 "2025-04-15T14:38:56Z")

</div>

Got it. Will give it a try.

The dev docs did not mention the step of sending CLIENT\_READY\_ACK, so I didn’t know it’s required.

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [July 21, 2025, 4:26pm UTC](https://devforum.zoom.us/t/the-client-server-is-not-receiving-any-media-data/131464/4 "2025-07-21T16:26:17Z")

</div>

Closed on July 21, 2025, 4:26pm UTC