There is no codecId field on the RTCRTPStreamStats and the corresponding RTCCodecStats objects. Steps to Reproduce: Head to: https://webrtc.github.io/samples/src/content/peerconnection/constraints/ Click "Get media" Click "Connect" Observe there is no codecId in the inbound-rtp stats objects Expected Results: Expect to see codecId in these stat objects. They exist in Chrome and Firefox. Observed Results: No codecId is observed
<rdar://problem/32443068>
rdar://problem/31899622
It is working for me in Safari 17.4 on macOS Sonoma. @Youenn & @Karl - is it reproducible for you or we can mark this as 'RESOLVED CONFIGURATION CHANGED'. On Chrome Canary 124, I get similar codecId.
I see in Report type=outbound-rtp id OT01A4292911247 time 1710215716331 codecId: COT01_111_minptime=10;useinbandfec=1 kind: audio but I don't see it in Report type=inbound-rtp on the other hand in chrome I can see it in inbound-rtp Firefox behaves like Safari.
Our code supports codecId in both outbound and inbound stats. I just tried with https://webrtc.github.io/samples/src/content/peerconnection/constraints/ and I can see codecId in both. Marking as Configuration changed.
Probably fixed in https://bugs.webkit.org/show_bug.cgi?id=189792 *** This bug has been marked as a duplicate of bug 189792 ***