Forum Discussion

palezvar's avatar
palezvar
Copper Contributor
Jan 26, 2024

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. ...
Microsoft Graph Api
microsoft teams
Meghana-MSFT's avatar
Meghana-MSFT
Bronze Contributor
Jan 29, 2024
Thank you for reporting this, we will check this and get back to you.
  • palezvar's avatar
    palezvar
    Copper Contributor
    Feb 02, 2024
    Hi there. Do you have any updates on this issue yet? I look forward to hearing from you.
    • Meghana-MSFT's avatar
      Meghana-MSFT
      Bronze Contributor
      Feb 05, 2024
      Apologies for the delay, we are following up with the engineering team for an update. We will update you.
      • Meghana-MSFT's avatar
        Meghana-MSFT
        Bronze Contributor
        Feb 06, 2024

        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.

Resources