VoIP Gateways Article

The adoption and influence of WebRTC continues to expand. Among the latest companies to employ this technology is Vapour Cloud. The U.K. tech firm is using it to support a new voice communication application called Höllr.

Höllr is a cloud-based offering that supports lower cost calling. It also features call redirection, CRM integration, one-click disaster recovery, recording, and reporting.

This offering is delivered over Vapour’s secure U.K. network backbone. The application is being used by such Vapour Cloud clients as Incident Support Group, Pure Technology Group, and Wainwright & Co.

“Voice communications is changing, in terms of how we consume it, the expectations we place upon it and the potential it has to transform our businesses,” says Vapour Cloud CEO Tim Mercer. “Consumer tech brands have really capitalized on this, and the use of WebRTC has been inspiring in this respect. But in the commercial market, organizations have continued to be plagued by the limitations of solutions like VoIP, which is actually rich in potential, but has been delivered by traditional suppliers that don’t truly understand the technology involved. As a result, products such as Skype (News - Alert) (News - Alert) – which could have revolutionized how companies communicated – have been met with little but frustration in the corporate environment.”

Just prior to the Höllr launch, Vapour Cloud unveiled a solution called Dfendr. That’s a secure cloud platform that enables users to recover business-critical data.

Vapour Cloud has received £4 million in investments to date, including £1 million from Seneca Partners in June. The Seneca funding will help provide fuel for Vapour Cloud’s national expansion, for which it’s growing its team by 20 percent.

In another recent noteworthy development on the WebRTC front, we learned in June that there is now WebRTC iOS and WebRTC Safari support on Apple (News - Alert) devices. Erik Lagerway (News - Alert) wrote: “Until now, in order for WebRTC to work on iOS, we were relegated to wrapping WebRTC code in Objective-C and Swift (News - Alert) (News - Alert), in our native iOS apps. Basically, we had to take the Chrome code and build an app that was sent to the app store for approval and wait in line, like all the other chumps (yours truly included). Conversely, on Android (News - Alert) (News - Alert) we could run much of that same code from our desktop Chrome apps, on the Android device as well, within reason of course. Now that Safari and Chrome are shipping compatible WebRTC on mobile, we get to reuse the same code, right!? Well, mostly, they are different code bases, after all.”