microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Recording - Loop not supported
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
When creating a call using the standard body listed in the API docs:
{
"bargeInAllowed": true,
"clientContext": "d45324c1-fcb5-430a-902c-f20af696537c",
"prompts": [
{
"@odata.type": "#microsoft.graph.mediaPrompt",
"mediaInfo": {
"uri": "https://cdn.contoso.com/beep.wav",
"resourceId": "1D6DE2D4-CD51-4309-8DAA-70768651088E"
},
"loop": 5
}
],
"maxRecordDurationInSeconds": 1800,
"initialSilenceTimeoutInSeconds": 10,
"maxSilenceTimeoutInSeconds": 2,
"recordingFormat": "wav",
"playBeep": true,
"streamWhileRecording": true,
"stopTones": [ "#", "11", "*" ]
}
Receive an error 400 due to message: "RecordAction: Loop not supported."
Removing the ,
"loop": 5
From the body resolves this.
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 standard request body shown in the API docs and reproduce the 400 response with the prompts.loop field present. Compare the documented loop behavior with the returned “Loop not supported” message; done means the supported behavior or the documentation is clarified and the discrepancy is addressed.
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