Merge branch 'MicrosoftDocs:main' into main

Author: inward-eye

articles/communication-services/.openpublishing.redirection.communication-services.json

@@ -54,6 +54,16 @@
         "source_path_from_root": "/articles/communication-services/quickstarts/voice-video-calling/download-recording-file-sample.md",
         "redirect_url": "/azure/communication-services/quickstarts/voice-video-calling/get-started-call-recording",
         "redirect_document_id": false
-      } 
+      },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/voice-video-calling/call-recording-sample.md",
+        "redirect_url": "/azure/communication-services/quickstarts/voice-video-calling/get-started-call-recording",
+        "redirect_document_id": false
+      },
+      {
+        "source_path_from_root": "/articles/communication-services/quickstarts/voice-video-calling/call-recording-unmixed-audio-private-preview-quickstart.md",
+        "redirect_url": "/azure/communication-services/quickstarts/voice-video-calling/get-started-call-recording",
+        "redirect_document_id": false
+      }  
     ]
 }

articles/communication-services/concepts/media/call-recording-client.png

@@ -2,10 +2,9 @@
 title: Azure Communication Services Call Recording overview
 titleSuffix: An Azure Communication Services concept document
 description: Provides an overview of the Call Recording feature and APIs.
-author: tophpalmer
-manager: anvalent
+author: dbasantes
+manager: seaen
 services: azure-communication-services
-
 ms.author: chpalm
 ms.date: 06/30/2021
 ms.topic: conceptual
