3 ms·
The problem with all of these is that different browsers such as firefox and safari have trouble with negotiating connections. For example we built the softwar
by EGreg 7y ago
The problem with all of these is that different browsers such as firefox and safari have trouble with negotiating connections.
For example we built the software we use on https://intercoin.org/meeting https://intercoin.org/meeting or any website. It works across safari on ios and chrome and we even made a workaround for webviews:
https://mobile.twitter.com/qbixapps/status/1156484156425039872 https://mobile.twitter.com/qbixapps/status/11564841564250398...
But the sdp connections between the browsers fail and A can hear B but C can’t. Weird.
Zoom or Google Hangouts doesn’t have such issues because they always assume one specific environment. Cross browser videoconferencing is not easy
But hey ours is open source and not locked into Twilio or these guys:
https://github.com/Qbix/Platform https://github.com/Qbix/Platform
Search for the string WebRTC
- tpetry 7y agoCan you describe why in some cases one cant hear the other peer? There are different sdp versions if i remember correctly but if you only use audio and video without changing the tracks later on it should work perfectly i guuess.
- EGreg 7y agoHere is what our developers said a week ago: Hi. I learned logs of your meeting where there were problems with peer connections. I couldn't reproduce the bug in real-time for now, I'll continue to debug tomorrow. Some conclusions: - problems with peer connection were happening between Firefox <-> Safari ("Mikki" was using Firefox); - first time (on the beginning of meeting) bug was caused by error In Safari while adding video to peer connection - this interrupted negotiation process: Failed to execute 'setLocalDescription' on 'RTCPeerConnection': Failed to set local offer sdp: Failed to set local video description recv parameters So, Firefox-user didn't receive any video from two Safari users. I googled error, there are very few explanations like a problem with codecs, but I think the bug depends on who was the initiator of peer connection as next time (after reconnections) this error wasn't happening (the similar bug is between Chrome and Firefox). - the second time, the bug was happening only between Firefox (Mikki) and Mobile Safari (Alexandra). This case is less clear for me as the negotiating process wasn't interrupted, but peer connection between these users was failing int several seconds after it was established.