Active TCP candidates? #562
Description
In some cases, I will use Pion instead of the browser as the client to push data to the server. When the server only supports tcp-type ice links, the candidate address generated by Pion needs to be an active-mode tcp address. Tried examples/ice-tcp, the current tcp candidate addresses only include passive mode addresses, and I didn’t find any configuration items that can change this.
The phenomenon I encountered is that Pion generates tcp passive candidate addresses, and the server’s candidate addresses only have tcp passive mode, and they always fail to connect.
When I use the browser as a client, it generates tcp's active mode candidates and works fine.
I guess the reason for the inability to connect may be related to the active mode and passive mode. I am sorry that I am a novice in webrtc, and I am not very clear about some underlying principles.
If Pion already supports this function, can you tell me how to make this function take effect?
Thanks.