Raja Subramanian 126872047d Handle duplicate padding packet in the up stream. (#2012) ...

* Handle duplicate padding packet in the up stream.

The following sequence would have produce incorrect results
- Sequence number 39 - regular packet - offset = 0
- Sequence number 40 - padding only - drop - offset = 1
- Sequence number 40 - padding only duplicate - was not dropped (this is
  the bug) - apply offet - sequence number becomes 39 and clashes with
  previous packet
- Sequence number 41 - regular packet - apply offset - goes through as 40.
- Sequence number 40 again - does not get dropped - will pass through as 39.

* fix duplicate dropping

* fix tests

* accept repeat last value as padding injection could cause that

* use exclusion ranges

* more UT and more specific errors

2023-08-30 16:46:39 +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

Handle duplicate padding packet in the up stream. (#2012)

2023-08-30 16:46:39 +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