microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Video injected issue in MS Teams client

Open
#402 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Hi guys, how is everything?

We are currently developing a hosted media application to inject media content into a MS Teams meeting but, while doing some tests injecting media content (audio and video) into the meeting, we noticed that the audio is always played but, sometimes the video is rendered in the corresponding place for the participant (bot) while other times it is not rendered. However, in the last case when the MS Teams client is minimized, the video can be seen in the meeting details miniature rendered in the bottom right corner.

As mentioned above, this behavior is random, and we found that if we pin a participant’s video in the meeting and unpin it, the video injected from the bot starts being rendered in the corresponding spot.

Based on the workarounds that we just mentioned, we assume that the audio and video are being injected correctly and is the MS Teams client that is having problems.

Is there is something under the hood that we do not know that can be affecting the bot? or it is a problem (bug) in the MS Teams client?

Thank in advance.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the hosted media injection in an MS Teams meeting and compare normal, minimized, and pin/unpin states. The issue names no repository files, tests, or entry points, so first determine whether the behavior is reproducible in the sample or isolated to the MS Teams client. Done would require identifying a confirmed cause and a project-owned change, if one exists.

Written by the indexing model from the issue text.

Assessment

Domain
audio-video-rtc
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.