Skip to content

Commit ce92e7c

Browse files
dbasantesdbasantes
committed
Changes in the language Audio only for just audio. Improvements on the narrative.
1 parent 846b853 commit ce92e7c

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

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

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ ms.subservice: calling
2020
> [!NOTE]
2121
> Call Recording is not enabled for [Teams interoperability](../teams-interop.md).
2222
23-
Call Recording provides a set of APIs to start, stop, pause and resume recording. These APIs can be accessed from server-side business logic or via events triggered by user actions. Recorded media output is in MP4 Audio+Video format, which is the same format that Teams uses to record media. Notifications related to media and metadata are emitted via Event Grid. Recordings are stored for 48 hours on built-in temporary storage for retrieval and movement to a long-term storage solution of choice. Call Recording supports all ACS data regions.
23+
Call Recording provides a set of APIs to start, stop, pause and resume recording. These APIs can be accessed from server-side business logic or via events triggered by user actions. Recorded media output is in MP4 Audio+Video format, which is the same format that Teams uses to record media. Notifications related to media and metadata are emitted via Event Grid. Recordings are stored for 48 hours on built-in temporary storage for retrieval and movement to a long-term storage solution of choice. Call Recording supports all Azure Communication Services data regions.
2424

2525
![Call recording concept diagram](../media/call-recording-concept.png)
2626

@@ -29,19 +29,19 @@ Call recording currently supports mixed audio+video MP4 and mixed audio-only MP3
2929

3030
| Content Type | Content Format | Channel Type | Video | Audio |
3131
| :----------- | :------------- | :----------- | :---- | :--------------------------- |
32-
| audioVideo | mp4 | mixed | 1920x1080 8 FPS video of all participants in default tile arrangement | 16kHz mp4a mixed audio of all participants |
33-
| audioOnly| mp3/wav | mixed | N/A | 16kHz mp3/wav mixed audio of all participants |
34-
| audioOnly| wav | unmixed | N/A | 16kHz wav, 0-5 channels for each participant |
32+
| 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 |
3535

3636
## Channel types
3737
> [!NOTE]
38-
> **Unmixed audio-only** is still in a **Private Preview** and NOT enabled for Teams Interop meetings.
38+
> **Unmixed audio** is in **Private Preview**.
3939
40-
| Channel type | Content format | Output | Scenario |
41-
|---------------------|-----------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------|
42-
| Mixed audio-video | Mp4 | Single file, single channel | Keeping records and meeting notes Coaching and Training |
43-
| Mixed audio-only | Mp3 (lossy)/ wav (lossless) | Single file, single channel | Compliance & Adherence Coaching and Training |
44-
| **Unmixed audio-only** | Mp3/wav | Single file, multiple channels maximum number of channels is 6 for mp3 and 50 for wav | Quality Assurance Analytics |
40+
| Channel type | Content format | Output | Scenario | Release Stage |
41+
|---------------------|-----------------------------|---------------------------------------------------------------------------------------|---------------------------------------------------------|----------------|
42+
| Mixed audio+video | Mp4 | Single file, single channel | Keeping records and meeting notes Coaching and Training | Public Preview |
43+
| Mixed audio | Mp3 (lossy)/ wav (lossless) | Single file, single channel | Compliance & Adherence Coaching and Training | Public Preview |
44+
| **Unmixed audio** | wav | Single file, up to 5 wav channels | Quality Assurance Analytics | **Private Preview** |
4545

4646
## Run-time Control APIs
4747
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.
@@ -57,6 +57,7 @@ Run-time control APIs can be used to manage recording via internal business logi
5757

5858
## Event Grid notifications
5959

60+
> [!NOTE]
6061
> Azure Communication Services provides short term media storage for recordings. **Export any recorded content you wish to preserve within 48 hours.** After 48 hours, recordings will no longer be available.
6162
6263
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.

0 commit comments

Comments
 (0)