microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Bot Configuration

Open
#291 4 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

Hello Team,

We are trying to implement the call recording policy at our end for auditing purposes.

I have been referring to this post , However I have been experiencing challenges in getting the bot implemented as the post is not descriptive enough.

The post mentions that "The Policy Recording bot sample guides you through building, deploying and testing a bot. This sample demonstrates how a bot can receive media streams for recording. Please note that the sample does not actually record. This logic is left up to the developer."

Plus I have been gifted with tons of errors when trying to build the project #259

I can see many of you have implemented this and have been able to record and retrieve calls.

It would be my humble request to all the bright minds out here to help me battle this out with the help of detailed steps or documentation as to how the bot was setup in your respective environments.

This would be of great help to me or anyone else who is trying to implement this functionality.

Thanks and Regards,
Vivek

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 referenced Policy Recording bot sample post and issue #259 to identify the setup and build problems described there. Done should be detailed, reproducible documentation covering bot setup, deployment, testing, and the steps needed to implement call recording and retrieve recordings.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.