At Discuss.io, we are able to speed up the research process dramatically by using the latest and most powerful set of tools. Unlike other video platforms for market research, we have built Discuss.io from the ground up using this WebRTC technology, which is supported in Google Chrome and Mozilla Firefox browsers. We use the best and most innovative WebRTC platform: OpenTok. When you conduct online IDIs and focus groups on the Discuss.io platform, you benefit directly from the powerful capabilities of WebRTC and OpenTok.

Overall, WebRTC is far more reliable and powerful than other options, like Adobe Connect, but like any technology, it occasionally experiences issues. Google and OpenTok are aware of this issue and are actively working to fix this bug within their systems. Justin Uberti, Principal Software Engineer at Google, acknowledged this concern recently, stating, “This is a top priority issue for us. … There’s a lot of work needed to fix this fully, but it is in the top 3 issues we are focusing on for desktop.” Unfortunately, until Google resolves their WebRTC issues, any issues affecting the OpenTok platform will have an impact on your experience while using our product on Google Chrome.

The following are most important known issues for this version of the OpenTok on WebRTC JavaScript library. For the full version, you can check the original article.

Video streaming is prevented on networks that have firewalls that use authenticated proxies. This is due to a core issue with the current underlying WebRTC implementation. (See this Chromium bug report.)

Chrome fails to get access to the microphone, which results in a Publish timeout error and a Subscriber error for any subscriber trying to subscribe to the stream. To work around this issue, the end-user must restart Chrome and reload your site. This is a high-priority bug for Chrome, and they are working on fixing it. Until then, an upcoming release of OpenTok.js will include an event that will be dispatched when this bug occurs, so that you can notify the user to restart the browser.

Reconnection does not work in Firefox. The OpenTok automatic reconnection feature does not currently work in Firefox. This is due to a known issue with offline mode and peer connections in Firefox (see https://bugzilla.mozilla.org/show_bug.cgi?id=1276559).

The OpenTok Automatic Reconnection feature does not work in Firefox or Internet Explorer. Firefox has a known issue with offline mode and peer connections (see this Mozilla bug), which Mozilla is working on.

Setting the frame rate does not work in Firefox on MacOS when using the built-in FaceTime camera. Setting the frameRate option when calling OT.initPublisher() has no effect. This is the Mozilla bug report for the issue.

Issues setting video source for a Publisher in Firefox. In a page loaded via HTTPS, if the user clicks “Always Share” when granting access to the camera, you can only use that camera. You cannot set the video source to another camera.

WebRTC is a peer-to-peer protocol, and it is possible that connections will fail to connect. The most common cause for failure is a firewall that the protocol cannot traverse. When OpenTok detects this failure, the OT object dispatches an exception event object, with the code property set to 1013.

Read more about these WebRTC issues on our blog: https://www.discuss.io/blog/audio-video-issues-chrome-54/

Did this answer your question?