Merge pull request #25993 from microsoftgraph/mcm223-callrecords-session-duplication

Clarify session behavior when CQAA in-memory tranfers are involved

Author: Danielabom

api-reference/beta/resources/callrecords-session.md

@@ -16,6 +16,8 @@ Namespace: microsoft.graph.callRecords
 
 Represents a user-user communication or a user-meeting communication in the case of a conference call.
 
+One session can be returned multiple times if the communication involves more than one service identity. For more information, see [call record API FAQ](/graph/callrecords-api-faq).
+
 ## Methods
 
 | Method       | Return Type | Description |

api-reference/v1.0/resources/callrecords-session.md

@@ -14,6 +14,8 @@ Namespace: microsoft.graph.callRecords
 
 Represents a user-user communication or a user-meeting communication in the case of a conference call.
 
+One session can be returned multiple times if the communication involves more than one service identity. For more information, see [call record API FAQ](/graph/callrecords-api-faq).
+
 ## Methods
 
 | Method       | Return Type | Description |

concepts/callrecords-api-faq.md

@@ -9,7 +9,7 @@ ms.date: 11/07/2024
 
 # Microsoft Graph call records API FAQ
 
-This topic provides answers to frequently asked quesstions about the call records API in Microsoft Graph.
+This topic provides answers to frequently asked questions about the call records API in Microsoft Graph.
 
 ## What is the Microsoft Graph call records API?
 
@@ -92,6 +92,10 @@ You can use the following methods to list all attending call participants:
 
 You might not see all participants because the [List participants_v2](/graph/api/callrecords-callrecord-list-participants_v2) API supports pagination, limiting the number of participants in the response to 130 per page. If there were more than 130 users on the call, the first call record response contains 130 participants along with a `@odata.nextLink` property. This property includes the URL to call the API and receive the next set of participants. Continue this process until the next link is empty, which indicates that there are no more participants to retrieve.
 
+## Why are there duplicate sessions returned for one call record?
+
+A call record [session](/graph/api/resources/callrecords-session) uniquely represents a single user-user communication in peer-to-peer calls or a single user-service communication in a group call or meeting. However, in some calling scenarios a single user-service communication can involve multiple service identities in a single session, such as a virtual transfer between an auto attendant and a call queue. In these scenarios, a session ID might be duplicated one or more times in order to properly represent each identity involved in the communication and the respective communication duration.
+
 ## Why do I receive a 404 Not Found error?
 
 The following are some reasons why you might encounter a `404 Not Found` error: