You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS name: Ubuntu
OS version: 22.04.2LTS
Architecture: Linux em04 5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
nprobe version/revision: nProbe v.10.3.230629 for x86_64-pc-linux-gnu, Built with nDPI 4.7.0-4188-86e89b4e
What happened:
★Both Microsoft Teams and Zoom have this problem.
The nprobe's RTP plugin shows blank values for the MOS and R_FACTOR like attached file. bug report2ntop.xlsx
In my understandings If the "L7 PROTO" is "91.125" it should be reported with the MOS and R_FACTOR but it is still blank.
This attached data is when Microsoft Teams meeting was ongoing.
Could you share the condition details when the nprobe wrote the MOS and R_FACTOR value?
How did you reproduce it?
If you do Microsoft Teams or Zoom you could reproduce this one.
Debug Information:
Kindly refer to the attached file.
regards,
Yoshihiro
The text was updated successfully, but these errors were encountered:
Environment:
OS name: Ubuntu
OS version: 22.04.2LTS
Architecture: Linux em04 5.15.0-73-generic #80-Ubuntu SMP Mon May 15 15:18:26 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
nprobe version/revision: nProbe v.10.3.230629 for x86_64-pc-linux-gnu, Built with nDPI 4.7.0-4188-86e89b4e
What happened:
★Both Microsoft Teams and Zoom have this problem.
The nprobe's RTP plugin shows blank values for the MOS and R_FACTOR like attached file.
bug report2ntop.xlsx
In my understandings If the "L7 PROTO" is "91.125" it should be reported with the MOS and R_FACTOR but it is still blank.
This attached data is when Microsoft Teams meeting was ongoing.
Could you share the condition details when the nprobe wrote the MOS and R_FACTOR value?
How did you reproduce it?
If you do Microsoft Teams or Zoom you could reproduce this one.
Debug Information:
Kindly refer to the attached file.
regards,
Yoshihiro
The text was updated successfully, but these errors were encountered: