[FEATURE] Add TCP host candidate support

[hiszpanski]

Is your feature request related to a problem? Please describe. On some networks, UDP traffic between peers is not permitted, but TCP traffic is. In these cases, the peers both select TURN TLS candidates. This increases the proportion of traffic transported via relays. The more desirable route in this scenario is to use host TCP candidates.

Describe the solution you'd like Add support for ICE-TCP, specifically passive host TCP candidates.

Describe alternatives you've considered Have considered solutions that attempt a non-WebRTC alternative path (e.g. HTTP or HTTPS to peer's IP on LAN) in parallel with WebRTC. However, this is non-ideal -- additional complexity.

[hiszpanski]

Note: Chrome does support ICE-TCP option via host candidates if it receives a tcptype passive TCP host candidate.

[github-actions[bot]]

This is a very old issue. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one.