Skip to content

Commit e6b1da1

Browse files
authored
Edits.
1 parent 8b9e9e4 commit e6b1da1

File tree

1 file changed

+23
-21
lines changed

1 file changed

+23
-21
lines changed

concepts/callrecords-api-faq.md

Lines changed: 23 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,41 +1,43 @@
11
---
22
title: "Microsoft Graph Call Records API FAQ"
3-
description: "Find answers to frequently asked questions about Microsoft Call Records API and Call Records notification feed."
3+
description: "Find answers to frequently asked questions about the call records API and call records notification feed in Microsoft Graph."
44
author: "MirraRaine"
55
ms.localizationpriority: high
66
ms.subservice: "cloud-communications"
77
---
88

9-
# Microsoft Graph Call Records API frequently asked questions
9+
# Microsoft Graph call records API FAQ
1010

11-
## What is the Microsoft Graph Call Records API?
11+
This topic provides answers to frequently asked quesstions about the call records API in Microsoft Graph.
1212

13-
The Microsoft Graph Call Records API (Call Records API) offers usage and diagnostic insights for calls and online meetings that occur within your organization when using Microsoft Teams or Skype for Business. Organizations, also referred to as "tenants," can use the Call Records API to subscribe to, list, retrieve call records by call IDs, and to look up calls for a participant. For more information, see [Working with the call records API in Microsoft Graph](/graph/api/resources/callrecords-api-overview).
13+
## What is the Microsoft Graph call records API?
1414

15-
## Which permission is required to use the Call Records API?
15+
The Microsoft Graph call records API offers usage and diagnostic insights for calls and online meetings that occur within your organization when using Microsoft Teams or Skype for Business. Organizations, also referred to as "tenants", can use the call records API to subscribe to, list, retrieve call records by call IDs, and look up calls for a participant. For more information, see [Working with the call records API in Microsoft Graph](/graph/api/resources/callrecords-api-overview).
16+
17+
## Which permission is required to use the call records API?
1618

1719
Your application needs the **CallRecords.Read.All** permission to access call records in Microsoft Graph. An administrator must grant this permission to the application. For more information, see [Microsoft Graph permissions reference](permissions-reference.md).
1820

19-
## Can I use delegated permissions with the Call Records API?
21+
## Can I use delegated permissions with the call records API?
2022

21-
No, the Call Records API doesn't support delegated permissions.
23+
No, the call records API doesn't support delegated permissions.
2224

23-
## Why can't I use delegated permissions with the Call Records API?
25+
## Why can't I use delegated permissions with the call records API?
2426

25-
You can't use delegated permissions because there's no way to limit **CallRecords.Read.All** permission to specific calls or users because the application permission is granted at the organization level, not the individual user level.
27+
You can't use delegated permissions because there's no way to limit **CallRecords.Read.All** permission to specific calls or users. The application permission is granted at the organization level, not the individual user level.
2628

27-
## How do I request a call record using the Microsoft Call Records API?
29+
## How do I request a call record using the call records API?
2830

29-
To request a call record, you need to make a `GET` request to the `/communications/callRecords/{id}` endpoint, where `{id}` is the unique identifier of your call. Ensure you have the **CallRecords.Read.All** permission and include the Authorization header with a valid bearer token. For more information, see [Get callRecord documentation](/graph/api/callrecords-callrecord-get).
31+
To request a call record, you need to make a `GET` request to the `/communications/callRecords/{id}` endpoint, where `{id}` is the unique identifier of your call. Make sure that you have the **CallRecords.Read.All** permission and include the Authorization header with a valid bearer token. For more information, see [Get callRecord documentation](/graph/api/callrecords-callrecord-get).
3032

3133
## Where can I find the call IDs of the calls that occurred in my organization?
3234

3335
You can find and collect call IDs in the following ways:
3436

