Raja Subramanian 2ff8fe3b78 Prevent old packets resolution. (#2134) ...

* Prevent old packets resolution.

With range map, we are just looking up ranges and not exactly
which packets were missing. This caused the case of old packets
being resolved after layer switch.

For example,
- Packet 10 is layer switch, range map gets reset
- Packet 11, 12, 13 are forwarded
- Packet 9 comes, it should ideally be dropped as pre-layer switch old
  packet. But, when looking up range map, it gets an offset and hence
  gets re-mapped to something before layer switch. This was probably
  okay as decoders would have had a key frame at the switch point and
  moved ahead, but incorrect technically.

Fix is to reset the start point in the range map to the switch point
and not 0. So, when packet 9 comes, range map will return "key too old"
error and that packet will be dropped as missing from cache.

* fix tests

2023-10-07 10:56:34 +05:30

..

clientconfiguration

Adding license notices (#1913)

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

config

Add SyncStreams flag to Room (#2110)

2023-09-28 15:41:44 +08:00

routing

Use random NodeID instead of MAC based (#2029)

2023-09-02 17:36:55 -07:00

rtc

Allow playout delay even when sync stream isn't used. (#2133)

2023-10-06 14:51:11 -07:00

service

Create stub for update outputs in egress service (#2132)

2023-10-05 12:00:47 -07:00

sfu

Prevent old packets resolution. (#2134)

2023-10-07 10:56:34 +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