microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Bot status changes from Establishing to Terminated - Unable to Add Bot in the meeting
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hello, I'm trying to get my bot into a meeting.
I get all status working fine, when it comes to actually join, it fails.
The Bot Call status goes from state "Establishing" to "Terminated" which I debuged from the code itself.
`"message": "Server Internal Error. DiagCode: 500#3002.@",`
There is no documentation or help on this issue. How can I find and fix the source of the issue?
I have been working on the PSI bot for quite sometime and this is the 3rd time this issue has occured out of no where. 2 days back, everything was working fine and suddenly the bot fails to join the meeting and I get this error everytime.
LegID
5e1f5600-e6c7-4abb-be5b-b01b857e05ff
CallID
5e1f5600-e6c7-4abb-be5b-b01b857e05ff
Logs
{
"value": [
{
"changeType": "Deleted",
"resourceUrl": "/communications/calls/5e1f5600-e6c7-4abb-be5b-b01b857e05ff",
"resource": "/app/calls/5e1f5600-e6c7-4abb-be5b-b01b857e05ff",
"resourceData": {
"@odata.type": "#microsoft.graph.call",
"callChainId": "3f8201c6-dca4-4934-bba2-ed0028dbb89c",
"chatInfo": {
"@odata.type": "#microsoft.graph.chatInfo",
"messageId": "0",
"threadId": "19:meeting_MDUzNGE4MDQtODU3ZC00Y2E1LTljYzktMzAxZGJiOWUyM@thread.v2"
},
"meetingInfo": {
"@odata.type": "#microsoft.graph.organizerMeetingInfo",
"organizer": {
"@odata.type": "#microsoft.graph.identitySet",
"user": {
"@odata.type": "#microsoft.graph.identity",
"tenantId": "9693631f-4521-4175-as8a-fb1919b76e48",
"id": "4e9d92a8-ce58-4d03-949b-a3b0ef768dee"
}
}
},
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 500,
"message": "Server Internal Error. DiagCode: 500#3002.@",
"subcode": 3002
},
"state": 8,
"tenantId": "9693631f-4521-4175-as8a-fb1919b76e48"
}
}
]
}
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 reviewing the bot's meeting-join flow and the logs for the Establishing-to-Terminated transition, especially result code 500 and subcode 3002. Use the provided LegID, CallID, tenant, and meeting identifiers to correlate the failure. Done means identifying a reproducible cause and documenting or applying a verified fix, but the issue names no repository files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100