microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Client Call Controls on Escalated Calls are Inconsistent
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
- User A calls Bot
- Bot Accepts
- Bot adds User B
We have a call now with three participants.
Here's how the call controls look like for the Users
User A:
Hold Button
Transfer Buttons
User B:
Transfer Buttons
Expected behavior
I expected that these buttons would not be there as it is essentially a meeting call now.
If you have a p2p call in teams and then add a third user now Hold or Transfer buttons are present for any User.
However the buttons actually do work... but it's a bit unpredictable from my point of view.
What is the offical story here? Is this a bug? How should these buttons work exactly?
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
No files, tests, or entry points are identified in the issue. First clarify the intended behavior of Hold and Transfer controls for two- and three-party calls, then trace the relevant call-control entry point. Done means the behavior is documented and the controls are consistently handled for all participants.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100