Unable to Render Video – Zoom Error Code 206 (active-media-failed)

Video SDK Web
1

Description
Sometimes, we are unable to render video using video-player, and Zoom throws the following error:

Error eventType: active-media-failed, data: {message: Oops! Something went wrong. Please close all browsers and rejoin the meeting., type: video, code: 206}

According to Zoom’s documentation, this error means: “Failed to get video data from the stream.”

Could you help us investigate why this is happening?
Also, if it’s not fully preventable, could you suggest how we might handle this error more gracefully, or reduce how frequently it occurs?

This is my sessionId: G7hN3patQvakN5hjB1Lumw==

Thank you in advance!

Which Web Video SDK version?
2.1.0

Video SDK Code Snippets

Start video:

      let videoOptions = {
        cameraId: cameraId,
         originalRatio: window.isMobile
      };

      if (mediaStream.isSupportVirtualBackground() && virtualBackground) {
        videoOptions.virtualBackground = { imageUrl: virtualBackground };
      }
      await mediaStream.startVideo(videoOptions);

Render video:

        const videoPlayer = await state.mediaStream.attachVideo(userId, quality);
        ...

WebRTC is not enabled for video in our implementation.

To Reproduce(If applicable)

  1. User 1 joins the meeting with camera and microphone enabled.
  2. User 2 then joins the same meeting on the same device, also with camera and microphone enabled.

→ At this point, both video views are completely black and the error mentioned above is thrown.

However, when User 3 joins the meeting (also on the same device), video rendering succeeds for all three users.

Device (please complete the following information):

  • Device: Window
  • Browser: Chrome
  • Browser Version: 137.0.7151.120 (Official Build) (64-bit)
2

Hey @lmtruong1512

Thanks for your feedback.

G7hN3patQvakN5hjB1Lumw==

After analyzing the logs, we found that the video was muted by the system due to interruption from another application, preventing the SDK from capturing any frames.

This case has been improved in the latest Video SDK Web (2.2.0), which introduces a new exception type — ActiveMediaFailedCode.VideoStreamMuted (207) — to help developers handle this scenario.

Thanks
Vic

3

@vic.yang Thank you for your response,
When this exception occurs, what handling approach do you recommend? We tried turning the camera off and on again, but the issue persists.

4

Hi @lmtruong1512

We tried turning the camera off and on again, but the issue persists.

Yes. Recapturing video will resolve the issue.

G7hN3patQvakN5hjB1Lumw==

For User 16781312 who encountered the issue, we didn’t find any stopVideo and startVideo call sequence after the issue occurred. Could you share a new session ID with us?

Thanks
Vic

5

Hi @vic.yang,

Yes. Recapturing video will resolve the issue.

We attempted to stop and start the video, but the issue persisted until another user joined the meeting—at which point the problem disappeared.

We’ll try to reproduce the issue again and share a new session ID with you.

Thank you for your time and continued support!

6

@vic.yang This is another session where we encountered the issue. Could you please help us check it?

Session ID:

pl633Rb2TwCv9W3iMCzk/A==
7

Hi @lmtruong1512

pl633Rb2TwCv9W3iMCzk/A==

The User 33555456 who encountered the issue, there was no stopVideo and startVideo call sequence after the issue occurred.

Thanks
Vic

8

@vic.yang

Yes. Recapturing video will resolve the issue.

We noticed that the documentation suggests the following action:

Screenshot 2025-07-10 at 13.59.08
Screenshot 2025-07-10 at 13.59.08723×123 12.7 KB

So, if the user doesn’t interact with the page, and we detect this specific error type ‘code - 207’, would programmatically stopping and restarting the camera resolve the issue?

Thank you for your time and support!

9

Hi @lmtruong1512

if the user doesn’t interact with the page, and we detect this specific error type ‘code - 207’, would programmatically stopping and restarting the camera resolve the issue?

This cannot be guaranteed. It’s better to add a prompt suggesting that the user interact with the page before recapturing the video.

Thanks
Vic

1 Like
10

Hi @vic.yang,
Could you help me check this session ID: 2IJoQ1xFTc2wy75X3b/icQ==?

We just encountered this issue. After the error occurred, the user tried clicking “Stop” and then “Start” camera again, but the issue still persisted.
Could you confirm whether the stop/start video actions were successfully triggered to ZoomSDK?
If they were, do you have any insight into why the issue wasn’t resolved?

Thanks

11

Hi @lmtruong1512

2IJoQ1xFTc2wy75X3b/icQ==

The session is still using Video SDK Web 2.1.0. The code - 207 was introduced in Video SDK Web 2.2.0.

Thanks
Vic

12

Hi @vic.yang

The session is still using Video SDK Web 2.1.0. The code - 207 was introduced in Video SDK Web 2.2.0.

Our current understanding is that if this is the same underlying issue, it would be reported as code -207 in version 2.2.0, whereas in our current version (2.1.0), it appears as code -206.

Given that, we’d like to confirm: if the user interacts with the page and we manually trigger a stop/start camera action, should that still resolve the issue—even in 2.1.0?

Is that understanding correct?

Thank you for your time and support!

13

Hi @lmtruong1512

Given that, we’d like to confirm: if the user interacts with the page and we manually trigger a stop/start camera action, should that still resolve the issue—even in 2.1.0?

Is that understanding correct?

Yes.

Thanks
Vic

14

Hi @vic.yang Thank you for your confirmation.

We plan to handle the error as suggested, but we’re a confused about the behavior in this session: 2IJoQ1xFTc2wy75X3b/icQ==
QeysI83xQoO78zzmd56Prw

The user manually tried to stop and start the camera, but the issue persisted and the video could not be rendered.

We’d like to clarify:
Is this a different bug unrelated to the one discussed, or is it the same issue—but the stop/start video action failed to trigger correctly on our client side, so ZoomSDK didn’t receive it and the problem wasn’t resolved?

Thank you!

15

Hi @lmtruong1512

2IJoQ1xFTc2wy75X3b/icQ==

The video stream of User ID 16778240 was muted. This is the same type of issue as code 207.

QeysI83xQoO78zzmd56Prw==

This is a separate issue — User ID 16778240 failed to initialize video successfully. We’ll provide updates on the investigation in another thread.

Thanks
Vic

1 Like
16

@vic.yang

The video stream of User ID 16778240 was muted. This is the same type of issue as code 207.

The user attempted to stop and start the camera, but the video still didn’t work. This seems to conflict with the earlier confirmation:

if the user interacts with the page and we manually trigger a stop/start camera action, should that still resolve the issue—even in 2.1.0?
Yes

Similarly, for session ID iWirGCz2StK/yr43EM7WyQ== , the user manually stopped and started the camera multiple times, but the video still couldn’t be rendered.

Could you please help us double-check this cases?

17

Hi @lmtruong1512

2IJoQ1xFTc2wy75X3b/icQ==

We did see logs showing that stopVideo was called followed by startVideo, but the logs also indicate that the video stream remained muted.

You mentioned in this thread that multiple users might be using the same device—this could be the reason why the browser-captured video stream behaves abnormally.

Currently, we don’t have a good solution for this case, as the original stream is obtained directly from the browser.

Thanks
Vic

1 Like
18

Hi @vic.yang,
Thank you for the information!