Is Microsoft Teams and Graph Call Records API support native ipv6?

Asaf Rimon (arimon) 1 Reputation point


We're exploring the Graph Call Records API. We are specifically interesting in the network info, device info and media stream info.
We are using the webhook notification to get the call record id and then query the call record with details to get the call records analytic data.

For instance, we like to identify client end point that initiate a call and trying to understnad the specific call quality from the API.
To idenfity the client end point we extract the ipAddress (IP address of the media endpoint) from microsoft.graph.callRecords.networkInfo.
It seems working fine while the client is associate with ipv4.

My questions are:

  • Is Microsoft Teams support native ipv6? Assuming that we are not useing nat 6 to 4.
  • If so, is ipAddress from microsoft.graph.callRecords.networkInfo will refer to the client ipv6 address?

Thanks for your help

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,030 questions
Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,516 questions
Microsoft Teams Development
Microsoft Teams Development
Microsoft Teams: A Microsoft customizable chat-based workspace.Development: The process of researching, productizing, and refining new or existing technologies.
2,822 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Asaf Rimon (arimon) 1 Reputation point

    I still wait for your reply.

    0 comments No comments

  2. Meghana-MSFT 3,771 Reputation points Microsoft Vendor

    @Asaf Rimon (arimon) - Apologies for the delay in response. Engineering team has confirmed that Teams does not currently support native IPv6, but this functionality is in the backlog. We do not have any ETA regarding the release of this functionality.

    Once Teams supports native IPv6, the client IP address will be available in the Graph Call Records API.

    0 comments No comments