Firefox Hello: Mozilla enhances OpenTok-powered video chat service

mozilla beta logoMozilla has today released some additional capabilities into the WebRTC communications feature beta it first released a couple months ago and unveiled its name for the first time – Firefox Hello. As always, we’re delighted that OpenTok is the platform of choice for companies building innovative services such as this that are able to scale up to hundreds of thousands of users.

New features of Firefox Hello being released in Firefox Beta today include:

  • New Call Options: One of the key benefits of Firefox Hello is that you don’t need an account to make a call. However, if there are people that you connect with regularly, you can all sign up for a Firefox Account. That enables you to initiate calls directly from your contact list without needing to share a callback link first.
  • Contacts integration: Contacts management has been added for the first time, with functionality for manual input or importing through a Google account. This will make it far easier to call these contacts from within Firefox.

Screen Shot 2014-10-15 at 12.38.29 PM

As Mozilla rolls out Firefox Beta to users over the next few weeks, they will be able to connect with anyone using a WebRTC-enabled browser (such as Firefox, Chrome or Opera) with no need to download software or plugins. These are just a few of the improvements that have been made since the last release.

4 Comments Read More

Mozilla expands experimental WebRTC communications feature into Firefox Beta

webrtc_logoWe know readers of this blog are enthusiasts and thought leaders when it comes to WebRTC implementations. Three months ago Mozilla launched its own experimental WebRTC feature powered by OpenTok into its Firefox Nightly channel. Now they’re calling on you to get involved and test it out as they release it into Firefox Beta.

Since launching this experimental feature it has evolved, and will continue to evolve, but the goal remains the same, to make audio and video communications simple and connect everyone with a WebRTC enabled browser.

0 Comments Read More

Releasing the OpenTok Plugin for Internet Explorer 8-11

opentok plugin for internet explorerToday we’re pleased to announce support for Internet Explorer versions 8 & 9 through our OpenTok Plugin. (The previous version of the plugin supported Internet Explorer 10 & 11.) Now you can leverage the same native WebRTC features enjoyed by Chrome and Firefox users in Internet Explorer versions 8 through 11.

Our release today means that your OpenTok powered applications will automatically start working with Internet Explorer 8 and 9. As always, we’re focused on bringing the best possible real time communications experiences to the endpoints you know and use. This is just one more step forward in our journey towards making the OpenTok platform endpoint agnostic.

0 Comments Read More

Announcing the end-of-life of the OpenTok 1.0 platform

LogoOpenTokCome November, it will have been four years since we launched the OpenTok platform into the world. Can you believe it? During that time technology has evolved, market demands have shifted, and mobile has become king. As your ambassador to real-time communications, we’ve stayed on top of that ever-changing ecosystem.

That’s why we have some important news to share with you – The OpenTok 1.0 platform will no longer be supported as of January 5th, 2015. It was a hard decision to make as the TokBox team and you – the OpenTok community – have dedicated so much time and energy to building on top of it.

5 Comments Read More

WebRTC for Enterprise: Challenges and Solutions

enterprise

WebRTC is changing the way enterprises communicate within their organization and with their customers.

As a result of the large and diverse range of different use cases of WebRTC in the Enterprise world, there are inevitably a number of challenges that need to be addressed. We’ve compiled a  list of some of the key challenges and solutions for consideration with regards to implementing WebRTC for Enterprise solutions: Signaling, Multi-party, Interoperability, Quality and Scalability.

Signaling:

SIP? XMPP? JSON? Rumor? The right answer to the signaling question probably depends a lot on your starting point and on what you’re trying to accomplish.

While many people think signaling should be standardized; others think we already have the answer in SIP or REST. Some maintain that the lack of a signaling specification (beyond the need to support SDP offer/answer) is a huge gap in the WebRTC standard.

0 Comments Read More