Raja Subramanian 08997c96b0 Drop not relevant packet only if contiguous. (#2167) ...

The probing + munging has not been set up to drop packets that follow
a gap. Dropping such a packet leads to padding packet sequence numbers
overlapping with regular packets.

This change does two things though.
- The not relevant packet will still not be sent over the wire. That could
create holes in the sequence number leading to NACKs
- Would the hole cause decode issues? Unclear as making this condition is hard.
Simulating it is not showing issues, but that may not be producing the bad
sequence if any.

Will look at the ability to drop a packet after a gap later.

2023-10-22 00:08:41 +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

Use 32-bit time stamp to get reference time stamp on a switch. (#2153)

2023-10-18 21:48:41 +05:30

service

fix CreateEgress not completing (#2156)

2023-10-18 23:18:53 -07:00

sfu

Drop not relevant packet only if contiguous. (#2167)

2023-10-22 00:08:41 +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