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
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/pre-call-diagnostics/pre-call-diagnostics-android.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,25 @@
1
1
---
2
-
title: Azure Communication Services pre-call diagnostics
2
+
title: Azure Communication Services precall diagnostics
3
3
titleSuffix: An Azure Communication Services concept document
4
-
description: Overview of the pre-call diagnostic API feature.
4
+
description: Overview of the precall diagnostic API feature.
The pre-call API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see pre-call diagnostics enabled.
18
+
The precall API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access precall features using the Calling SDK. The precall diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see precall diagnostics enabled.
19
19
20
-
## Pre-Call diagnostics access
20
+
## Precall diagnostics access
21
21
22
-
To access pre-call diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
22
+
To access precall diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
When the pre-call diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of pre-call diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
81
+
When the precall diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of precall diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/pre-call-diagnostics/pre-call-diagnostics-ios.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,25 @@
1
1
---
2
-
title: Azure Communication Services pre-call diagnostics
2
+
title: Azure Communication Services precall diagnostics
3
3
titleSuffix: An Azure Communication Services concept document
4
-
description: Overview of the pre-call diagnostic API feature.
4
+
description: Overview of the precall diagnostic API feature.
The pre-call API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see pre-call diagnostics enabled.
18
+
The precall API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access precall features using the Calling SDK. The precall diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see precall diagnostics enabled.
19
19
20
-
## Pre-Call diagnostics access
20
+
## Precall diagnostics access
21
21
22
-
To access pre-call diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
22
+
To access precall diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
23
23
24
24
```swift
25
25
let acsToken: String;
@@ -103,7 +103,7 @@ let permissionList = preCallDiagnosticsFeature?.devicePermissions()
103
103
104
104
## Pricing
105
105
106
-
When the pre-call diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of pre-call diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
106
+
When the precall diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of precall diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/pre-call-diagnostics/pre-call-diagnostics-javascript.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
-
title: Azure Communication Services pre-call diagnostics
2
+
title: Azure Communication Services precall diagnostics
3
3
titleSuffix: An Azure Communication Services concept document
4
-
description: Overview of the pre-call diagnostic API feature.
4
+
description: Overview of the precall diagnostic API feature.
The pre-call API feature enables developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see pre-call diagnostics enabled.
18
+
The precall API feature enables developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access precall features using the Calling SDK. The precall diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see precall diagnostics enabled.
19
19
20
20
## Prerequisites
21
21
@@ -30,12 +30,12 @@ The pre-call API feature enables developers to programmatically validate a clien
30
30
31
31
For more information, see [Use Azure CLI to Create and Manage Access Tokens](../../quickstarts/identity/access-tokens.md?pivots=platform-azcli).
32
32
33
-
## Accessing pre-call diagnostics
33
+
## Accessing precall diagnostics
34
34
35
35
>[!IMPORTANT]
36
36
>Pre-call diagnostics are available starting with version [1.9.1-beta.1](https://www.npmjs.com/package/@azure/communication-calling/v/1.9.1-beta.1) of the Calling SDK. Make sure to use that version or higher when following these instructions.
37
37
38
-
To Access pre-call diagnostics, you need to initialize a `callClient`, and provision an Azure Communication Services access token. There you can access the `PreCallDiagnostics` feature and the `startTest` method.
38
+
To Access precall diagnostics, you need to initialize a `callClient`, and provision an Azure Communication Services access token. There you can access the `PreCallDiagnostics` feature and the `startTest` method.
@@ -124,7 +124,7 @@ If devices aren't available, the user shouldn't continue into joining a call. Ra
124
124
125
125
Performs a quick call to check in-call metrics for audio and video and provides results back. Includes connectivity (`connected`, boolean), bandwidth quality (`bandWidth`, `'Bad' | 'Average' | 'Good'`) and call diagnostics for audio and video (`diagnostics`). Provided diagnostic categories include `jitter`, `packetLoss`, and `rtt` and results are generated using a simple quality grade (`'Bad' | 'Average' | 'Good'`).
126
126
127
-
InCall diagnostics uses [Media quality statistics](./media-quality-sdk.md) to calculate quality scores and diagnose issues. During the pre-call diagnostic, the full set of media quality statistics are available for consumption. These statistics include raw values across video and audio metrics that you can use programatically.
127
+
InCall diagnostics uses [Media quality statistics](./media-quality-sdk.md) to calculate quality scores and diagnose issues. During the precall diagnostic, the full set of media quality statistics are available for consumption. These statistics include raw values across video and audio metrics that you can use programatically.
128
128
129
129
The InCall diagnostic provides a convenience layer on top of media quality statistics to consume the results without the need to process all the raw data. For more information including instructions to access, see [Media quality statistics for an ongoing call](./media-quality-sdk.md#media-quality-statistics-for-an-ongoing-call).
130
130
@@ -148,7 +148,7 @@ At this step, there are multiple possible failure points. The values provided by
148
148
149
149
## Pricing
150
150
151
-
When the pre-call diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of pre-call diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
151
+
When the precall diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of precall diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/voice-video-calling/includes/pre-call-diagnostics/pre-call-diagnostics-windows.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,25 +1,25 @@
1
1
---
2
-
title: Azure Communication Services pre-call diagnostics
2
+
title: Azure Communication Services precall diagnostics
3
3
titleSuffix: An Azure Communication Services concept document
4
-
description: Overview of the pre-call diagnostic API feature.
4
+
description: Overview of the precall diagnostic API feature.
The pre-call API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access pre-call features using the Calling SDK. The pre-call diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see pre-call diagnostics enabled.
18
+
The precall API feature allows developers to programmatically validate a client’s readiness to join an Azure Communication Services call. You can only access precall features using the Calling SDK. The precall diagnostic feature provides multiple diagnostics including device, connection, and call quality. Provide us with [feedback](../../support.md) about which platforms you want to see precall diagnostics enabled.
19
19
20
-
## Pre-Call diagnostics access
20
+
## Precall diagnostics access
21
21
22
-
To access pre-call diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
22
+
To access precall diagnostics, you need to initialize a `CallClient`, and provision an Azure Communication Services access token. Then you can access the `PreCallDiagnostics` feature and the `startTest` method.
23
23
24
24
```c#
25
25
stringacsToken="";
@@ -41,7 +41,7 @@ Once it finishes running, developers can access the result object.
41
41
42
42
## Diagnostic results
43
43
44
-
Pre-call diagnostics return a full diagnostic of the device including details like availability and compatibility, call quality statistics, and in-call diagnostics. The results are returned as a `PreCallDiagnosticsReadyEvent` object.
44
+
Precall diagnostics return a full diagnostic of the device including details like availability and compatibility, call quality statistics, and in-call diagnostics. The results are returned as a `PreCallDiagnosticsReadyEvent` object.
@@ -79,7 +79,7 @@ var permissionList = preCallDiagnosticsFeature.DevicePermissions;
79
79
80
80
## Pricing
81
81
82
-
When the pre-call diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of pre-call diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
82
+
When the precall diagnostic test runs behind the scenes, it uses calling minutes to run the diagnostic. The test lasts for roughly 30 seconds, using up 30 seconds of calling time which is charged at the standard rate of $0.004 per participant per minute. For the case of precall diagnostics, the charge is for 1 participant x 30 seconds = $0.002.
0 commit comments