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/concepts/voice-video-calling/call-diagnostics.md
+18-44Lines changed: 18 additions & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.author: amagginetti
7
7
manager: chpalm
8
8
9
9
services: azure-communication-services
10
-
ms.date: 11/21/2023
10
+
ms.date: 06/20/2024
11
11
ms.topic: conceptual
12
12
ms.service: azure-communication-services
13
13
ms.subservice: calling
@@ -79,7 +79,7 @@ selected call.
79
79
80
80
The search field allows you to search by callID. See our documentation to [access your client call ID.](../troubleshooting-info.md#access-your-client-call-id)
81
81
82
-

82
+

83
83
84
84
85
85
> [!NOTE]
@@ -128,6 +128,17 @@ You can view detailed call logs for each participant within a call. Call informa
128
128
129
129

130
130
131
+
## Copilot for Call Diagnostics
132
+
133
+
Artificial Intelligence can help app developers across every step of the development lifecycle: designing, building, and operating. Developers with [Microsoft Copilot in Azure (preview)](../../../copilot/overview.md) can use Copilot within Call Diagnostics to understand and resolve a variety of calling issues. For example, developers can ask Copilot questions, such as:
134
+
135
+
- How do I run network diagnostics in Azure Communication Services VoIP calls?
136
+
- How can I optimize my calls for poor network conditions?
137
+
- What are the common causes of poor media streams in Azure Communication calls?
138
+
- The video on my call didn’t work, how do I fix the subcode 41048?
139
+
140
+

141
+
131
142
<!-- > [!NOTE]
132
143
> You can explore information icons and links within Call Diagnostics to learn functionality, definitions, and helpful tips. -->
- Follow instructions to add diagnostic settings for your resource here [Enable logs via Diagnostic Settings in Azure Monitor.](../analytics/enable-logging.md) We recommend you initially collect all logs and then determine which logs you want to retain and for how long after you have an understanding of the capabilities in Azure Monitor. When adding your diagnostic setting you are prompted to [select logs](../analytics/enable-logging.md#adding-a-diagnostic-setting), select "**allLogs**" to collect all logs.
190
200
191
201
- Your data volume, retention, and Call Diagnostics query usage in Log Analytics within Azure Monitor is billed through existing Azure data meters. We recommend you monitor your data usage and retention policies for cost considerations as needed. See: [Controlling costs.](../../../azure-monitor/essentials/diagnostic-settings.md#controlling-costs)
- Participants from other Azure Communication Services resources will have limited information in Call Diagnostics. The participants that belong to the resource you open Call Diagnostics will have all available insights shown.
198
208
199
-
- What are the common call issues I might see and how can I fix them?
209
+
-**What are the common call issues I might see and how can I fix them?**
200
210
201
211
- Here are resources for common call issues. For an overview of troubleshooting strategies for more information on isolating call issues. Please see: [Overview of general troubleshooting strategies](../../resources/troubleshooting/voice-video-calling/general-troubleshooting-strategies/overview.md)
- If call participants have video issues. For example, their video looks fuzzy, or cuts in and out. See: [Overview of video issues](../../resources/troubleshooting/voice-video-calling/video-issues/overview.md)
214
224
225
+
-**How do I use Copilot in Azure (preview) in Call Diagnostics?**
215
226
216
-
217
-
218
-
<!-- 2. If that ACS resource isn't part of **<u>your Azure subscription
219
-
and / or hasn't enabled Diagnostics Settings to store call logs,
220
-
there will not be any data available</u>** for Call Diagnostics. -->
227
+
- Your organization needs to manage access to [Microsoft Copilot in Azure (preview)](../../../copilot/overview.md). Once your organization has access to Copilot for Azure (preview), the Call Diagnostics interface will include the option to 'Diagnose with Copilot' in the Search, Overview, and Issues tabs.
228
+
- Leverage Copilot for Call Diagnostics to improve call quality by detailing problems faced during Azure Communication Services calls. Giving Copilot detailed information from Call Diagnostics will help it enhance analysis, identify issues, and identify fixes. Be aware that this Copilot iteration lacks programmatic access to your call details.
221
229
222
230
<!-- 1. If Teams participants join a call, how will they display in Call
a. It could no longer be stored by your Log Analytics workspace, you may need to ensure you retain your call data in diagnostics settings. It's possible your callID is incorrect. (**ENG add details on which call ID to specifically pull in the event of multiple callIDs.**)
241
-
242
-
a. Maybe it’s not the ACS call ID, check “how do I find a callID?” to learn more. -->
243
-
244
242
<!-- 1. My call had issues, but Call Diagnostics doesn’t show any issues.
245
243
246
244
a. Call Diagnostics relies on several common call issues to help diagnose calls. Issues can still occur outside of the existing telemetry or can be caused by unlisted call participants you aren’t allowed to view due to privacy restrictions. -->
0 commit comments