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
We wanted to get this initial informational document out right away so everyone that has any interest would be able to review the concepts and comment before we get too far along on the actual API.
“No SDP Offer/Answer” is a concept that has been bantered about for some time. It continues to rear its ugly head within the IETF and W3C Working Groups. There is evidence that some major browser vendors will not back the current SDP O/A methodology at all, but some of us continue to pin our hopes and dreams on SDP O/A nonetheless.
We are told by the developers we need something that will not only pass muster with them but will also be something that can be extended and innovated upon, uninhibited by large browser vendors or any vendor for that matter.
According to many, real adoption of WebRTC will not happen if we continue to force everyone to use this SDP Offer/Answer methodology. It is clearly blocking our way forward and the amount of specification documentation remaining needed for the browser vendors to produce a compatible SDP based WebRTC engine in a browser is much more daunting than most are willing to admit.
It’s time for a change.
What does that mean? It means we need to rewrite a portion of the current WebRTC specification and WebRTC API, which also means that many of the demo apps running out there will need some level of modification. Which is O.K. It’s better to break a few demo apps now than to proceed knowing there is a material flaw in the design, precluding the rest of the web from playing along and causing untold pain in future development.
Long live WebRTC.
Imagine a new secure P2P (Skype like) offer that also supported SIP in the client. You could use the client software on it’s own (just like Skype) or attach it to just about any VoIP service or phone system for free.
Does it make sense for consumers?
Does it make sense for business users?
Is there room in the market?
Would you use it?
Martyn Davies chimes in…
I would use it, but as a telecom industry insider, I know that I’m not the average business user or consumer. As to whether there is room in the market, I think that depends a lot on what Microsoft do with Skype now that they own it. From a business point-of-view, their efforts are focused around OCS/Lync (and software licenses), so Skype there is not adding to their central proposition. Skype has a lot of users, but produces very little revenue, since the majority just use the free services. As a Skype competitor you would have the same problems getting to the cash.
Skype was really the first company to take VoIP and make it completely trivial to install and use. To do that, they had to take some liberties and deviate from standards (like SIP), so that they could add the magic that made it work from behind firewalls, add security and self-configuration, and integrate video so seamlessly. Like Facebook, once it is clearly the biggest of its kind of services, it becomes the community that everyone must join. I can’t see that another Skype-alike has a way in, unless Microsoft significantly change the rules now.
Jazinga and Freetalk have combined efforts and the result is a Skype enabled SMB phone system called Freetalk Connect.
The press release:
FREETALK Partners With Jazinga To Create FREETALK® Connect
Companies Collaborate On Skype-enabled Small Business Communication System
Featuring Set Up In Less Than 15 Minutes
MIAMI, January 20, 2010 — As the result of a new partnership announced today at ITEXPO East 2010, FREETALK and Jazinga have created the FREETALK® Connect, a full-featured unified communications system that is the first to feature Skype for SIP and Skype for Asterisk functionality.
FREETALK and Jazinga collaborated in designing the FREETALK Connect, featuring a do-it-yourself (DIY) technology approach that can be configured in less than 15 minutes, enabling users who are not tech savvy to use it without formal training. This new class of DIY communications system allows anyone with basic knowledge of computers to install and maintain the office phone system. SIP, Skype and traditional PSTN phones can be plugged into the network, and the FREETALK Connect auto-detects and configures them. An onscreen wizard guides the user through setup. Adding users and administering the system after install is equally simple.
Further distinguishing the FREETALK Connect is its intelligent routing capabilities. Incoming Skype calls, as well as SIP, PSTN and IAX2 calls, can be routed to any local or remote Skype user, SIP, analog or mobile phone. Additionally, the FREETALK Connect enables users to set up “Find Me, Follow Me” features, and provides a unified mail box that consolidates messages from voice mail and email into one mailbox.
Some of the key features from the Jazinga platform found in the FREETALK Connect include:
Callback / Dial-around
Access to Skype Buddy lists
Auto Attendant / IVR
Music on Hold
The FREETALK Connect also has an easily configured and updated:
Managing routes to users, telephone services, and applications
Providing SIP/Skype telephone service management
Router management (networking, port forwarding, DNS, DHCP)
“Jazinga’s products consistently ensure call integrity by integrating quality of service and prioritizing voice traffic on the network into an affordable, simple product,” said In Store Solutions COO Craig Smith. “There was no question that FREETALK wanted to partner with Jazinga to develop the FREETALK Connect, because it continues our goal of working with the best providers to distribute outstanding products around the world.”
“FREETALK Connect is designed for small businesses with between 2 and 49 users, an undersold market that desperately needs UC functionality,” said Randy Busch, CEO of Jazinga Inc. “As a result of our partnership with In Store Solutions, the telecom technology playing field is much more level between larger enterprises and their smaller competitors.”
The the FREETALK Connect is marketed through Skype Shop, which is operated by In Store Solutions. The unit initially will be available to registered U.S. Skype users beginning in March.
For more information about FREETALK Connect PBX or to order a unit, visit
FREETALK is a product innovation catalyst – identifying market gaps and working with its global partners to design, manufacture and quickly bring to market products that disrupt traditional categories. Leveraging untapped market opportunities, FREETALK products are designed to be environmentally friendly, sold online and delivered globally at aggressive price-points. Always at the forefront of innovation, FREETALK is known for creating synergistic products that add unique value to its partners’ branded points-of-sale.
Jazinga Inc. develops communications products for small businesses and homes. The Jazinga system provides enterprise telephony and data functionality for this market, but at a fraction of the cost and without the setup complexity of an enterprise-class IP PBX. Jazinga Inc. is privately held and headquartered in Toronto, Canada. Additional information is available at http://www.jazinga.com.
Sue Huss, for In Store Solutions
Jazinga came to market a while back with a Asterisk appliance that is not much different than other you would find in the Asterisk market today. Skype recently announced their Skype SIP Trunking capability which is helping Skype become more open standards compliant, paving the way for deals like this one.
Since I have not tested the system myself I can only speculate that it is not huge departure from other Asterisk systems, which are not trivial to set up. Let’s hope they did their homework and come to market (March) with something that is much less technical and more end-user friendly, like Response Point.. was.
One thing that I find interesting is that it will be sold via the Skype store to US registered Skype users. If you were wondering what the connection is between Freetalk and Skype; the creators of Freetalk are also the curators of the Skype store. Ya, you heard me right. The company that created Freetalk (In Store Solutions) operates the Skype store. Which makes one wonder if there is overlapping ownership between Skype and In Store Solutions.
Something else that I find interesting, and not just because I am one of the founders of Xten/Counterpath, is how this announcement relates the recent announcement of the Asterisk/Digium softphone from Counterpath. Which may be why In Store Solutions decided not to leverage the Digium or Asterisk brand in this release, maybe they see the new Asterisk Bria softphone as a competitor in this instance?
I expect this will not be the last Asterisk-based phone system to incorporate Skype functionality this year, but it would seem as though they are the first, congrats to fellow Canadians at Jazinga.
Looking for a contract PHP (or RoR) rock star for dev lead on exciting new (funded) VoIP-centric web app. I expect it will be no more than 6 weeks work. Email firstname.lastname@example.org for info.
It’s only a few months after Microsoft finally put its Response Point (RP) System in the spotlight with the release of SP2 and John Frederiksen’s keynote speech at ITEXPO East in February 2009, and the wings of the entrepreneurial RP team seem to have been cut. It is clear that the latest wave of Microsoft lay-offs has impacted the RP team and some cryptic statements on the official Response Point Team Blog indicate that Microsoft wishes “to take a good look at the next version of Response Point and ensure it addresses the needs of Small Businesses.”
I contacted John Frederiksen, General Manager for Response Point at Microsoft, and he responded to my concerns with the following somewhat re-assuring comments:
The company will continue to support Response Point version 1.0.
We will continue to support our current OEMs, Service Providers and resellers that are selling Response Point version 1.0. Customers will continue to be supported through their OEMs.
We will also continue to promote the product online and spotlight compatible 3rd party services and add-on products.
The team is evaluating the strategy for the next version of the product and will continue to investigate the opportunity in the small business market.
The Response Point team has not been moved to another division.
Two years ago, when RP was still in beta trials, I thought it offered some interesting features and capabilities and I believed Microsoft was going to leverage this innovative solution to aggressively pursue the SMB customer segment as another entry point (vis-à-vis OCS) into the telephony market in general (see my article here). I did wonder if there was going to be some conflict of interest between OCS and RP and the respective teams, but ruled out that possibility assuming Microsoft had sufficient resources to support both lines of business as they seem to serve fairly distinct market segments. Today, the economic recession seems to be forcing Microsoft, not unlike other IT and communication vendors, to make tough choices. I am still unsure if the decision was made on the basis of comparing the respective potentials of OCS and RP, but RP has definitely fallen prey to Microsoft’s efforts to cut down expenses where short-term revenue and profit prospects are less certain.
Response Point Value and Market Positioning
In a more recent article discussing the release of SP2, I stated my belief that Response Point is uniquely positioned because of it features including the speech recognition capability and the Magic Blue Button (voice-controlled auto attendant and dialing), but mostly because of its ease of installation, use and management. It is as close as it gets to an affordable, plug-and-play telephony solution for small businesses, and thus in a category of its own, since most other small-business systems are neither as simple to use nor as inexpensive. Generally, it is hard to find an IP telephony platform that can provide a cost-effective communication solution for a business of less than 20 users, or a larger business with geographically dispersed sites of that size. SP2 offered some valuable enhancements such as analog phone support, intercom, VPN and multi-subnet support, an after-hours receptionist setting and more robust audio. The anticipated release of version 2.0 is supposed to make it an even more robust business-class solution that competes head-to-head with platforms offered by traditional telephony vendors such as Alcatel-Lucent, Avaya, Cisco, Nortel and Siemens.
However, what I believed was going to be Microsoft’s (not so) secret weapon in the battle for the small-business space was its extensive channel of VARs, resellers, specialists, etc. The traditional vendors use channels that have mastered the skill of marketing, implementing and managing more complex solution for medium and large businesses. Very much like the vendors themselves, these channel partners have a vested interest in pursuing larger implementations that produce greater margins and help them scale and grow more rapidly. Response Point, on the other hand, is well positioned to enable multiple Microsoft specialists and consultants to add a new revenue stream to their business and offer a more complete portfolio of business solutions to their small business customers. Response Point customers have indicated that they appreciate the features and lower cost of the solution, but their trust in Microsoft’s continued support and extensive channels represents a major factor in their decision to select Response Point versus open-source or some other less mainstream solutions. Yet Microsoft is currently failing to re-assure its channel by sharing a clear vision for the future of the Response Point system.
I talked to several RP resellers about three months ago and I was really impressed by the positive feedback. They seemed to believe that the features, though not on par with those offered by traditional vendors, were sufficient for most of their clients. A phrase that frequently came up in partners’ comments was: “This time they got it right from the start. It just works.” Also, partners appreciated the continued interaction with Microsoft allowing them to contribute to the development and addition of new capabilities that would further enhance the value of the RP system for small businesses. They were eagerly awaiting release 2.0 as the more compelling solution that would indeed enable them to compete successfully in their target market. My conversations with resellers as well as the blog entries I have read on various web sites dedicated to Response Point and Microsoft’s eco-system of partners indicate a very strong confidence in Microsoft’s ability to deliver and its commitment to this product line.
The Channel Awaits Microsoft’s Official Statement
As the rumors spread about the fate of the RP team and Microsoft delays making an official statement on the future of this products, disappointment and doubt are beginning to creep in among the partner ranks. For some of these small outfits RP had just opened up opportunities that now seem to be closing without proper notice. Not only the income, but also the reputation of these specialists and consultants is on the line since they have promised their customers a certain roadmap of product viability and evolution.
Further, partners are now having second thoughts about the quality of the Response Point system. They see more clearly some of its disadvantages in light of Microsoft’s hesitation to continue investing in further product development. Most of them continue to believe that, given continued development, this product is right for them and for their customers. Yet others are quickly beginning to look for competitive products to add to their portfolio in order to be able to sustain their competitive position in the small business communication space.
Finally, partners are now questioning the nature of their relationship with Microsoft – is Microsoft really committed to supporting its partner network or are they after quick and guaranteed profits only?
Speculations Abound at Times of Uncertainty
I saw speculations about the possibility of Microsoft integrating RP with OCS. I don’t see why they would want to do that. Microsoft can use certain elements of RP for call control with OCS if needed, but OCS is not a suitable solution for small businesses. If a business needs inexpensive telephony and/or IM client, they have other options. The value of OCS and unified communications is in their ability to integrate multiple applications from IM to voice to UM to conferencing, but in order to deploy all these capabilities, a business will need several servers with a significant price tag.
Others are speculating that Microsoft is planning to focus most of its efforts in the communication space on cloud computing and communications as a service (CaaS). I believe that Software as a Service (SaaS) and CaaS have some potential for delivering business applications and communications to SMBs. Similar to existing hosted telephony services, it alleviates all implementation and management hassles for small businesses typically lacking in-house technical expertise. However, SOHOs and very small businesses are likely to continue to prefer the least expensive consumer solutions. On the other hand, small businesses at the upper end of the range – 20 to 100 users – may actually benefit from inexpensive premise-based solutions such as Response Point.
In my opinion, Microsoft should certainly pursue profitable opportunities as that would eventually be best for both itself and its partners. I do believe, however, that Response Point has a good market potential. As I mentioned earlier, it is competing against traditional vendor platforms, many of which are just too expensive and difficult to manage for small businesses of up to 50 users. Hosted IP telephony has failed to gain much traction throughout its nearly decade-long existence, although it is touted to be a most suitable alternative for this particular market segment. Open-source telephony, on the other hand, is becoming a more viable option, especially with Digium and others focusing on developing a channel, something that was considered one of their major weaknesses so far. Consumer vendors such as Google and Skype are also vying for a piece of the SOHO and small business market and are likely to eventually gain some penetration. However, Response Point has the advantage of having been developed as a business system from the start and the channel has already been trained.
Overall, I believe that Response Point is a viable solution for the small business market. As with any technology, however, its success is largely dependent on the vendor’s execution plan, and I’ll repeat myself – “It’s all about channels”. Given the right marketing efforts, it will sell, and given the right vendor and channel support – it will thrive; without those elements, it is not going to make it on its own. The small business market continues to be under-penetrated and to offer tremendous opportunities. While the competition seems to be intensifying in this market segment, the various solutions seem to offer some distinct advantages and disadvantages thus basically catering to slightly different sub-segments. As some of Microsoft’s partners seem to believe, more extensive marketing efforts may be needed (TV commercials, end-user webinars, etc.) with a strong marketing message that clearly identifies the benefits of Response Point in order for Microsoft and its partners to be able to keep Response Point sales afloat in this challenging economy.
Tom did his homework and found that Cisco is using OpenSER as a SIP proxy for their Linksys One service node. This is very interesting considering the original SIP Express Router (SER) was used widely as a test proxy for various applications, I seem to remember one in particular, although who knows what it’s running on now.
I know that colleague Adrian Georgescu over at AG Projects has leveraged OpenSER for some very interesting projects they are working on.
Good to see OpenSER making strides with the larger vendors, although Cisco is no stranger to that. Some of you may remember a little open source shop named Vovida that got snapped up by Cisco some years ago.