Strange RTP packet from DirectTransport Consume

[jbaudanza (Jonathan Baudanza)]

I had a similar problem with ffmpeg, as documented in this thread:

Help debugging duplicate RTP timestamps from WebRTC

I’m passing an Opus RTP stream from WebRTC M89 on Android through MediaSoup to an instance of ffmpeg. Every 5 seconds, my ffmpeg process is receiving a set of three RTP packets with duplicate RTP timestamps, but sequential sequence numbers. The first packet contains audio data, the last two are empty, except for a header extension (RTCP Source Description Items). I’m able to verify this with Wireshark and debug code in ffmpeg. This streams looks something like this: Sequence timestamp …

I fixed it on the ffmpeg side by just ignoring any packet with a length of 0. I’m using the C interface to ffmpeg, I’m not sure if that’s possible with the command line.

This only started becoming a problem with recent version of libwebrtc (around M89 I think)