microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Migration to .net 8 : Group call mode with participantcapacity does not support
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
We have policy recording bot handles Group call / meeting mode with participantcapacity ( ex 100) . after migration policy recoding bot solution to .net 8, we receives Call.ParticipantJoiningHandler event when multipe users join to call / meeting then we send back "AcceptJoinResponse()" but it keep re-sending Call.ParticipantJoiningHandler event mutiple times.
1-1 call or meeting works fine but issue occurs when 3 or subsequent user attempt to join to the call then Unable to join and the user will be dropped from the call after receiving Call.ParticipantJoiningHandler event retries.
Expected behavior
Subsequent user is able to join to the exising call.
Graph SDK (please complete the following information):
- Microsoft.Skype.Bots.Media ( 1.27.0.2-alpha)
- Microsoft.Graph.Communication.Calls.Media ( 1.2.0.10563 )
- Microsoft.Graph.Communications.Call ( 1.2.0.10563 )
- Microsoft.Graph.Communications.Client ( 1.2.0.10563 )
- Microsoft.Graph.Communications.Common ( 1.2.0.10563 )
- Microsoft.Graph.Communications.Core ( 1.2.0.10563 )
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 by reproducing a group call with participantcapacity after the .NET 8 migration, focusing on repeated Call.ParticipantJoiningHandler events and the AcceptJoinResponse response. Done means subsequent participants can join the existing call without retries or being dropped.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, audio-video-rtc, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100