- Sept 30 – Oct 2 / Chicago – IIT Real-time Communications Conference
(For me, this is “the” objective gathering of the brightest technical minds in the RTC space.) Robin Raymond will be speaking on ORTC / WebRTC 1.1 and also Cloud + P2P Communications.
- 30-31 Oct / Santa Clara – W3C TPAC / WebRTC WG Meeting
(W3C Technical Plenary / Advisory Committee Meetings Week which includes WebRTC Working Group meetings. This should be a rather interesting set of meetings for the WebRTC WG, for a variety of reasons.)
(tba) Oct ? / Web – W3C ORTC Community Group Meeting
- Nov 4-6 / Santa Clara – Cloud Expo / WebRTC Summit
(One of the bigger events, plenty more happening here than just WebRTC.) Erik Lagerway will be speaking on Real-time Communications, PaaS & Cloud Communications.)
- Nov 9-14 / Honolulu – IETF Meeting 91 / RTCWEB WG Meetings
- Nov 18-20 / San Jose – WebRTCworld Conference West
- Dec 16-18 / Paris – WebRTC Conference Expo Paris
The first ORTC Public Draft Specification has been published, authored by Hookflash, Microsoft, and Google. (http://ortc.org/wp-content/uploads/2014/08/ortc.html ) This specification extends WebRTC 1.0 with new functionality to create a WebRTC 1.1 API with exceptional flexibility and no loss of compatibility.
Like WebRTC, ORTC (Object Real-time Communication) enables plugin-free real-time communications for mobile, web and cloud, but is specifically tailored to provide the direct control needed to enable advanced multimedia and conferencing features.
“We heard developers say that they wanted more direct control over the technologies available in WebRTC. At the same time, we didn’t want existing developers to have to start over with a new API. ORTC is our proposal for how we can accomplish both of these things – a new set of APIs for direct control, that builds off the existing WebRTC 1.0 API set. As an evolution of the existing API, we consider this WebRTC 1.1” comments Justin Uberti, Google Tech Lead, WebRTC. “We’re grateful to Hookflash for their work to get ORTC off the ground. They have been instrumental in making this cross-industry collaboration happen, and we look forward to continuing our work with them.”
This newly published public draft has come a long way since the W3C ORTC Community Group was formed in mid-2013. As it has progressed from an initial set of ideas to a fleshed-out draft complete enough for implementations, several companies have gotten closely involved, with Microsoft and Google now joining Hookflash as authors of the emerging specification.
The W3C ORTC Community Group now numbers more than 60 participants.
“We believe the contributions to WebRTC 1.1 / ORTC will allow web communications technology to become ubiquitous and transcend nearly all communications technologies that came before it” says Hookflash Co-founder, Erik Lagerway, “We are honored to be working with some of the brightest minds at Google, Microsoft, and the other contributing members in the ORTC CG to mature WebRTC into a universal go-to toolkit enabling communications across the globe.”
Hookflash enables real-time social, mobile, and web communications for integration of voice, video, messaging with federated identity into world leading software, enterprise, applications, networks, mobile and computing devices. Hookflash and Open Peer are trademarks of Hookflash Inc.
Developers can register at (http://fly.hookflash.me) to start using the Hookflash RTC service and toolkits today. For more information on Hookflash RTC toolkits and White Labeling please visit Hookflash http://hookflash.com.
Come and work at one of the coolest companies in the space! We’re now hiring for these development positions: iOS, Android, Node.js & C++ send us your resume: email@example.com.
Hookflash – Trent Johnsen
855-466-5352 Ext: 1
The WebRTC media stack has been ported to QNX / Blackberry 10 as reported hy Hookflash in this Press Release below.
This does not mean that WebRTC browsers will now begin communicating with Blackberry apps written using the Open Peer SDK, well… not today anyhow. What it does mean is Blackberry 10 developers can write apps using this new SDK to enable P2P voice, video and messaging, across Blackberry and iOS platforms using their own user identity model or mashed up with social identities.
In the sample app (pictured above) running on a production Z10 and a Alpha Z10 device, Facebook was used to map IDs.
Here is the Press Release…
BlackBerry Live 2013, Orlando Florida – May 13, 2013 – Hookflash announces beta availability of Open Peer Software Development Kit (SDK) for BlackBerry® 10, providing developers with an effective way to integrate high quality, secure, real-time, voice, video and messaging into their own BlackBerry 10 applications.
“The Open Peer SDK for BlackBerry 10 enables a completely new generation of communications integration on the BlackBerry 10 platform,” explains Hookflash co-founder Erik Lagerway. “The Hookflash team has worked tirelessly to build this toolkit and port the WebRTC libraries to BlackBerry 10. BlackBerry developers and enterprise customers can now integrate high quality, real-time, peer-to-peer (P2P), voice, video and messaging into their own BlackBerry 10 applications. People just want good quality voice, video and text communications embedded in whatever they’re doing. Open Peer enables progressive developers in medical, finance, gaming, travel and many other verticals with this next evolution of integrated P2P communications on BlackBerry 10 smartphones.”
“BlackBerry is committed to our app partners through an open ecosystem, strong platform and commitment to supporting innovation and invention,” said Martyn Mallick, VP of Global Alliances and Business Development at BlackBerry. “We are pleased to have Hookflash bring Open Peer to BlackBerry 10, enabling developers to add rich peer-to-peer communications in their apps, and enhance the customer experience.”
The Open Peer SDK for BlackBerry 10 is the most recent addition to the Open Peer, open source family of real-time P2P communications toolkits. The BlackBerry 10 SDK joins the existing C++ and iOS SDKs already available. Mobile developers creating applications across multiple platforms can now leverage the suite of Open Peer toolkits to deliver real-time P2P communications for all of their applications. The Open Peer SDKs are available in open source and can be found on Github (http://github.com/openpeer/).
Hookflash is a globally distributed software development team building “Open Peer”, new “open” video, voice and messaging specification and software for mobile platforms and web browsers. Open Peer enables important new evolution of communications; Open, for developers and customers to create with. “Over-the-top” via the Internet, where users control their economics and quality of service. “Federated Identity” so users can find and connect without limitations of service provider’s walled gardens and operating systems and “Integrated”, communications as a native function in software and applications. Hookflash founders, lead developers and Advisors previous accomplishments include; creators of the world’s most popular softphones, built audio technology acquired and used in Skype, created technology acquired and open sourced by Google to create WebRTC, and engaged inWebRTC standards development in the IETF and W3C.
Developers can register at (http://hookflash.com/signup) to start using the Open Peer SDK today.
For more information and an Open Peer/WebRTC white paper on please visit Hookflash http://hookflash.com
855-HOOKFLASH (466-5352) ext 1
Hookflash enables real-time social, mobile, and WebRTC communications with “Open Peer” for integration of voice, video, messaging and federated identity into world leading software, enterprise, applications, networks, mobile and computing devices. Hookflash and Open Peer are trademarks of Hookflash Inc. BlackBerry and related trademarks, names and logos are the property of Research In Motion Limited. BlackBerry is not responsible for any third-party products or services. Skype is a trademark of Microsoft. Google is a trademark of Google. Other company and product names may be trademarks of their respective owners.
(full disclosure, I work for Hookflash)
Update 2: To the hundreds/thousands of repetitive spam tweets / twits, “Will WebRTC replace / kill Skype”, the answer is NO!! It will not. WebRTC is using broken Jingle in the browser, it does not support chat and can only make and receive calls., there is no buddy / contact list to speak of etc etc. NO it will not replace Skype. Stop with the spam tweets already, please!
Update: It seems to me that until all the browsers are on board, native clients will be required to make this go. Which is not outside the realm of possibility, considering Google has open sourced the GIPS audio and video engine along with WebRTC.
Something to remember, WebRTC is not RTCWEB! It may sound silly but it’s true. WebRTC is a Google-centric project using Google code etc. RTCWEB is essentially an IETF effort, a working group driving towards open real-time communications on the web. They are not the same, which can be rather confusing.
— Original Post —
Google has been busy it would seem, last night WebRTC appeared to the public for the first time. This has some pretty serious implications for Flash, which was the de-facto technology one had to use to get real-time communications in a browser, that has now been circumvented, at least to a certain degree.
The sessions are not run by a signaling protocol per se, not Jingle, no XMPP, not SIP not anything we have seen before. All the session management looks to be coming from libjingle. Which, to me means Jingle is in the browser.
A few early comments:
1. Where does Google stand on websockets? Google have said they will block it if an exploit emerges.
2. Chrome, Opera & Firefox are the supported browsers. Where does Safari and IE land? My guess is that Microsoft will not be in any hurry to implement this considering their recent Skype acquisition.
3. Web-cam captures from HTM5 has not been ratified, although this is likely not as serious as the former points.
Google has become a powerful force in the lives of many people. It certainly is my window to the World today as I land on the Google search page as soon as I open my eyes in the morning and before I go to bed at night. It has become a symbol and an icon, our “virtual home”, almost synonymous with the Internet, Internet browsing, and … the Cloud! With its presence already established in the consumer world, Google is also making an aggressive foray into the business market with a set of cloud applications.
Since I promised to post several articles on the raging battle between premises-based and hosted/cloud communications, I will dedicate this one to Google. So much has been written about it, that it seems there is nothing left to say. However, two of my colleagues – Subha Rama and Alaa Saayed – put together two very different pieces on Google that provide some unique value. Subha chose to look deeply into Google’s corporate culture and identified several major factors that have driven and will likely continue to drive Google’s success going forward. Alaa, on the other hand, managed to get a hold of Rajen Sheth, Senior Product Manager for Google Apps, and received some first-hand insight into Google’s vision for the enterprise market.
My key takeaway from the two articles is that Google’s success is largely due to the fact that it’s built on the tenets of the Internet and the Internet age. Its product portfolio benefits from the advantages of the web and the cloud; its culture and internal organization also derive their efficiency from applying the innovative spirit and democratic principles of the new age in IT and communications technologies.
Here I provide excerpts from both articles, as well as links to the complete versions on our website.
Subha Rama’s piece is titled: “Google: the IT Iconoclast ”, and it can be found here. According to Subha, Google’s success story is based on two simple tenets: “question established ways and have a healthy disregard for the impossible”. She writes: “As Google grandly outlined in its first SEC filing, its mission was “to organize the world’s information …. and make it universally accessible and useful”. Google believed that the most effective, and ultimately the most profitable, way to accomplish this mission was to put the needs of their users first. This has become more or less the governing principle behind almost all its product innovations.”
Then Subha goes on to ask “What makes Google, well… Google?” She believes that, at Google, “crazy definitely triumphs comfy”. She points to the fact that Google strives to hire only the best talent out there, people who are academically exceptional and are capable of thinking out of the box. You can find neurosurgeons and rocket scientists, in addition to nerdy computer engineers, among Google’s employees. Also, it continues to adhere to its Stanford culture, allowing employees to dedicate 20 percent of their time to work on their pet ideas. This is how products such as Google News, Orkut and Google Images came into being. Subha recognizes that Google employees are constantly challenged to think in new directions and come out with defining ideas. She further notes, however, that Google also focuses on productivity and enforcing deadlines so that it is not drowned in chaos, which can be so typical of highly creative environments.
Further, Subha discusses “the long-tail model”, which forms the foundation of Google’s strategy: “Google strongly believes in the long-tail model, that as the costs of online production and distribution fall, niche products and services can become as economic as mainstream ones. This theory forms the core of a cloud-based service delivery model, which while accommodating a wide variety of applications is not subject to the lowest-common-denominator principle that we apply in a physical environment.” According to Subha, this business model focuses on a large number of products, each targeted at a relatively small audience, thus addressing niche segments, and building customer communities in the process. Further she concludes that the Google business model is in fact based on openness, interoperability, decentralization and accessibility, the pivots around which cloud-based services are built.
Alaa Saayed tackled similar issues of corporate culture and success factors in his recent interview with Rajen Sheth, Senior Product Manager, Google Apps, posted unabridged here. In this interview, Rajen Sheth identified some of Google’s strategic directions as well as some of the key factors impacting Google’s success.
When Alaa asked Sheth if they were finding it difficult to migrate customers to Google Apps, Rajen admitted that it used to be very difficult, but things are rapidly changing. He stated: “Almost every CIO that I talk to is planning a cloud strategy and the value proposition of the cloud is very widely known at this point. For most corporations, now, it seems, it’s a matter of WHEN rather than IF they are going to move to the cloud for a lot of their core services…We are a serious player in most of the conversations we are having about messaging out there.”
Then Alaa asked Rajen about innovation at Google: “Google is well-known for its unwavering commitment to innovation…How is the process of innovation managed at Google”?
Sheth responded as follows: “Having worked in different companies, I could say that Google really operates in a very different way than a lot of organizations out there. It really operates in a way that spurs this innovation. I think there are a few elements to it. The first thing is that we are not afraid to look beyond what an existing space is all about right now, and so if you think about it, in many of the cases where Google has been successful, we’ve reinvented existing spaces … We take an existing space, not thinking about it in terms of how it is today, but what it should be, and how do we make it a brand-new experience”.
“Another big element to it is the notion of cloud computing, and that is actually one of the things that spur innovation. In many cases where you have to build packaged software, you are forced into a stream where you are releasing major updates every two, three or four years. The problem with that is that you have to think three, four-plus years in advance what is going to be the innovation that you want to push, whereas in reality, innovation happens all the time. With the cloud computing paradigm, we have it such that all our applications are centralized and we can update them incrementally, and that actually increases our innovation rate quite dramatically.
Finally, the Google culture definitely spurs innovation. The structure is very, very flat and people are encouraged to think, and to take risks, and think in brand-new areas. In fact, we have this philosophy that we call 70-20-10 and basically what it means, we put 70 percent of our effort in the core of our business, but we put 20 percent of our effort in new areas that are beyond the core business that we think might be fruitful. So we think beyond what is making money right now. Then we put 10 percent of our effort in completely off-the-wall things that may or may not see the light of day, may or may not be a great technology. There are definitely some great examples of technologies that have started out in that bucket and that have become some major areas for Google”.
I believe the discussion above clearly highlights the factors that will make cloud computing and cloud communications successful and will drive continued growth for Google itself. I will still caution, though, that the cloud is not for everyone – both on the supply and the demand side, but that is the topic of another post.
Ok, so VoIP over 3G isn’t quite there, but 4G is not far off.
It would seem that Apple believes 4G is ready for voice and video calling in Korea at least. According to a Korean blog, Korea Telecom will be deploying the iPhone 4G in June of this year. The new device will sport forward and rearward facing (5-megapixel) cameras, an OLED screen and a video calling service.
It occurs to me that with all that is going on in the mobile space, at least one of the providers would have come to market with a data only + VoIP offer. Well, there is still a chance that might happen, in Canada. If we look at the recent spectrum auction it is plain to see the potential players who could bring the Google Nexus One (N1) to market in Canada. It seems that there are only 2 possibilities; DAVE wireless or Wynd Mobile.
Since Wynd has launched there has been no mention of the N1, so maybe it’s DAVE wireless that is bringing the N1 to market in Canada? Will we see a data only offer? One can only hope.
I am an iPhone 3GS user now, but I would jump ship in a heartbeat if I could get decent coverage at a decent price with 3.5/4G + VoIP service of my choice. This seems like such a no-brainer and could seriously disrupt the industry. Let’s get on with it already!
update: FCC sees VoIP as the future.
I don’t want to go on the cart!
Some of you may remember rumblings in the blogosphere, “VoIP died or VoIP is dead” around this time last year. Whatever the context, I think it should be clear by now the VoIP is not dead, nor dying. As a matter of fact, VoIP has never been less dead.
Some may argue that I am taking some of those statements out of context. Semantics. Some said “buddy list” centric calling is the future, hence VoIP is dead, again – semantics.
Call it what you like, VoIP is here to stay, Mobile VoIP is only just getting started.
Give it 5-10 years (not long considering the PSTN has been around for more than 100 years) and everything will be * over IP, including Voice and Video.
I will admit, this is a bit of a silly comparison but the truth is that I have had a few customers (and some analysts) asking for some clarification on the new Google Voice offer and how it may compete with Response Point when coupled with an ITSP. The fact is they really do not compete in any measurable way and they could easily compliment each other.
The obvious major difference is that Response Point is a small business phone system, Google Voice is really a service offering targeted at individuals.
When we combine Response Point with an ITSP (Internet Telephony Service Provider) we start seeing some similarities in the services between the two offers but they are really meant for 2 distinctly different purposes.
Response Point offers an actual premise-based system with a base unit, handsets and features like; auto-receptionist, DID integration, hunt groups, voice mail to email integration etc. All of the things one would expect when purchasing a small business phone system.
Google Voice service is an overlay service on whatever you have today, so if your existing phone system is simply not cutting it, it’s unlikely that Google Voice is going to be able to transform it into the system of your dreams. It’s true that Google Voice will allow you to take advantage of certain features but don’t expect to find a Park, Hold or Transfer or anything fancy like speech recognition.
Google Voice is an inbound-centric service. Most features can only be used with an inbound call, that includes call recording and call joining.
How they play nice together
One could use the Google Voice – simulring feature to call your Response Point phone number and at the same time it could call your mobile.
Google Voice – call recording is a handy feature that is currently not a feature offered in the Response Point system.
Google Voice – voice mail transcriptions is a handy way to receive visual voice mails via email and SMS.
Google Voice – call widgets allow users to put callback widgets on a website. This will allow the visitor to put in their phone number and the system will call them and then it will call your Google Voice number.
Google Voice – SMS is a cool way to compose, accept and manage text messages while maintaining control over the devices associated with that service.
The Google Voice service is only available in the US. Even US subscribers can only forward/simring their Google Voice numbers to other US numbers but that is likely to change to include international countries in the near future.
In theory, the Google Voice call should go wherever the media is sent. Call Routing results may vary depending on the Response Point ITSP you choose.
When calling out, your existing phone number (Caller ID) will be presented to the callee unless you use the dial-out feature, which is (IMHO) a bit of a hassle. This causes some problems as most of us are used to calling people back on the number we last saw from them. Fortunately, many ITSPs (unlike the conventional phone companies) will allow you to change your Caller ID number to match your Google Voice number.
Google Voice does not address LNP (Local Number Portability) at all right now. Which means you can not bring your existing numbers to Google Voice, you have to choose a new number.