microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

VideoReceiveStatusChanged not raised on Teams browser version

Open
#577 5 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

Describe the issue
I discovered a strange behaviour of the Microsoft Teams browser version compared to the desktop/andriod version.
I'm developing a bot to receive video from Teams calls. I recently started testing 1:1 calls between a Teams user and the bot.

My testing scenario:

  1. Teams user calls bot
  2. Bot receives incoming call
  3. Bot creates media session with receive only video sockets
  4. Bot answeres call with created media session
  5. Waiting for Videosocket.VideoReceiveStatusChanged to get raised if the Teams user turns camera on

What I found out during testing:
Teams user on Teams browser version calls bot ---> Videosocket.VideoReceiveStatusChanged not raised
Teams user on Teams Desktop/Andriod verion calls bot ---> Videosocket.VideoReceiveStatusChanged raised

Has anyone already encountered the same problem?

Expected behavior
Event Videosocket.VideoReceiveStatusChanged works with all platforms.

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 listed 1:1 call scenario with a Teams browser caller, then compare it with Teams Desktop or Android while monitoring Videosocket.VideoReceiveStatusChanged. The issue is done when the event is raised when the browser caller turns the camera on, matching the expected behavior.

Written by the indexing model from the issue text.

Assessment

Domain
audio-video-rtc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.