webrtc-issue-detector
webrtc-issue-detector copied to clipboard
Diagnostic tool and troubleshooter for WebRTC applications with Mean Opinion Score (MOS) calculator
Hi All, I am currently working on a project to enable VoIP calling on our application. To gauge the quality of the call, I plan to use MOS (Mean Opinion...
Discussed issue [here](https://github.com/VLprojects/webrtc-issue-detector/issues/20) Added new optional `id?: string` param in `handleNewPeerConnection` method and emited the `id` back in callback `calculateNetworkScores`, so now developers can use it that way ```js webRTCIssueDetector.handleNewPeerConnection(pc,...
Hi! How can I distinguish inbound MOS if I have several participants in videocall? I want to connect partner id's and inbound mos value
Hi! I've noticed that the library does rtc stats parsing to calculate mos and possible issues, but does not share the parsed rtc stats. Do you have plans on adding...
Hello, Is this MOS formula based on ITU G.107? If so, is it applicable for video WebRTC stream using RTP (unreliable transport). There is also ITU P.1024.x which targets only...
### Summary `FrozenVideoTrackDetector` previously reported only SSRCs of frozen streams in the `statsSample`. This PR extends the output to include the full frozen stream objects, which contain additional properties such...
### Summary The default jitter threshold in both `InboundNetworkIssueDetector` and `OutboundNetworkIssueDetector` was set to `200`, which corresponds to 200 seconds. Since jitter values are reported in seconds, this default was...