It seems like WebRTC by default prioritizes IPv4 over IPv6 when it's available, contrary to most other types of traffic. That is probably because of stability reasons. It may change in the near future.
In my lab, IPv4 and IPv6 WebRTC clients was able to speak to each other. I guess since all traffic gets TURNed, the TURN server doesn't mind if it has to forward traffic from an IPv4 client to an IPv6 client, as long as it is configured with dual stack. Without a TURN/HPB server i don't think it would have been possible. So the answer is no, it worked surprisingly smooth.
Thank you!
It seems like WebRTC by default prioritizes IPv4 over IPv6 when it's available, contrary to most other types of traffic. That is probably because of stability reasons. It may change in the near future.
In my lab, IPv4 and IPv6 WebRTC clients was able to speak to each other. I guess since all traffic gets TURNed, the TURN server doesn't mind if it has to forward traffic from an IPv4 client to an IPv6 client, as long as it is configured with dual stack. Without a TURN/HPB server i don't think it would have been possible. So the answer is no, it worked surprisingly smooth.