Raja Subramanian f854201101 Warn on out-of-order RTCP RR. (#1101) ...

Have been seeing a few instances of "too many packets expected in delta"
when trying to generate RTCP SR on down track. Actual sequence numbers
indicate that start is after the end.

As down track RTPStats are driven by receiver report, wondering if we
are getting RTCP_RR out-of-order somehow causing this to happen.
Cannot find any other reason for this.

So, accepting RTCP_RR based update only if the sequence number is higher
than existing and also logging a warning with sequence numbers if they
look out-of-order.

2022-10-19 11:21:43 +05:30

..

clientconfiguration

publish new codec when subscriber needed (#762)

2022-06-16 18:16:34 +08:00

config

Refine nat 1to1 mapping setting (#1094)

2022-10-17 16:11:52 +08:00

logger

Cleanup pass through logging (#1073)

2022-10-06 23:48:37 -07:00

routing

add participant id when client reconnect (#988)

2022-09-07 15:56:56 +08:00

rtc

Misc clean up (#1099)

2022-10-19 05:02:41 +05:30

service

remove record check on CreateRoom (#1096)

2022-10-17 11:25:20 -07:00

sfu

Warn on out-of-order RTCP RR. (#1101)

2022-10-19 11:21:43 +05:30

telemetry

Create stats worker for participant on Active if not exists (#1059)

2022-09-29 17:26:43 -04:00

testutils

Expose Participant.IsPublisher to differentiate pubs from subs (#643)

2022-04-21 22:15:01 -07:00

utils

An attempt to use consistent layer mapping (#986)

2022-09-07 09:57:31 +05:30