forked from microsoftgraph/microsoft-graph-comms-samples
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updating to latest sample. (microsoftgraph#127)
* Updating to latest sample. * Updating to latest
- Loading branch information
Showing
125 changed files
with
3,113 additions
and
3,290 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,42 @@ The Compliance Recording bot sample guides you through building, deploying and t | |
|
|
||
| This section walks you through the process of deploying and testing the sample bot. | ||
|
|
||
| ### Bot Registration | ||
|
|
||
| 1. Follow the steps in [Register Calling Bot](https://microsoftgraph.github.io/microsoft-graph-comms-samples/docs/articles/calls/register-calling-bot.html). Save the bot name, bot app id and bot secret for configuration. | ||
|
|
||
| 1. Add the following Application Permissions to the bot: | ||
|
|
||
| * Calls.AccessMedia.All | ||
| * Calls.JoinGroupCall.All | ||
|
|
||
| 1. The permission needs to be consented by tenant admin. Go to "https://login.microsoftonline.com/common/adminconsent?client_id=<app_id>&state=<any_number>&redirect_uri=<any_callback_url>" using tenant admin to sign-in, then consent for the whole tenant. | ||
|
|
||
| ### Create an Application Instance | ||
|
|
||
| Open powershell (in admin mode) and run the following commands. When prompted for authentication, login with the tenant admin. | ||
| * `> Import-Module SkypeOnlineConnector` | ||
| * `> $userCredential = Get-Credential` | ||
| * `> $sfbSession = New-CsOnlineSession -Credential $userCredential -Verbose` | ||
| * `> Import-PSSession $sfbSession` | ||
| * `> New-CsOnlineApplicationInstance -UserPrincipalName <[email protected]> -DisplayName <displayName> -ApplicationId <your_botappId>` | ||
| * `> Sync-CsOnlineApplicationInstance -ObjectId <objectId>` | ||
|
|
||
| ### Create a Compliance Recording Policy | ||
| Requires the application instance ID created above. Continue your powershell session and run the following commands. | ||
| * `> New-CsTeamsComplianceRecordingPolicy -Tenant <tenantId> -Enabled $true -Description "Test policy created by <yourName>" <policyIdentity>` | ||
| * ```> Set-CsTeamsComplianceRecordingPolicy -Tenant <tenantId> -Identity <policyIdentity> -ComplianceRecordingApplications ` @(New-CsTeamsComplianceRecordingApplication -Tenant <tenantId> -Parent <policyIdentity> -Id <objectId>)``` | ||
|
|
||
| After 30-60 seconds, the policy should show up. To verify your policy was created correctly: | ||
| * `> Get-CsTeamsComplianceRecordingPolicy <policyIdentity>` | ||
|
|
||
| ### Assign the Compliance Recording Policy | ||
| Requries the policy identity created above. Contine your powershell session and run the following commands. | ||
| * `> Grant-CsTeamsComplianceRecordingPolicy -Identity <[email protected]> -PolicyName <policyIdentity> -Tenant <tenantId>` | ||
|
|
||
| To verify your policy was assigned correctly: | ||
| * `> Get-CsOnlineUser <[email protected]> | ft sipaddress, tenantid, TeamsComplianceRecordingPolicy` | ||
|
|
||
| ### Prerequisites | ||
|
|
||
| * Install the prerequisites: | ||
|
|
@@ -24,29 +60,29 @@ This section walks you through the process of deploying and testing the sample b | |
| 3. Copy the thumbprint for later. | ||
|
|
||
| 1. Set up cloud service configuration | ||
| 1. Open powershell, go to the folder that contains file `configure_cloud.ps1`. The file is in the same directory as `AudioVideoPlaybackBot.sln` | ||
| 2. Run the powershell script with parameters `.\configure_cloud.ps1 -p .\AudioVideoPlaybackBot\ -dns {your DNS name} -cn {your CN name, should be the same as your DNS name} -thumb {your certificate thumbprint} -bid {your bot name} -aid {your bot app id} -as {your bot secret}`, for example `.\configure_cloud.ps1 -p .\AudioVideoPlaybackBot\ -dns bot.contoso.com -cn bot.contoso.com -thumb ABC0000000000000000000000000000000000CBA -bid bot -aid 3853f935-2c6f-43d7-859d-6e8f83b519ae -as 123456!@#$%^` | ||
| 1. Open powershell, go to the folder that contains file `configure_cloud.ps1`. The file is in the `Samples` directory. | ||
| 2. Run the powershell script with parameters: | ||
| * `> .\configure_cloud.ps1 -p .\BetaSamples\LocalMediaSamples\ComplianceRecordingBot\ -dns {your DNS name} -cn {your CN name, should be the same as your DNS name} -thumb {your certificate thumbprint} -bid {your bot name} -aid {your bot app id} -as {your bot secret}`, for example `.\configure_cloud.ps1 -p .\BetaSamples\LocalMediaSamples\ComplianceRecordingBot\ -dns bot.contoso.com -cn bot.contoso.com -thumb ABC0000000000000000000000000000000000CBA -bid bot -aid 3853f935-2c6f-43d7-859d-6e8f83b519ae -as 123456!@#$%^` | ||
|
|
||
| 1. Publish the bot from VS: | ||
| 1. Right click ComplianceRecordingBot, then click `Publish...`. Publish it to the cloud service you created earlier. | ||
|
|
||
| ### Test | ||
|
|
||
| 1. Set up the test meeting and test clients: | ||
| 1. Sign in to Teams client with a non-recorded test tenant user, and schedule a Teams meeting with the recorded user. | ||
|  | ||
| 1. Sign in to Teams client with a non-recorded test tenant user. | ||
| 1. Use another Teams client to sign in with the recorded user. (You could use an private browser window at https://teams.microsoft.com) | ||
|
|
||
| 1. Join the meeting from the Teams client with the non-recorded user. | ||
| 1. Place a call from the Teams client with the non-recorded user to the recorded user. | ||
|
|
||
| 1. Invite the recorded user to the meeting. Your bot should now receive an incoming call, and join the call. (See next step for retrieving logs) Use the recorded user's Teams client to accept the call. | ||
| 1. Your bot should now receive an incoming call, and join the call (See next step for retrieving logs). Use the recorded user's Teams client to accept the call. | ||
|
|
||
| 1. Interact with your service, _adjusting the service URL appropriately_. | ||
| 1. Get diagnostics data from the bot. Open the links in a browser for auto-refresh. Replace the call id 311a0a00-53d9-4a42-aa78-c10a9ae95213 below with your call id from the first response. | ||
| * Active calls: https://bot.contoso.com/calls | ||
| * Service logs: https://bot.contoso.com/logs | ||
|
|
||
| 1. Terminate the call through `DELETE`, as needed for testing. Replace the call id `311a0a00-53d9-4a42-aa78-c10a9ae95213` below with your call id from the first response. | ||
| 1. By default, the call will be terminated when the recording status has failed. You can terminate the call through `DELETE`, as needed for testing. Replace the call id `311a0a00-53d9-4a42-aa78-c10a9ae95213` below with your call id from the first response. | ||
|
|
||
| ##### Request | ||
| ```json | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.