microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
"Callee could not be reached"
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hello Community. I am building an Microsoft teams recording bot (console application). I am following Policy Recording Bot sample as well se teams recording bot sample code. I am getting the 202 Accepted response on incoming call request but my bot is not joining the call ( Connection is not getting established only receiving incoming request). Could anyone can help me in this problem.
Debugging the code I found that the error while answering the call {"@odata.type":"#microsoft.graph.resultInfo","code":408,"subcode":8544,"message":"Callee could not be reached."}
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 comparing the Policy Recording Bot sample with the Teams recording bot sample and reproduce the incoming-call flow. Inspect the answer response and the reported 408/8544 result to determine why the callee is unreachable; done would mean the bot successfully establishes the call connection.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100