Page History
...
OfficeExpert TrueDEM supports all public versions of Microsoft 365. However, it is a dynamic environment where updates and changes happen often and fast. The OfficeExpert TrueDEM team is dedicated to adjust and fix any issues that can arise from this. If issues can't be resolved immediately we will report them here.
| Info |
|---|
Status - 24th 8th of October 2024 |
Issues with retrieving real-time call data from Microsoft Teams
Updates to newer versions of Microsoft Teams and the way Microsoft performs these updates can, in certain cases, affect the reliability of data retrieval. We are aware of two specific situations where this currently can happen:
- When the Teams client is updated during idle time without a full restart
- When the Teams client restarts certain components in the backend without requiring a complete restart of the Teams client
This can cause the OfficeExpert TrueDEM agent to temporarily loose connection with the Teams client which impacts the collection of real time call data. Other collected data is not impacted. We advice you to reboot the device if this happens and, in general, to make sure devices are regularly rebooted.
...
2025 |
Excessive number of Teams calls are being reported as impacted
Beginning with Teams Version 25227.* (Windows), TrueDEM displays a larger than normal number of Teams calls using video and/or screensharing as impacted.
TrueDEM indicates call quality based on a large number of criteria and conditions. One such condition relates to the lowVideoProcessingCapabilityRatio. TrueDEM flags calls as impacted when this ratio exceeds a pre-defined threshold as it could indicate issues with the local endpoint's ability to process video/screensharing. Since the introduction of the above mentioned Teams version, data provided by Microsoft indicates that nearly every call made on Windows devices is seeing a 100% lowVideoProcessingCapabilityRatio, which clearly exceeds any threshold.
It is highly unlikely that this is the case for every device and call, and the issue was therefor reported to Microsoft for further investigation.