and send back an answer. Note that this assumes the handling of ice role conflicts works.
@jlaine I get flaky failures on nack.html with this one. It is pretty odd, in chrome://webrtc-internals one can see that
1/ iceconnectionstate goes to connected
2/ legacy iceconnectionstate goes to connected (that is the old combined ice+dtls one)
3/ connectionstate goes to failed immediately.
webrtc-internals dump: tlsfail.txt
pcap: dtls-fail.zip
There is a DTLS client hello from Chrome in packet 295 and then a fragmented one from aiortc in packet 300.
One of them is wrong, not sure which side.
and send back an answer. Note that this assumes the handling of ice role conflicts works.
@jlaine I get flaky failures on nack.html with this one. It is pretty odd, in chrome://webrtc-internals one can see that 1/ iceconnectionstate goes to connected 2/ legacy iceconnectionstate goes to connected (that is the old combined ice+dtls one) 3/ connectionstate goes to failed immediately.
webrtc-internals dump: tlsfail.txt pcap: dtls-fail.zip There is a DTLS client hello from Chrome in packet 295 and then a fragmented one from aiortc in packet 300. One of them is wrong, not sure which side.