Raja Subramanian f653efcf10 Do not update highest time on padding packet. (#2157) ...

* Error log of padding updating highest time to get backtrace.

* Do not update highest time on padding packet.

Padding packets use time stamp of last packet sent.
Padding packets could be sent when probing much after last packet
was sent. Updating highest time on that screws up sender report
calculations. We have ways of making sure sender reports do not
get too out-of-whack, but it logs during that repair.
That repair should be unnecessary unless the source is behaving weird
(things like publisher sending all packets at the same time, publisher
sample rate is incorrect, etc.)

2023-10-19 12:01:48 +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

Do not update highest time on padding packet. (#2157)

2023-10-19 12:01:48 +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