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
| 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**|
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, advance 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. 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. Once a call is created, 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 use the `serverCallId` to initiate recording. Once a call is created, 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. Learn how to [Get `serverCallId`](../../quickstarts/voice-video-calling/get-server-call-id.md) 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.
0 commit comments