microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Can not get recording location and token when we end the call directly in Record Response Graph API

Open
#376 15 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

I would like to focus your attention on Record Response API This API sends us callback notification with Recording Location URL and Recording Access Token on the following cases:

  1. When we input some keypad as stopTones (*, #, 1, 2, etc.) to stop the recording completely.
  2. When we keep on recording our voice for 2 min duration
  3. When events like maxSilenceTimeoutInSeconds get triggered

But the issue here is when we end the call directly from the customer phone before max duration reached(2 min) OR maxSilenceTimeoutInSeconds OR without passing stopTones, we didn't get any callback notifications i.e. we lose our recordings.

Is there any way or workaround to resolve this issue?

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 linked Record Response API documentation and the callback behavior for direct call termination. Reproduce the documented completion cases and a customer hang-up, then verify whether a recording location and access token callback is specified; done means confirming supported behavior or documenting a valid workaround.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.