Forum Discussion
Graph API: create a PSTN call and invite a PSTN participant
Hello everybody, We are using the MS Graph API within a C# project. After successful creating a PSTN call from our bot like described here https://docs.microsoft.com/en-us/graph/api/application-...
Any update?
A peer-to-peer bot to PSTN call, works as expected, but we receive the following exception when adding a PSTN participant into a group call:
Code: 403
Message: Unexpected 'Failed' status for operation eb8990a2-4dd0-48f8-b171-01ae9092696b:
addParticipants failed for participant 4:+4xxxxxxxxxx. Underlying reason: Forbidden. DiagCode: 403#10151.@
AdditionalData:
subcode: 10151
"@odata.type": "#microsoft.graph.commsNotifications",
"value": [
{
"@odata.type": "#microsoft.graph.commsNotification",
"changeType": "Deleted",
"resourceUrl": "/communications/calls/06206100-0f1d-44dd-88ff-80a5610d7637/operations/9ace7412-7553-4246-b232-80ed4a0f5a35",
"resource": "/app/calls/06206100-0f1d-44dd-88ff-80a5610d7637/operations/9ace7412-7553-4246-b232-80ed4a0f5a35",
"resourceData": {
"@odata.type": "#microsoft.graph.inviteParticipantsOperation",
"participants": [
{
"@odata.type": "#microsoft.graph.invitationParticipantInfo",
"identity": {
"@odata.type": "#microsoft.graph.identitySet",
"phone": {
"@odata.type": "#microsoft.graph.identity",
"id": "+4xxxxxxxxxx"
}
},
"participantId": "f6d17697-0b8c-4f89-946b-b04d43a5d658"
}
],
"clientContext": "f3d0bc58-09c9-4887-8244-c4aaf6fb02b8",
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 403,
"message": "addParticipants failed for participant 4:+4xxxxxxxxxx. Underlying reason: Forbidden. DiagCode: 403#10151.@",
"subcode": 10151
},
"status": "Failed",
"id": "9ace7412-7553-4246-b232-80ed4a0f5a35"
}
}
]
Thank you!
A peer-to-peer bot to PSTN call, works as expected, but we receive the following exception when adding a PSTN participant into a group call:
Code: 403
Message: Unexpected 'Failed' status for operation eb8990a2-4dd0-48f8-b171-01ae9092696b:
addParticipants failed for participant 4:+4xxxxxxxxxx. Underlying reason: Forbidden. DiagCode: 403#10151.@
AdditionalData:
subcode: 10151
"@odata.type": "#microsoft.graph.commsNotifications",
"value": [
{
"@odata.type": "#microsoft.graph.commsNotification",
"changeType": "Deleted",
"resourceUrl": "/communications/calls/06206100-0f1d-44dd-88ff-80a5610d7637/operations/9ace7412-7553-4246-b232-80ed4a0f5a35",
"resource": "/app/calls/06206100-0f1d-44dd-88ff-80a5610d7637/operations/9ace7412-7553-4246-b232-80ed4a0f5a35",
"resourceData": {
"@odata.type": "#microsoft.graph.inviteParticipantsOperation",
"participants": [
{
"@odata.type": "#microsoft.graph.invitationParticipantInfo",
"identity": {
"@odata.type": "#microsoft.graph.identitySet",
"phone": {
"@odata.type": "#microsoft.graph.identity",
"id": "+4xxxxxxxxxx"
}
},
"participantId": "f6d17697-0b8c-4f89-946b-b04d43a5d658"
}
],
"clientContext": "f3d0bc58-09c9-4887-8244-c4aaf6fb02b8",
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 403,
"message": "addParticipants failed for participant 4:+4xxxxxxxxxx. Underlying reason: Forbidden. DiagCode: 403#10151.@",
"subcode": 10151
},
"status": "Failed",
"id": "9ace7412-7553-4246-b232-80ed4a0f5a35"
}
}
]
Thank you!
Sayali-MSFT
Microsoft
Microsoftadrianpopa - We are confirm with the engineering team ,if bot wants to invite another PSTN to join, the P2P call will be escalated into a group call. So far we don't support escalation by adding PSTN. We are working on this feature now and it will be ready soon.
So, here are some scenarios:
1. P2P call between Bot and another peer (Teams user, PSTN), bot invites another PSTN: Not supported.
2. P2P call between Bot and another peer (Teams user, PSTN), bot invites another Teams user: Supported.
3. P2P call between Bot and another peer (Teams user, PSTN), bot invites another bot: Supported.
So, here are some scenarios:
1. P2P call between Bot and another peer (Teams user, PSTN), bot invites another PSTN: Not supported.
2. P2P call between Bot and another peer (Teams user, PSTN), bot invites another Teams user: Supported.
3. P2P call between Bot and another peer (Teams user, PSTN), bot invites another bot: Supported.
Sayali-MSFT - Thanks for the confirmation.
From our tests, also the following scenario is not supported: group call between Bot and 2+ users, bot invites another PSTN, so no group escalation. Exception: addParticipants failed for participant 4:+4xxxxxxxxxx. Underlying reason: Forbidden. DiagCode: 403#10151.
Tested with both direct routing and calling plans. The Bot can receive and create P2P PSTN calls.
- I would like to add to the scenario adrianpopa, there is a difference in how the group call was created.
A) When having a group call where the 'escalation part' is done by inviting a Teams user, you cannot invite a PSTN participant.
B) When having a group call where the 'escalation part' is done by inviting a PSTN user, you can invite another PSTN participant.
I noticed there is a slight difference in the calls (by requesting info via graph) before requesting the 4th particpant depending on the scenario:
A ChatInfo null,
B ChatInfo not null
A meetingCapability null
B meetingCapability not null
A pstnDetails null
B pstnDetails not null (altough the values are guid's with all '0' and dialinUrl null)
The only difference here is that A uses POST /participants/invite with a azure id, and B with a phone number (before requesting an additional participant with PSTN) - I can make a bot to PSTN call and bot to teas users
I am trying to make a group call bot, teams user and PSTN. Please assist
