microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Bot problem: Client Media Error
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Our policy recording bot is removed from a call halfway during a call.
We would like it to remain in the call until the end.
Currently using library version 1.2.0.7270.
Call IDs:
34003580-931f-4d23-9cee-46cfb7745e39 (2024-10-08T09:04:23.9993188Z)
40005180-3432-4177-ad93-a6e9b360f13d (2024-10-08T09:15:38.4361194Z)
6d003880-cdb4-4b38-8d60-69067b71bd2d (2024-10-08T09:15:38.5161160Z)
Logs contain:
"@odata.type": "#microsoft.graph.commsNotification",
"changeType": "Deleted",
"resourceUrl": "/communications/calls/6d003880-cdb4-4b38-8d60-69067b71bd2d",
...
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 410,
"message": "Client Media Error. DiagCode: 410#301005.@",
"subcode": 301005
},
It occured a few times on the same day. I also noticed there is a queue, is that normal, or does it indicate a problem?
Queue found for resource communications/calls/40005180-3432-4177-ad93-a6e9b360f13d, current queue size 7 with id communications/calls/40005180-3432-4177-ad93-a6e9b360f13d
What can we do to avoid the error?
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 repository file, test, or entry point is named. Start by reviewing the Microsoft Graph communications call resource and the supplied Client Media Error (410/301005) logs for the affected call IDs; document whether the queue is expected and define a verified mitigation that keeps the bot connected through call completion.
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
- 25/100