microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Do not receive notification when invitee rejects an invite to a call
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
When inviting a user to an already established call, I do not receive respected event when he/she rejects the call, despite that I see it in logs.
Code Snippet
_endpoint.TeamsClient.OnNotificationProcessed += (r) => {
switch (r.Notification.ChangeType) {
case ChangeType.Deleted:
var extracted = r.Notification.ExtractResouceData();
break;
default:
break;
}
};
var operation = await (_botCall).Participants.InviteAsync(
new List<InvitationParticipantInfo>() {
new InvitationParticipantInfo() {
Identity = usertocall,
}
},
cancellationToken
);
Expected behavior
Should get the following data when I use "extracted " from above code:
GraphLogger::PalBabakBot - {
"value": [
{
"changeType": "Deleted",
"resourceUrl": "/communications/calls/09005280-1a9b-4920-b36a-41120f8d11c9/operations/496ecbca-26fa-45c1-937e-08fd1aed1e4f",
"resource": "/app/calls/09005280-1a9b-4920-b36a-41120f8d11c9/operations/496ecbca-26fa-45c1-937e-08fd1aed1e4f",
"resourceData": {
"@odata.type": "#microsoft.graph.inviteParticipantsOperation",
"participants": [
{
"@odata.type": "#microsoft.graph.invitationParticipantInfo",
"identity": {
"@odata.type": "#microsoft.graph.identitySet",
"user": {
"@odata.type": "#microsoft.graph.identity",
"tenantId": "293c78bf-b98b-4505-a3aa-2f330db99522",
"displayName": "sip:core_agent1@wspa365.dev",
"id": "96bb95f4-7a20-446a-bea5-04541b2001a7"
}
},
"participantId": "58935b36-232d-44fe-b545-e0250249e339"
}
],
"clientContext": "c2056953-fda3-4d35-8083-1ba6a43b251f",
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 603,
"message": "addParticipants failed for participant 8:orgid:96bb95f4-7a20-446a-bea5-04541b2001a7. Underlying reason: Decline. DiagCode: 603#0.@",
"subcode": 0
},
"status": 3,
"id": "496ecbca-26fa-45c1-937e-08fd1aed1e4f"
}
}
]
}
Graph SDK:
Azure.Identity:1.12.0
Microsoft.Graph:5.38.0
Microsoft.Graph.Communications.Calls:1.2.0.10563
Microsoft.Graph.Communications.Client:1.2.0.10563
Microsoft.Graph.Communications.Common:1.2.0.10563
Microsoft.Graph.Communications.Core:1.2.0.10563
Microsoft.Graph.Core:3.1.3
Microsoft.IdentityModel.Clients.ActiveDirectory:3.19.8
Microsoft.IdentityModel.Protocols.OpenIdConnect:6.7.1
Logs
2024-12-18 11:02:57,978 [17] GraphLogger::PalBabakBot - No queue or registered callbacks for
Deleted: /communications/calls/09005280-1a9b-4920-b36a-41120f8d11c9/operations/496ecbca-26fa-45c1-937e-08fd1aed1e4f
2024-12-18 11:04:02,010 [17] GraphLogger::PalBabakBot - {
"value": [
{
"changeType": "Deleted",
"resourceUrl": "/communications/calls/09005280-1a9b-4920-b36a-41120f8d11c9/operations/496ecbca-26fa-45c1-937e-08fd1aed1e4f",
"resource": "/app/calls/09005280-1a9b-4920-b36a-41120f8d11c9/operations/496ecbca-26fa-45c1-937e-08fd1aed1e4f",
"resourceData": {
"@odata.type": "#microsoft.graph.inviteParticipantsOperation",
"participants": [
{
"@odata.type": "#microsoft.graph.invitationParticipantInfo",
"identity": {
"@odata.type": "#microsoft.graph.identitySet",
"user": {
"@odata.type": "#microsoft.graph.identity",
"tenantId": "293c78bf-b98b-4505-a3aa-2f330db99522",
"displayName": "sip:core_agent1@wspa365.dev",
"id": "96bb95f4-7a20-446a-bea5-04541b2001a7"
}
},
"participantId": "58935b36-232d-44fe-b545-e0250249e339"
}
],
"clientContext": "c2056953-fda3-4d35-8083-1ba6a43b251f",
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 603,
"message": "addParticipants failed for participant 8:orgid:96bb95f4-7a20-446a-bea5-04541b2001a7. Underlying reason: Decline. DiagCode: 603#0.@",
"subcode": 0
},
"status": 3,
"id": "496ecbca-26fa-45c1-937e-08fd1aed1e4f"
}
}
]
}
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 OnNotificationProcessed callback and the Participants.InviteAsync call shown in the report, then compare them with the logged Deleted notification for the invite operation. Trace why the callback reports no registered handler while the notification is later logged, and verify that a rejected invite exposes the expected resultInfo with code 603 and a Decline message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100