Note: in the diagram above, “VoIP”=WebRTC
(…..and of course, in general WebRTC=VoIP, although this might need an entirely separate post)
Earlier this month, Movirtu announced CloudPhone, a “virtual SIM” service based on WebRTC. The white label service is aimed at mobile operators. Using CloudPhone they can allow their customers to make and receive calls using their usual mobile phone number via a laptop, tablet, and potentially any IP-enabled device.
In context of Facebook’s acquisition of WhatsApp and the increased focus on lost revenue implications for mobile operators, it’s pertinent that Movirtu is offering operators a means to tackle the threat of growth in OTT voice services.
In recent interviews CEO Carsten Brinkschulte said he felt WebRTC would mostly be driven by native applications rather than the browser. He also said the CloudPhone development team found WebRTC to be “quite mature” to work with.
WebRTC Insights headed-off to the Movirtu offices in London to learn more about CloudPhone, get the rationale behind Carsten’s comments, and in particular to find out what drove Movirtu to use WebRTC as the VoIP element of a platform where its peer-to-peer capabilities are not a requirement
(Spoiler Alert: it’s strategic!)
Here is a summarised 10 minute interview (recorded 12th Feb 2014)
Carsten Brinkschulte, CEO Movirtu
- The “virtual SIM” concept (0:00)
- CloudPhone Overview (01:08)
- How does CloudPhone makes use of WebRTC? (01:43)
- What drove Movirtu to use WebRTC? (03:40)
- Why is Movirtu’s virtual SIM platform different? (05:38)
- Movirtu’s experience of developing with WebRTC (06:40)
- WebRTC adoption driven by native applications? (07:38)
- What next for Movirtu? (09:42)