Raja Subramanian 81f41aca20 Full reconnect on publication mismatch on resume. (#1823) ...

* Full reconnect on publication mismatch on resume.

It is possible that publications mismatch on resume. An example sequence
- Client sends `AddTrack` for `trackA`
- Server never receives it due to signalling connection breakage.
- Client could do a resume (reconnect=1) noticing signalling connection
  breakage.
- Client's view thinks that `trackA` is known to server, but server does
  not know about it.
- A subsequence offer containing `trackA` triggers `trackInfo not
  available before track publish` and the track does not get published.

Detect the case of missing track and issue a full reconnect.

* UpdateSubscriptions from sync state a la cloud

* add missing shouldReconnect

2023-06-24 19:18:05 +05:30

..

clientconfiguration

Added Xiaomi 2201117TI to devices that does not support H.264 (#1728)

2023-05-22 21:38:56 -07:00

config

No proof that this helps (#1772)

2023-06-06 11:28:13 +05:30

routing

Remove unnecessary check (#1806)

2023-06-19 16:40:05 +05:30

rtc

Full reconnect on publication mismatch on resume. (#1823)

2023-06-24 19:18:05 +05:30

service

Send updated events on state updates (#1819)

2023-06-22 09:20:58 -07:00

sfu

Removing commented out short cut path, don't need more debug data. (#1822)

2023-06-23 14:18:55 +05:30

telemetry

Add IngressUpdated event (#1775)

2023-06-16 10:58:49 -07:00

testutils

Improve error message when WaitUntil fails. (#1723)

2023-05-18 14:10:40 -07:00

utils

send min/median connection score along with avg (#1720)

2023-05-18 13:50:54 -04:00