Skip to content

Commit f26e433

Browse files
authored
Update call-recording.md
1 parent f745c94 commit f26e433

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/communication-services/concepts/voice-video-calling/call-recording.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,7 @@ Call Recording use [Azure Event Grid](https://learn.microsoft.com/azure/event-gr
7575
An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated` is published when a recording is ready for retrieval, typically a few minutes after the recording process has completed (for example, meeting ended, recording stopped). Recording event notifications include `contentLocation` and `metadataLocation`, which are used to retrieve both recorded media and a recording metadata file.
7676

7777
### Notification Schema Reference
78+
7879
```typescript
7980
{
8081
"id": string, // Unique guid for event
@@ -103,7 +104,8 @@ An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated`
103104
"eventTime": string // ISO 8601 date time for when the event was created
104105
}
105106
```
106-
## Metadata Schema
107+
### Metadata Schema Reference
108+
107109
```typescript
108110
{
109111
"resourceId": <string>, // stable resource id of the ACS resource recording
@@ -140,7 +142,7 @@ An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated`
140142

141143
Many countries and states have laws and regulations that apply to call recording. PSTN, voice, and video calls, often require that users consent to the recording of their communications. It is your responsibility to use the call recording capabilities in compliance with the law. You must obtain consent from the parties of recorded communications in a manner that complies with the laws applicable to each participant.
142144

143-
Regulations around the maintenance of personal data require the ability to export user data. In order to support these requirements, recording metadata files include the participantId for each call participant in the `participants` array. You can cross-reference the MRIs in the `participants` array with your internal user identities to identify participants in a call. An example of a recording metadata file is provided below for reference.
145+
Regulations around the maintenance of personal data require the ability to export user data. In order to support these requirements, recording metadata files include the participantId for each call participant in the `participants` array. You can cross-reference the MRIs in the `participants` array with your internal user identities to identify participants in a call.
144146

145147
## Known Issues
146148

0 commit comments

Comments
 (0)