Bug 237443

Summary: Implement remote-inbound-rtp packetsLost
Product: WebKit Reporter: Dag-Inge Aas <daginge>
Component: WebRTCAssignee: youenn fablet <youennf>
Status: RESOLVED FIXED    
Severity: Normal CC: eric.carlson, ews-watchlist, glenn, hta, jer.noble, philipj, sergio, tommyw, webkit-bug-importer, youennf
Priority: P2 Keywords: InRadar
Version: Safari 15   
Hardware: All   
OS: All   
Attachments:
Description Flags
Patch none

Dag-Inge Aas
Reported 2022-03-03 12:30:21 PST
Would be great to have remote-inbound-rtp packetsLost implemented to calculate send-side packet loss calculations for media tracks. Chrome now implements this (from https://webrtc.github.io/samples/src/content/peerconnection/constraints/) Report type=remote-inbound-rtp id RTCRemoteInboundRtpAudioStream_1121966634 time 1646339188209.999 ssrc: 1121966634 kind: audio transportId: RTCTransport_0_1 codecId: RTCCodec_0_Outbound_111 jitter: 0.00014583333333333335 packetsLost: 0 <-- here localId: RTCOutboundRTPAudioStream_1121966634 roundTripTime: 0.001 fractionLost: 0 totalRoundTripTime: 0.003 roundTripTimeMeasurements: 3 Would be a great way for us to design UI/handling around packet loss depending on this heuristic, as well as for our own analytical purposes and tagging calls good/bad. Since it's currently unsupported in Safari which amounts to about 60% of our traffic, we lose one important signal of quantitative call quality.
Attachments
Patch (6.68 KB, patch)
2022-03-04 01:33 PST, youenn fablet 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2022-03-04 01:33:19 PST
Created attachment 453822 [details] Patch
Dag-Inge Aas
Comment 2 2022-03-04 02:47:58 PST
Amazing turnaround time! Thank you, youenn!
EWS
Comment 3 2022-03-05 03:34:30 PST
Committed r290865 (248096@main): <https://commits.webkit.org/248096@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 453822 [details].
Radar WebKit Bug Importer
Comment 4 2022-03-05 03:35:17 PST
<rdar://problem/89854282>
Note You need to log in before you can comment on or make changes to this bug.