Steps to reproduce
Attached is a capture of a decrypted RTCP Receiver Report packet sent from Edge. As you can see from the RTCP header, the length is marked as 0x0F. This means there should be 0x0F+1 = 0x10 total 32-bit words in the output) Also from the header, there is only 1 report block in this packet. So the Receiver Report should have a length field equal to 0x07. That leaves 0x10 more 32-bit words in the output that aren’t accounted for. Could you point me towards the extension that is being applied?
Also, extensions in Receiver Reports should only be present if the SDP indicates it as such. And I don’t see any such extension. Can you please add it to the SDP?
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Shijun S.”
Changed Status to “Confirmed”
Changed Status from “Confirmed” to “By design”
Thanks for reaching out to us for the question!
The ORTC API does not have direct dependency on SDP. However, you can get the receiver side capabilities through the getCapabilities() method defined in the RTCRtpReceiver object , and pass in RTCRtpParameters when you call the receive() method. The Edge RTC capabilities  are also listed in the same public spec. You should be able to find the references  for the related protocols as well.
All the Best, Shijun for the Edge Platform team