| title | call: logTeleconferenceDeviceQuality |
|---|---|
| description | Log video teleconferencing device quality data. |
| ms.localizationpriority | medium |
| author | dongkyun |
| ms.subservice | cloud-communications |
| doc_type | apiPageType |
| ms.date | 04/05/2024 |
Namespace: microsoft.graph
[!INCLUDE beta-disclaimer]
Log video teleconferencing device quality data.
The Cloud Video Interop (CVI) bot represents video teleconferencing (VTC) devices and acts as a back-to-back agent for a VTC device in a conference call. Because a CVI bot is in the middle of the VTC and Microsoft Teams infrastructure as a VTC proxy, it has two media legs. One media leg is between the CVI bot and Teams infrastructure, such as Teams conference server or a Teams client. The other media leg is between the CVI bot and the VTC device.
The third-party partners own the VTC media leg and the Teams infrastructure cannot access the quality data of the third-party call leg. This method is only for the CVI partners to provide their media quality data.
[!INCLUDE national-cloud-support]
Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.
[!INCLUDE permissions-table]
POST /communications/calls/logTeleconferenceDeviceQuality| Name | Description |
|---|---|
| Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
| User-Agent | Describes the name and version of the calling application. Details will surface in Azure Information Protection Analytics. Suggested format is ApplicationName/Version. Required. |
In the request body, provide a JSON object with the following parameters.
| Parameter | Type | Description |
|---|---|---|
| quality | teleconferenceDeviceQuality | Quality data of VTC media leg. |
If successful, this method returns a 200 OK response code. It doesn't return anything in the response body.
The following example shows how to call this API.
The following example shows a request.
POST https://graph.microsoft.com/beta/communications/calls/logTeleconferenceDeviceQuality
Content-type: application/json
{
"quality": {
"@odata.type": "#microsoft.graph.teleconferenceDeviceQuality",
"callChainId": "0622673d-9f69-49b3-9d4f-5ec64f42ecce",
"participantId": "ea078406-b5d4-4d3c-b85e-90103dcec7f6",
"mediaLegId": "bd9ee398-4b9d-42c7-8b8d-4e8efad9435f",
"deviceName": "TestAgent",
"deviceDescription": "TestDescription",
"mediaQualityList": [
{
"@odata.type": "#microsoft.graph.teleconferenceDeviceAudioQuality",
"channelIndex": 1,
"mediaDuration": "PT20M",
"networkLinkSpeedInBytes": 13000,
"localIPAddress": "127.0.0.1",
"localPort": 6300,
"remoteIPAddress": "102.1.1.101",
"remotePort": 6301,
"inboundPackets": 5500,
"outboundPackets": 5400,
"averageInboundPacketLossRateInPercentage": 0.01,
"averageOutboundPacketLossRateInPercentage": 0.02,
"maximumInboundPacketLossRateInPercentage": 0.05,
"maximumOutboundPacketLossRateInPercentage": 0.06,
"averageInboundRoundTripDelay": "PT0.03S",
"averageOutboundRoundTripDelay": "PT0.04S",
"maximumInboundRoundTripDelay": "PT0.13S",
"maximumOutboundRoundTripDelay": "PT0.14S",
"averageInboundJitter": "PT0.01S",
"averageOutboundJitter": "PT0.015S",
"maximumInboundJitter": "PT0.023S",
"maximumOutboundJitter": "PT0.024S"
},
{
"@odata.type": "#microsoft.graph.teleconferenceDeviceVideoQuality",
"channelIndex": 1,
"mediaDuration": "PT20M",
"networkLinkSpeedInBytes": 13000,
"localIPAddress": "127.0.0.1",
"localPort": 6300,
"remoteIPAddress": "102.1.1.101",
"remotePort": 6301,
"inboundPackets": 5500,
"outboundPackets": 5400,
"averageInboundPacketLossRateInPercentage": 0.01,
"averageOutboundPacketLossRateInPercentage": 0.02,
"maximumInboundPacketLossRateInPercentage": 0.05,
"maximumOutboundPacketLossRateInPercentage": 0.06,
"averageInboundRoundTripDelay": "PT0.03S",
"averageOutboundRoundTripDelay": "PT0.04S",
"maximumInboundRoundTripDelay": "PT0.13S",
"maximumOutboundRoundTripDelay": "PT0.14S",
"averageInboundJitter": "PT0.01S",
"averageOutboundJitter": "PT0.015S",
"maximumInboundJitter": "PT0.023S",
"maximumOutboundJitter": "PT0.024S"
},
{
"@odata.type": "#microsoft.graph.teleconferenceDeviceScreenSharingQuality",
"channelIndex": 1,
"mediaDuration": "PT20M",
"networkLinkSpeedInBytes": 13000,
"localIPAddress": "127.0.0.1",
"localPort": 6300,
"remoteIPAddress": "102.1.1.101",
"remotePort": 6301,
"inboundPackets": 5500,
"outboundPackets": 5400,
"averageInboundPacketLossRateInPercentage": 0.01,
"averageOutboundPacketLossRateInPercentage": 0.02,
"maximumInboundPacketLossRateInPercentage": 0.05,
"maximumOutboundPacketLossRateInPercentage": 0.06,
"averageInboundRoundTripDelay": "PT0.03S",
"averageOutboundRoundTripDelay": "PT0.04S",
"maximumInboundRoundTripDelay": "PT0.13S",
"maximumOutboundRoundTripDelay": "PT0.14S",
"averageInboundJitter": "PT0.01S",
"averageOutboundJitter": "PT0.015S",
"maximumInboundJitter": "PT0.023S",
"maximumOutboundJitter": "PT0.024S"
}
]
}
}[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
[!INCLUDE sample-code] [!INCLUDE sdk-documentation]
The following example shows the response.
HTTP/1.1 200 OK