VoIP: Verizon dancing with Google

Some interesting news. Verizon offering integrated VoIP with Google Apps.

From the story.

Verizon has launched a new cloud phone service for small and midsize businesses (SMBs) called Virtual Communications Express. The voice-over-Internet protocol (VoIP) service integrates with Google Apps to offer click-to-call functionality from email, calendar, and chat.

Observation 1: 

Now Google Apps, as we know, are web-based.

It will be interesting to find out about implementation of the Virtual Communications Express.

VCE needs not be based on (prereleases of) RTCWeb necessarily, but let's put it this way: would not be surprised if it was.

Observation 2:

Competitively, it appears that this is a pre-emptive move from Verizon. Better for Verizon to offer its own VoIP, rather than Google offering Gtalk (which it will of course do, sooner or later). From the story:

The devil's advocate--or, better yet, the truly bootstrapped small business--might ask: Why not just use Skype or Google Talk alongside Google Apps?

Observation 3:

It is interesting to note that Verizon value-add here is customer service.

Makes sense. I recently heard someone joke "has anyone heard of Google customer service number"...

Feature comparisons aside, Verizon apparently intends to flex its customer support muscle here. "We've found in the SMB space it's really important that there be a high touch, high customer care installation," Dalrymple said, adding that an "implementation coordinator" will be assigned to each new account to oversee the process from sale to deployment.

Observation 4:

Not surprisingly, it seems that this service has some very evolutionary elements from customer point of view. Traditional telco strongholds ie. PSTN-connectivity and numbering important:

Deployment takes seven days, according to Dalrymple; if you're porting over existing numbers, that will take about twice as long, but Verizon will issue temporary numbers in the interim.

Germany NGN Interconnection...but where is IMS?

Interconnecting VoIP networks I thought was the job of IMS and related peering setup (IPX?).
Now it seems that XConnect is doing it in a partnership. And the XConnect I know has emerged from Internet VoIP technologies, connecting the Internet VoIP islands.
Definitely an interesting case to be followed. If we see more of these, it will change the world.


From the story:
The DE-CIX NGN service resolves these challenges by offering national and international network operators a secure hub for NGN interconnection, with benefits including:

• Multilateral NGN interconnection to multiple networks, by-passing the PSTN, and reducing the need to create and manage numerous commercially and technically onerous bilateral IP interconnects
• Improved Voice quality and support for higher-value multimedia services
• Number portability corrected routing via a Centralised Number Portability database (CDB) to ensure accurate call routing
• Policy control to define and manage the technical terms of each interconnection and support for different settlement models between operators
• Reduction of capital and operating expenses, transit charges, and resource requirements for creating and managing interconnects, from interoperability testing to implementation

WebRTC could be huge...but where is MS/Skype?

Today, September 5th, Nokia launched two new Windows8-handsets.
Instead of focusing on the devices themselves (which deservedly are getting attention elsewhere!) let's talk of an emerging Internet technology standard that could fundamentally change how we communicate: WebRTC.

Basically, WebRTC could revolutionise how we communicate.
Reason is that it will enable Web developers to include voice and video communications to the web page development.
Think how you retrieve information from the Web, from any www-site. The promise of WebRTC is that communications will become as friction-free.
Think of a hotel chain. They can embed a WebRTC call-to link in their web pages and enable consumers to talk to their agents.
No need to download a VoIP client, just do it from any browser.

Until now, the VoIP providers have in reality been isolated islands, but communications moving to the browser that could change.
Let's remember, VoIP-in-browser as such is a known solution, but here we are talking of a standard, meaning the user needs not install proprietary plugins.
While this sounds elementary, the VoIP and Web industry could change with the new transparency.

But we are not quite there yet. Summer was an interesting one for WebRTC.
The good news was Google promoting WebRTC in its IO conference.
Clearly, Google and the browser vendors are leading the way for WebRTC.

But what happened then?
Microsoft (remember, MS acquired Skype some time ago...) entered the stage.

They made a comprehensive proposal on how they see WebRTC.
The concern is that if MS has its way, the WebRTC will either change course or diverge.

The MS proposal could change radically the concept of WebRTC.
One issue is the need for lower level APIs they see. This would in turn require more functionality at javascript layer, meaning burden to the developers.

Also, it is interesting to see that MS wants IETF to take network conditions into consideration. That is what the mobile industry has argued for, while IETF has always developed their solutions to "generic IP networks", assuming their performance will be adequate.
Now the word in the industry is that MS wants to slow WebRTC down, simply because Skype is the dominant VoIP network, and a closed one. This is of course very logical. Meanwhile, Google (and browser vendors like Mozilla Firefox) want to move on.
So, the game is on.
But, Google Chrome supports WebRTC basic functionality early version today, and seems others will follow.

Then, how does all this impact Nokia? Well, many Nokia devices support wifi and LTE is around the corner. LTE is an excellent bitpipe for VoIP.
Question for Nokia is: will MS/Skype be left off the WebRTC train?

Tele2 of Sweden...challenging GSMA with VoIP?

Telcos are more and more coming out with VoIP apps of their own.
Tele2 has done exactly that, their announcement today.
Unluckily in Swedish only.

Key points translated:
- available via Apps Store and Google Play
- they call this "traveler's app", key benefit being able to make and receive calls over wifi when traveling

But they may have more in the pipeline, seems RCSLabs is working for Tele2 here?
This COULD mean Web based VoIP-client for Tele2?
RCSlabs seems to be promoting a SIP based client in their webpages.

So Tele2 announced a rather simple solution now, but a step forward nonetheless.

Korean operators to charge more for VoIP...

The war against innovative IP Communications and VoIP apps is picking up.
Now Korean operators have announced they will be charging more for VoIP.

"This will set a precedent for coming apps such as FaceTime, where SKT and KT already said they will apply the same pricing policy as with local apps, and this can clash with global players like Apple and Google," said Jiho Park, an activist with the Citizens' Coalition for Economic Justice.

This is in a sense surprising to hear. Some questions:
- how does this move map to Korean industry policy? One would think net neutrality would promote the chances of Samsung and LG who want to sell endpoints, rather than be at the mercy of megaoperators
- or is this just that? This way Samsung the infra vendor is learning to play by the new rules?

In general, it is easy to note that this scheme will create a lot of confusion. Think of an iPhone Facetime user who moves between free wifi and 4G.
4G being flat rate would be the easy way to go, but now he has to be aware of different pricing schemes.

Secondly, VoIP is quickly becoming "just another media component", as it should be.
How then to charge apps combining various types of media?
I guess "multimedia" as such is not a new topic...for folks outside telcos...

Browsers starting to support WebRTC

Opera12 has it, WebRTC support.

Opera 12 has a lot to offer Web developers. The new version includes preliminary support for WebRTC, an emerging standard that is being drafted by the W3C Web Real-Time Communications Working Group. WebRTC will eventually enable standards-based audio and video chat in Web applications.

Also, other browsers like Chrome seem to have early support.
This is excellent news as voice and video chat will greatly enhance the Web apps.

Skype ads - would you want to watch them?

Skype has now introduced ads to 1-1 voice calls.

The ads will be visual for users with no Skype credit. Wonder how much clicks they will generate, but cannot complain of their self-confidence:

While on a 1:1 audio call, users will see content that could spark additional topics of conversation that are relevant to Skype users and highlight unique and local brand experiences. So, you should think of Conversation Ads as a way for Skype to generate fun interactivity between your circle of friends and family and the brands you care about.


Additional topics of conversation for people in the call? Hey, how about adding voice-recognition? Talk about thinking of buying a new car, and then, out of nowhere, just suddenly an ad appears...