3537
* **Subscribe to notifications**: Subscribe to [change notifications feed](changenotifications-for-callrecords.md) and receive notifications containing call IDs whenever a new call record is created.
3638
* **List call records**: Get a list of call IDs by requesting it from [List callRecords API](/graph/api/callrecords-cloudcommunications-list-callrecords).
37-
* **Manual search**: If you have access to [Call Analytics](/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality) within the [Teams Admin Center](/microsoftteams/teams-overview) for Microsoft Teams, you can manually search for a call ID in a user’s history. However, there's no automated system available to retrieve all call IDs from Call Analytics.
38-
* **Use callChainId:**: Look up the call ID using the `callChainId` from the [Get call](/graph/api/resources/call) API after the call is completed. Use this approach when the call is programmatically created and you're working with the [call resource type](/graph/api/resources/call). Also, the `callChainId` can differ from the call record ID in certain scenarios, such as transfer calls, due to architecture specifics. Therefore, prefer the other methods in this list when possible.
39+
* **Manual search**: If you have access to [Call Analytics](/microsoftteams/use-call-analytics-to-troubleshoot-poor-call-quality) within the [Teams Admin Center](/microsoftteams/teams-overview) for Microsoft Teams, you can manually search for a call ID in a user’s history. However, no automated system is available to retrieve all call IDs from Call Analytics.
40+
* **Use callChainId:**: Look up the call ID using the `callChainId` from the [Get call](/graph/api/resources/call) API after the call is completed. Use this approach when the call is programmatically created and you're working with the [call resource type](/graph/api/resources/call). Also, the `callChainId` can differ from the call record ID in certain scenarios, such as transfer calls, due to architecture specifics. Therefore, use the other methods in this list when possible.
3941

4042
## When is a call record available?
4143

@@ -47,11 +49,11 @@ Call records are retained for 30 days after the call ends.
4749

4850
## Can I retrieve call records older than 30 days?
4951

50-
No, the Call Records API doesn't return call records older than 30 days. Requests for such records result in a `404 Not Found` error response.
52+
No, the call records API doesn't return call records older than 30 days. Requests for such records result in a `404 Not Found` error response.
5153

5254
## Why is my first call record notification delayed?
5355

54-
Your call record notification can be delayed because it can take up to 60 minutes for the service to make the **first** version of a call record available. If you experience a longer delay for delivery of the first call record version, check for outages reported by the Call Records API team in the "Health" tab of the [Teams Admin Portal](https://admin.teams.microsoft.com/). Also, you can open a [Support Ticket](https://developer.microsoft.com/graph/support) with the Call Records API team.
56+
Your call record notification can be delayed because it can take up to 60 minutes for the service to make the **first** version of a call record available. If you experience a longer delay for delivery of the first call record version, check for outages reported by the call records API team in the **Health** tab of the [Teams Admin Portal](https://admin.teams.microsoft.com/). Also, you can open a [support ticket](https://developer.microsoft.com/graph/support) with the call records API team.
5557

5658
## Why are subsequent versions of my call record delayed?
5759

@@ -63,11 +65,11 @@ A call record can have missing fields due to delayed telemetry from a client. Wh
6365

6466
However, it's important to note that some fields can remain empty by design or because the client telemetry never arrived, such as media stream values.
6567

66-
If critical or previously delivered fields are missing, open a [Support Ticket](https://developer.microsoft.com/graph/support) with the Call Records API team.
68+
If critical or previously delivered fields are missing, open a [support ticket](https://developer.microsoft.com/graph/support) with the call records API team.
6769

6870
## How can I list all participants who attended a call?
6971

70-
You can use the following three methods to list all attending call participants:
72+
You can use the following methods to list all attending call participants:
7173

7274
1. **List participants_v2 API**
7375

@@ -91,8 +93,8 @@ You might not see all participants because the [List participants_v2](/graph/api
9193

9294
## Why do I receive a 404 Not Found error?
9395

94-
The following list shows some reasons why you might encounter a `404 Not Found` error:
96+
The following are some reasons why you might encounter a `404 Not Found` error:
9597

96-
* **Recent Call**: If the call was made within the last 60 minutes, the call record might not be generated yet. Wait 60 minutes after the call ended and try again.
97-
* **Old Call**: If the call is older than 30 days, the Call Records API returns a 404 Not Found error by design.
98-
* **Other Issues**: If neither of the reasons apply, check for any outages reported by the Call Records API team in the "Health" tab of the [Teams Admin Portal](https://admin.teams.microsoft.com/). Also, you can open a [Support Ticket](https://developer.microsoft.com/graph/support) with the Call Records API team for assistance.
98+
* **Recent call**: If the call was made within the last 60 minutes, the call record might not be generated yet. Wait 60 minutes after the call ended and try again.
99+
* **Old call**: If the call is older than 30 days, the call records API returns a `404 Not Found` error by design.
100+
* **Other issues**: If neither of the reasons apply, check for any outages reported by the call records API team in the **Health** tab of the [Teams Admin Portal](https://admin.teams.microsoft.com/). Also, you can open a [support ticket](https://developer.microsoft.com/graph/support) with the call records API team for assistance.

0 commit comments

Comments
 (0)