Closed temaivanoff closed 6 years ago
@alessiopcc @markandrus @arlolra @keroserene
A- offer B - Answer
I test the same algorithm node-webrtc
(1.0.4 - v60) and go-webrtc
(v58, v64)
node-webrtc
, A B - waiting, no error, after timeout the connection was successful
go-webrtc
A - waiting, no error, B - exactly after 4 minutes, an error is triggered OnIceCandidateError.
I have not yet found the parent that called OnIceCandidateError
can have special settings when building static libraries? Maybe someone has an assumption why so? Thanks for any help
go-webrtc
version 58 OnIceCandidateError missing, I mistakenly thought that it was tested 58.
But it's still strange why it happens in version 64. When you upgrade to a new version, the problem will repeat
Hi I am generating an answer but do not pass on to the initiator. After 4 minutes I get "OnIceCandidateError". Although the initiator is no such error even after 10 minutes. Such behavior I watch only at this library. In the browser, node-wrtc, it turns out to generate an answer and pass it in 30 minutes the connection will be successful. Maybe someone knows how to increase the timeout? Thanks