David Zhao

`Incoming unhandled RTP ssrc` means a track could not be published properly. Can you provide more details on your use case? How are you using this? which client APIs are...

Are you using `use_external_ip` ? that should help ensure it's advertising a public IP. you can also specify desired interfaces [here](https://github.com/livekit/livekit-server/blob/v0.15.7/config-sample.yaml#L66)

How would you ideally like to configure this? specify each IP address in LiveKit config? some sort of CIDR mask?

This has been fixed in #1052

I think we can deprecate lower protocol versions? We can remove support for protocol 2 in the next minor server update, and it could just reject the connection in that...

This makes sense.. we can probably define something like this in the config and provide a clear reason when a user connects but is rejected.

this is expected behavior to some degree (i.e. peerconnection doesn't remove the transceivers, only add). but we should be better about reusing the downtracks to the participants. FWIW, Google Meets...

we can leave this open. I think on the SFU side, it's possible to re-use the downtracks instead of create new connections. that'll be an improvement going forward.

there's nothing that could explain a 2 minute gap. if you can reproduce this, please provide steps to reproduce this issue. How are you publishing video into livekit?

Closing as we cannot reproduce. Please re-open with specific steps to repro if this remains an issue.