microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Invite participants with phone failed

Open
#410 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Call invite operation with direct routing failed.
{
"participants": [
{
"@odata.type": "#microsoft.graph.invitationParticipantInfo",
"identity": {
"@odata.type": "#microsoft.graph.identitySet",
"phone": {
"@odata.type": "#microsoft.graph.identity",
"id": "+61xxxxxxxx"
}
}
}
],
"clientContext": "671f2c00-8c1f-4341-bd35-c1df3c29fd05"
}

InviteParticipantsOperation always has below error message.
....
"status": "failed",
"clientContext": "671f2c00-8c1f-4341-bd35-c1df3c29fd05",
"resultInfo": {
"@odata.type": "#microsoft.graph.resultInfo",
"code": 412,
"subcode": 9999,
"message": "addParticipants failed for participant 4:+61xxxxxxxx. Underlying reason: Could not find the PSTN content for the sponsor of this PSTN leg.. DiagCode: 412#10073"
},
"id": "8b9e3f46-e5c1-4e1c-813f-b934b811bcf6"
...

Graph version is beta.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the InviteParticipantsOperation request shown in the issue and reproduce it against the Microsoft Graph beta API using the phone identity and direct routing details provided. Review the returned PSTN sponsor error and available Communications API documentation; this is done when the cause and a verified resolution or limitation for phone invitations are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.