microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Graph API recording duration limitation
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
I would record a call on teams using Graph API.
As mentionned in documentation .
I make a request
POST https://graph.microsoft.com/beta/app/calls/{id}/record
Content-Type: application/json
Content-Length: 394
{
"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", "*" ]
}
I get the response with file locatop,
{
[
{
"changeType": "deleted",
"resource": "/app/calls/57DAB8B1894C409AB240BD8BEAE78896/operations/0FE0623FD62842EDB4BD8AC290072CC5",
"resourceData": {
"@odata.type": "#microsoft.graph.recordOperation",
"@odata.id": "/app/calls/57DAB8B1894C409AB240BD8BEAE78896/operations/0FE0623FD62842EDB4BD8AC290072CC5",
"@odata.etag": "W/\"54451\"",
"clientContext": "d45324c1-fcb5-430a-902c-f20af696537c",
"status": "completed",
"recordResourceLocation": "https://file.location/17e3b46c-f61d-4f4d-9635-c626ef18e6ad",
"recordResourceAccessToken": "<access-token>",
"completionReason": "stopToneDetected"
}
}
]
}
Actual problem
When I request the location url and get the file , the maximum duration of the audio file is 300s
Expected behaviour
Be able to extend the recording time to longer than 300 s ( 5min ) ?
Thanks
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 linked Microsoft Graph call-record documentation and the POST /beta/app/calls/{id}/record example in the issue. Reproduce the request and compare maxRecordDurationInSeconds with the returned five-minute file. Done means the supported duration is clarified or the limitation is addressed, with the result reflected in the issue or relevant project documentation.
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
- Mostly clear
- Newbie friendliness
- 25/100