microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Wrong direction when using call queues
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
Direction of call is wrong in case of using call queues
Code Snippet
{ botData: {
callId: 187baca4-2a2f-4441-ac4b-a70a73bc1b76,
mediaHostedRegion: AUEA,
user: {participationMethod: Caller},
otherSideUser: {id: 4:+61xxxxxxxx,participantId: ba3a876a-6403-43e3-92b9-dddfb66dd41f,tenantId: null,participationMethod: Callee}
}}"
Expected behavior
It should be the way around. OtherSideuser is Caller, User is Callee.
Graph SDK (please complete the following information):
- Version 1.2.0.850 with skype bots.media 1.17.0.39 alpha
Call ID
CallID = 187baca4-2a2f-4441-ac4b-a70a73bc1b76
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 call queue handling associated with the reported Call ID and inspect how the code assigns the user and otherSideUser participationMethod values. Compare the payload with the expected caller and callee roles; done means queued calls consistently report OtherSideUser as Caller and User as Callee.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100