You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| audio + video | mp4 | mixed | 1920x1080 8 FPS video of all participants in default tile arrangement |16kHz mp4a mixed audio of all participants |
33
-
| audio| mp3/wav | mixed | N/A |16kHz mp3/wav mixed audio of all participants |
34
-
| audio| wav | unmixed | N/A |16kHz wav, 0-5 channels, 1 for each participant |
32
+
| audio + video | mp4 | mixed | 1920x1080 eight (8) FPS video of all participants in default tile arrangement |16 kHz mp4 mixed audio of all participants |
33
+
| audio| mp3/wav | mixed | N/A |16 kHz mp3/wav mixed audio of all participants |
34
+
| audio| wav | unmixed | N/A |16 kHz wav, 0-5 channels, 1 for each participant |
35
35
36
36
## Channel types
37
37
> [!NOTE]
@@ -44,14 +44,14 @@ Call recording currently supports mixed audio+video MP4 and mixed audio MP3/WAV
44
44
|**Unmixed audio**| wav | Single file, up to 5 wav channels | Quality Assurance Analytics |**Private Preview**|
45
45
46
46
## Run-time Control APIs
47
-
Run-time control APIs can be used to manage recording via internal business logic triggers, such as an application creating a group call and recording the conversation, or from a user-triggered action that tells the server application to start recording. Call Recording APIs are [Out-of-Call APIs](./call-automation-apis.md#out-of-call-apis), using the `serverCallId` to initiate recording. When creating a call, a `serverCallId` is returned via the `Microsoft.Communication.CallLegStateChanged` event after a call has been established. The `serverCallId` can be found in the `data.serverCallId` field. See our [Call Recording Quickstart Sample](../../quickstarts/voice-video-calling/call-recording-sample.md) to learn about retrieving the `serverCallId` from the Calling Client SDK. A `recordingOperationId` is returned when recording is started, which is then used for follow-on operations like pause and resume.
47
+
Run-time control APIs can be used to manage recording via internal business logic triggers, such as an application creating a group call and recording the conversation. Also, recordings can be triggered by a user action that tells the server application to start recording. Call Recording APIs are [Out-of-Call APIs](./call-automation-apis.md#out-of-call-apis), using the `serverCallId` to initiate recording. When creating a call, a `serverCallId` is returned via the `Microsoft.Communication.CallLegStateChanged` event after a call has been established. The `serverCallId` can be found in the `data.serverCallId` field. See our [Call Recording Quickstart Sample](../../quickstarts/voice-video-calling/call-recording-sample.md) to learn about retrieving the `serverCallId` from the Calling Client SDK. A `recordingOperationId` is returned when recording is started, which is then used for follow-on operations like pause and resume.
| Get Recording State |`recordingOperationId`| Returns `recordingState`|
53
53
| Pause Recording |`recordingOperationId`| Pausing and resuming call recording enables you to skip recording a portion of a call or meeting, and resume recording to a single file. |
54
-
| Resume Recording |`recordingOperationId`| Resumes a Paused a recording operation. Content is included in the same file as content from prior to pausing. |
54
+
| Resume Recording |`recordingOperationId`| Resumes a Paused recording operation. Content is included in the same file as content from prior to pausing. |
55
55
| Stop Recording |`recordingOperationId`| Stops recording, and initiates final media processing for file download. |
56
56
57
57
@@ -60,7 +60,7 @@ Run-time control APIs can be used to manage recording via internal business logi
60
60
> [!NOTE]
61
61
> Azure Communication Services provides short term media storage for recordings. **Recordings will be available to download for 48 hours.** After 48 hours, recordings will no longer be available.
62
62
63
-
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 (e.g. meeting ended, recording stopped). Recording event notifications include `contentLocation` and `metadataLocation`, which are used to retrieve both recorded media and a recording metadata file.
63
+
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.
64
64
65
65
### Notification Schema Reference
66
66
```typescript
@@ -125,7 +125,7 @@ An Event Grid notification `Microsoft.Communication.RecordingFileStatusUpdated`
125
125
126
126
## Regulatory and privacy concerns
127
127
128
-
Many countries and states have laws and regulations that apply to the recording of PSTN, voice, and video calls, which 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.
128
+
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.
129
129
130
130
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.
0 commit comments