In the blog I posted on Tuesday about Using BlueVia Voice directly on calls between 2 phones, I think the key point to reinforce is that as BlueVia is an application layer built on top of the mobile network, it is actually possible to use that network in ways that our competitors cannot. The product demonstrated, see the video above, is not the key point. The key point is that it is possible to do enact any call functionality, supported by BlueVia Voice, on any outbound or inbound call to a mobile phone.
That mobile simply needs an Intelligent Network trigger set at the network level, to allow calls to be forwarded to an application server. The is the first key differentiator that carriers can have over OTT players, i.e. between BlueVia Voice and other Over The Top (OTT) Voice API providers. OTT Voice API providers have no control over the network, they cannot add in call functionality without the use of a Direct Inward Dialling (DID) number.
This means that for a Customer to engage with a service, build on top of an OTT providers Voice API, they must dial a DID, as opposed to directly dialling their friends number. The BlueVia Voice demo above shows a call being made directly between two mobile phones, not through a DID, and BlueVia Voice commands then being played on that call. This is the power of a telco being able to provide access to their own voice services to developers. Telcos have a unique opportunity to provide differentiated Voice API services - should they choose to.
Don't dwell on the thought that free calls based on advertising didn't work in the UK, as the product demo above shows. Remember there are still many billion mobile subscribers outside of North America and Europe who might just be interested ;-). But that is not the point.
Cheers
m
No comments:
Post a Comment