I made some tests to create an offer with iceRestart to true and the result seems it’s not supported by the library. Can you confirm? I saw an issue on github where someone talk about iceRestart but it does nothing for me.
Normally the SDP must contains a new ice-ufrag and ice-pwd but the result is actually, i have the same.
Does someone have input? Thank you for your feedback.
I checked yesterday on the react-native-webtc and i saw you call directly the libwebrtc. So maybe there is an issue with the M67 library. I read the M6X changelog and i don’t see anything about that. But i did the same test (same code) with chrome (the latest version) then my app and the result is very different. The strange things is the ice restart is probably launch, because i see new ice candidate, but the issue is ice-ufrag and pwd is the same.
For information my test is to switch from wifi network to a cellular network.
Ok long time ago we discussed about this subject ;).
I worked on this subject and now with the 0.84 support i have some success. But looks like when we use { IceRestart : “yes” }, we loose our STUN or TURN configuration. So my ICE agent restart the ice candidate but without my first configuration.
To test it i use a TURN server for my first call, i bind my ICE restart on a WiFI - 4G switch and my media switch to a classic STUN way instead using my TURN service.
Before to continue my research i would like to be sure someone have the same issue, i suspect we don’t have the correct support on the lib.
TBH I’m not sure. Last I checked all parameters are passed ok down to
libWebRTC. Now, we don’t use iceRestart on Jitsi, so I don’t have a good
way to verify it either.