Raja Subramanian 9afb0873ae Do not process packets not processed by RTPStats. (#2015) ...

Seeing the case of a stream starting with padding packets
on migration. As publisher in that case is always sending packets.
it is possible that the new node gets padding packets at the start.
Processing them in buffer leads to trying to drop that padding packet
and adding an exclusion range. That fails because the extended
sequence number is not available for unprocessed packets.

It is okay to drop them as they will be dropped anyway.
But, they are useful for bandwidth estimation. So, headers are processed
even if the packet is RTPStats unprocessed.

2023-08-30 19:43:24 +05:30

..

clientconfiguration

Adding license notices (#1913)

2023-07-27 16:43:19 -07:00

config

Stream allocator tweaks (#1936)

2023-08-04 13:47:54 +05:30

routing

Adding license notices (#1913)

2023-07-27 16:43:19 -07:00

rtc

Address comments from #1998 (#2006)

2023-08-27 22:50:36 -07:00

service

Remove sender report warp logs. (#2007)

2023-08-29 00:30:24 +05:30

sfu

Do not process packets not processed by RTPStats. (#2015)

2023-08-30 19:43:24 +05:30

telemetry

preallocate prometheus packet counters (#1942)

2023-08-08 01:06:14 -07:00

testutils

Adding license notices (#1913)

2023-07-27 16:43:19 -07:00

utils

Integrate logger components (#1933)

2023-08-03 13:31:17 -07:00