@@ -25,14 +24,14 @@ Call Recording enables you to record multiple calling scenarios available in Azu
 Depending on your business needs, you can use Call Recording for different Azure Communication Services calling implementations.
 For example, you can record 1:1 or 1:N scenarios for audio and video calls enabled by [Calling Client SDK](https://learn.microsoft.com/azure/communication-services/concepts/voice-video-calling/calling-sdk-features). 
 
-
-![Diagram showing call recording architecture using calling client sdk.](../media/call-recording-with-calling-client.png)
-
+![Diagram showing a call that it's being recorded.](../media/call-recording-client.png)
 
 But also, you can use Call Recording to record complex PSTN or VoIP inbound and outbound calling workflows managed by [Call Automation](https://learn.microsoft.com/azure/communication-services/concepts/voice-video-calling/call-automation).
 Regardless of how you established the call, Call Recording allows you to produce mixed or unmixed media files that are stored for 48 hours on a built-in temporary storage. You can retrieve the files and take them to the long-term storage solution of your choice. Call Recording supports all Azure Communication Services data regions.
 
-## Media output and Channel types supported
+![Diagram showing call recording architecture using calling client sdk.](../media/call-recording-with-call-automation.png)
+
+## Call Recording that supports your business needs
 Call Recording supports multiple media outputs and content types to address your business needs and use cases. You might use mixed formats for scenarios such as keeping records, meeting notes, coaching and training, or even compliance and adherence. Or, you can use unmixed formats to address quality assurance use cases or even more complex scenarios like advanced analytics or AI-based (Artificial Intelligence) sophisticated post-call processes.
 
 ### Video
@@ -53,7 +52,7 @@ Call Recording supports multiple media outputs and content types to address your
 
 
 
-## Call Recording APIs
+## Get full control over your recordings with our Call Recording APIs
 Call Recording 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 use exclusively the `serverCallId` to initiate recording. To learn how to get the `serverCallId`, check our [Call Recording Quickstart](../../quickstarts/voice-video-calling/get-started-call-recording.md).
 A `recordingId` is returned when recording is started, which is then used for follow-on operations like pause and resume.  
 
@@ -68,7 +67,7 @@ A `recordingId` is returned when recording is started, which is then used for fo
 
 
 ## Event Grid notifications
-Notifications related to media and metadata are emitted via Event Grid.
+Call Recording use [Azure Event Grid](https://learn.microsoft.com/azure/event-grid/event-schema-communication-services) to provide you with notifications related to media and metadata.
 
 > [!NOTE]
 > 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.

articles/communication-services/concepts/media/call-recording-concept.png

@@ -8,35 +8,33 @@ ms.custom: public_preview
 
 ## Prerequisites
 
-Before you start testing Call Recording, make sure to comply with the following prerequisites:
-
-
 - You need an Azure account with an active subscription.
 - Deploy a Communication Service resource. Record your resource **connection string**.
 - Subscribe to events via [Azure Event Grid](https://learn.microsoft.com/azure/event-grid/event-schema-communication-services).
 - Download the [.NET SDK](https://dev.azure.com/azure-sdk/public/_artifacts/feed/azure-sdk-for-net/NuGet/Azure.Communication.CallAutomation/overview/1.0.0-alpha.20221013.2)
 
-**IMPORTANT**:  
+## Before you start
+
 Call Recording APIs use exclusively the `serverCallId`to initiate recording. There are a couple of methods you can use to fetch the `serverCallId` depending on your scenario:
-- When using Call Automation, you have two options to get the `serverCallId`:
+
+### Call Automation scenarios
+- When using [Call Automation](../../callflows-for-customer-interactions.md), you have two options to get the `serverCallId`:
     1) Once a call is created, a `serverCallId` is returned as a property of the `CallConnected` event after a call has been established. Learn how to [Get serverCallId](https://learn.microsoft.com/azure/communication-services/quickstarts/voice-video-calling/callflows-for-customer-interactions?pivots=programming-language-csharp#configure-programcs-to-answer-the-call) from Call Automation SDK.
     2) Once you answer the call or a call is created the `serverCallId` is returned as a property of the `AnswerCallResult` or `CreateCallResult` API responses respectively.
 
-- When using Calling Client SDK, you can retrieve the `serverCallId` by using the `getServerCallId` method on the call. 
+### Calling SDK scenarios
+- When using [Calling Client SDK](../../get-started-with-video-calling.md), you can retrieve the `serverCallId` by using the `getServerCallId` method on the call. 
 Use this example to learn how to [Get serverCallId](../../get-server-call-id.md) from the Calling Client SDK. 
 
 
-> [!NOTE]
-> Unmixed audio is in Private Preview and is available in the US only. Make sure to provide the Call Recording team with your [immutable Azure resource ID](../../get-resource-id.md) to be allowlisted during the Unmixed audio **private preview** tests. Changes are expected based on feedback we receive during this stage.
-
-
 
 Let's get started with a few simple steps!
 
 
 
 ## 1. Create a Call Automation client
 
+Call Recording APIs are part of the Azure Communication Services [Call Automation](../../../../concepts/voice-video-calling/call-automation.md) libraries. Thus, it's necessary to create a Call Automation client. 
 To create a call automation client, you'll use your Communication Services connection string and pass it to `CallAutomationClient` object.
 
 ```csharp
@@ -63,6 +61,7 @@ Response<RecordingStateResult> response = await callAutomationClient.getCallReco
 ```
 
 ### 2.1. Only for Unmixed - Specify a user on a channel 0
+To produce unmixed audio recording files, you can use the `ChannelAffinity` functionality to specify which user you want to record on each channel. Channel 0 typically records the agent attending or making the call. If you use the affinity channel but don't specify any user to any channel, Call Recording will assign channel 0 to the first person on the call speaking. 
 
 ```csharp
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<ServerCallId>")) 
@@ -112,6 +111,8 @@ var resumeRecording = await callAutomationClient.GetCallRecording().ResumeRecord
 
 Use an [Azure Event Grid](https://learn.microsoft.com/azure/event-grid/event-schema-communication-services) web hook or other triggered action should be used to notify your services when the recorded media is ready for download.
 
+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.
+
 Below is an example of the event schema.
 
 ```

articles/communication-services/concepts/media/call-recording-conceptual-diagram.png

@@ -8,25 +8,24 @@ ms.custom: public_preview
 
 ## Prerequisites
 
-Before you start testing Call Recording, make sure to comply with the following prerequisites:
-
 - You need an Azure account with an active subscription.
 - Deploy a Communication Service resource. Record your resource **connection string**.
 - Subscribe to events via [Azure Event Grid](https://learn.microsoft.com/azure/event-grid/event-schema-communication-services).
 - Download the [Java SDK](https://dev.azure.com/azure-sdk/public/_artifacts/feed/azure-sdk-for-java/maven/com.azure%2Fazure-communication-callautomation/overview/1.0.0-alpha.20221013.1)
 
-**IMPORTANT**:  
+## Before you start
+
 Call Recording APIs use exclusively the `serverCallId`to initiate recording. There are a couple of methods you can use to fetch the `serverCallId` depending on your scenario:
-- When using Call Automation, you have two options to get the `serverCallId`:
+
+### Call Automation scenarios
+- When using [Call Automation](../../callflows-for-customer-interactions.md), you have two options to get the `serverCallId`:
     1) Once a call is created, a `serverCallId` is returned as a property of the `CallConnected` event after a call has been established. Learn how to [Get serverCallId](https://learn.microsoft.com/azure/communication-services/quickstarts/voice-video-calling/callflows-for-customer-interactions?pivots=programming-language-csharp#configure-programcs-to-answer-the-call) from Call Automation SDK.
     2) Once you answer the call or a call is created the `serverCallId` is returned as a property of the `AnswerCallResult` or `CreateCallResult` API responses respectively.
 
-- When using Calling Client SDK, you can retrieve the `serverCallId` by using the `getServerCallId` method on the call. 
+### Calling SDK scenarios
+- When using [Calling Client SDK](../../get-started-with-video-calling.md), you can retrieve the `serverCallId` by using the `getServerCallId` method on the call. 
 Use this example to learn how to [Get serverCallId](../../get-server-call-id.md) from the Calling Client SDK. 
 
-> [!NOTE]
-> Unmixed audio is in Private Preview and is available in the US only. Make sure to provide the Call Recording team with your [immutable Azure resource ID](../../get-resource-id.md) to be allowlisted during the Unmixed audio **private preview** tests. Changes are expected based on feedback we receive during this stage.
-
 
 
 Let's get started with a few simple steps!
@@ -35,6 +34,7 @@ Let's get started with a few simple steps!
 
 ## 1. Create a Call Automation client
 
+Call Recording APIs are part of the Azure Communication Services [Call Automation](../../../../concepts/voice-video-calling/call-automation.md) libraries. Thus, it's necessary to create a Call Automation client. 
 To create a call automation client, you'll use your Communication Services connection string and pass it to `CallAutomationClient` object.
 
 ```java
@@ -62,7 +62,8 @@ Response<StartCallRecordingResult> response = callAutomationClient.getCallRecord
 
 ```
 
-### 2.1. For Unmixed only - Specify a user on a channel 0
+### 2.1. Only for Unmixed - Specify a user on a channel 0
+To produce unmixed audio recording files, you can use the `ChannelAffinity` functionality to specify which user you want to record on each channel. Channel 0 typically records the agent attending or making the call. If you use the affinity channel but don't specify any user to any channel, Call Recording will assign channel 0 to the first person on the call speaking. 
 
 ```java
 StartRecordingOptions recordingOptions = new StartRecordingOptions(new ServerCallLocator("<serverCallId>"))
@@ -109,6 +110,8 @@ Response<Void> response = callAutomationClient.getCallRecording()
 
 Use an [Azure Event Grid](https://learn.microsoft.com/azure/event-grid/event-schema-communication-services) web hook or other triggered action should be used to notify your services when the recorded media is ready for download.
 
+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.
+
 Below is an example of the event schema.
 
 ```