Skip to content

Commit a80b387

Browse files
committed
Update Recording-logs.md
1 parent fb2bd79 commit a80b387

File tree

1 file changed

+9
-10
lines changed

1 file changed

+9
-10
lines changed

articles/communication-services/concepts/analytics/Recording-logs.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -12,18 +12,17 @@ ms.service: azure-communication-services
1212
ms.subservice: data
1313
---
1414

15-
1615
# Call Recording Summary Log
1716
Call recording summary logs provide details about the call duration, media content (e.g., Audio-Video, Unmixed, Transcription, etc.), the format types used for the recording (e.g., WAV, MP4, etc.), as well as the reason of why the recording ended.
1817

1918
Recording file is generated at the end of a call or meeting. The recording can be initiated and stopped by either a user or an app (bot) or ended due to a system failure.
2019

21-
[!IMPORTANT]
20+
> [!IMPORTANT]
2221
23-
Please note the call recording logs will be published once the call recording is ready to be downloaded. The log will be published within the standard latency time for Azure Monitor Resource logs see [Log data ingestion time in Azure Monitor](../../../azure-monitor/logs/data-ingestion-time.md#azure-metrics-resource-logs-activity-log)
22+
> Please note the call recording logs will be published once the call recording is ready to be downloaded. The log will be published within the standard latency time for Azure Monitor Resource logs see [Log data ingestion time in Azure Monitor](../../../azure-monitor/logs/data-ingestion-time.md#azure-metrics-resource-logs-activity-log)
2423
2524

26-
### Properties Description
25+
## Properties Description
2726

2827
| Field Name | DataType | Description |
2928
|---------- |-----------|--------------|
@@ -56,11 +55,11 @@ A call can have one recording or many recordings depending on how many times a r
5655
For example, if an agent initiates an outbound call in a recorded line and the call drops due to poor network signal, the `callid` will have one `recordingid`. If the agent calls back the customer, the system will generate a new `callid` as well as a new `recordingid`.
5756

5857

59-
#### Example 1: Call recording for " One call to one recording"
58+
#### Example1: Call recording for " One call to one recording"
6059
```json
6160
"properties"
62-
{
63-
"TimeGenerated":"2022-08-17T23:18:26.4332392Z",
61+
{
62+
"TimeGenerated":"2022-08-17T23:18:26.4332392Z",
6463
"OperationName": "RecordingSummary",
6564
"Category": "CallRecordingSummary",
6665
"CorrelationId": "zzzzzz-cada-4164-be10-0000000000",
@@ -80,11 +79,11 @@ For example, if an agent initiates an outbound call in a recorded line and the c
8079

8180
If the agent initiated a recording and stopped and restarted the recording multiple times while the call is still on, the `callid` will have many `recordingid` depending on how many times the recording events were triggered.
8281

83-
#### Example 2: Call recording for " One call to many recordings"
82+
#### Example2: Call recording for " One call to many recordings"
8483
```json
8584

86-
{
87-
"TimeGenerated": "2022-08-17T23:55:46.6304762Z",
85+
{
86+
"TimeGenerated": "2022-08-17T23:55:46.6304762Z",
8887
"OperationName": "RecordingSummary",
8988
"Category": "CallRecordingSummary",
9089
"CorrelationId": "xxxxxxx-cf78-4156-zzzz-0000000fa29cc",

0 commit comments

Comments
 (0)