RTCMultiConnection
RTCMultiConnection copied to clipboard
muaz-khan
After Chrome 72, RTCMultiConnection stops working
Hello Muaz, thanks for great RTCMultiConnection.
I detected that after updating from M71 to M72, the connection is not stablished. After some search, I found out that the problem lays somewhere on new feature called Unified Plan.
I search on your work, and found out the update you applied for connection.sdpSemantics . I saw this guide from main webrtc page and this transition guide and this one about how to set Unified Plan as the main plain for the connection (which is pretty the same you applied in the new update).
I do everything I know to fix the problem, but no luck.
I want to participate in fixing this problem, but don't know how to and what should I do. Can anyone throw some light on this problem?
I saw another problem which make it worth to share here. Both Coturn and Restund servers are seems to be offline on M72. when I use Trickle ICE with provided data, browser says it is unreachable. The data i used for this, is: turn server: turn:webrtcweb.com:7788 username: muazkh credential: muazkh There is something broken inside of chrome, I think. Since using Canary version will show you correct data. I will investigate and email to chrome support.
cannot reproduce anything that you are saying. I have added my test results to the chrome bug report that you have filed... do not see any issues
https://bugs.chromium.org/p/chromium/issues/detail?id=950260&can=2&start=0&num=100&q=&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified&groupby=&sort=
Thanks for your reply. That was weird, using settings > advanced > restore settings to their original defaults solved the problem. Since you cannot say to end user doing this (maybe they are not so that techie to understand the process), I will do the further investigate why this is happenning.
@avspeed TURN is stoped today. So please try xirsys. It may fix the issues.
PS. Please use connection.sdpSemantics='plan-b' and verify it via chrome://webrtc-internals.
PS. From now on, RTCMultIConnection itself is not gonna provide any TURN server. So I'll recommend to install your own coTURN.
PS. PlanB/UnifiedPlan brought too many issues in the current RTCMultiConnection release. These are RTCMultiConnection issues. None of them are related to chromium itself. So please don't report bugs on their threads.
@muaz-khan Thanks for your reply.
RTCMultIConnection is working fine now with no errors, even when the connection to coturn is not established.
I'm not agree with your opinion. This error was absolutely occurs due to misconfiguration of chrome. Your code was working fine using Firefox, and resetting the chrome helped solving the issue.
Although due to respect to you, I will comment to the bug I reported. This may end the thread which was opened.
Hey @AliBahramiEhsan can you explain how do you resolve that problem, in 2022 I am still having that issue, any help?
