microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
[ComplianceRecordingBot] Video stream is never subscribed
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
I built the latest sample code and deployed to Azure Cloud Service (classic). When I made a Teams video call from the non-recorded user to the recorded user (per "Test" section of README.md), the bot was correctly triggerred and it received audio sample callbacks. However, the video samples were not delivered, i.e. BotMediaSTream.OnVideoMediaReceived is never called.
I put more logging and found that CallHandler.SubscribeToParticipantVideo() logic never calls this.BotMediaStream.Subscribe(). here
As far as I read the code and put some additional logging, availableSocketIds and msiToSocketIdMapping are created as empty and they are not filled until a video stream is subscribed (and then unsubscribed). In other words, I don't find the locatin where socket ID is set and socket ID is never created.
Is it a logic bug of the sample code? Or, do I miss anything and should I investigate somewhere else why video samples are not delivered?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Test section of README.md and CallHandler.cs at SubscribeToParticipantVideo(), especially the logic around BotMediaStream.Subscribe() and the socket ID mappings. Trace why availableSocketIds and msiToSocketIdMapping remain empty, then verify that video samples reach BotMediaSTream.OnVideoMediaReceived during the documented Teams call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- audio-video-rtc, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100