Forum Discussion
Number of participants is reported inaccurately on CallRecord endpoint
We have been pulling CallRecord data via Graph API for analysis. One particular record grabbed our attention. According to the JSON return from Graph API there were 40 participants and 60 sessions. ...
Meghana-MSFT
Microsoft
MicrosoftThank you for reporting this, we will check this and get back to you.
Hi there. Do you have any updates on this issue yet? I look forward to hearing from you.
- Meghana-MSFTApologies for the delay, we are following up with the engineering team for an update. We will update you.
- Meghana-MSFT
palezvar - Engineering team requires below details. Could you please share below details?
Is this on beta or v1.0 version of callRecord Graph API? Also, is this a regular call/conference or a special meeting type like a Teams Live Event or TownHall?
Currently participants are not paginated on v1.0, it's a single collection at the callRecord level and limited to 130 results. We recently introduced pagination for the participant_v2 relationship in beta, which should be available in v1.0 in the next few weeks.
Without seeing a specific Call Id it's hard to know the exact reason why there might be a discrepancy between CQD and Graph, but my guess is that this may be a live event with streaming participants. Streaming users are not currently supported in callRecord Graph API.
- This is what we use: https://graph.microsoft.com/v1.0/communications/callRecords/{id}
We grab the participant section of the return for that particular call I mentioned. The number of participants listed is 45 but according to CQD it is more than 100. Do we need to engage "/communications/calls/{id}/participants" endpoint and not reply on the participant content returned in callRecord?
This was a conference call. Is there a way for me to send you the call id directly instead of sharing it here?
Thanks
