It seems like the event last week in San Francisco, hosted by TMCnet, is now the main event for WebRTC. It doesn’t matter how many people attended it or what topics where covered. All that matters is the fact that every other company dealing with WebRTC – issued a press release or a major announcement of some kind.

I decided to bunch up all of the announcements (in no specific order) – hope I didn’t miss anyone…

Thrupoint

The way I read this – this is a gateway initiative for WebRTC. If you are looking to connect between WebRTC and SIP or PSTN and don’t want to develop the gateway on your own, then Thrupoint provides such a hosted gateway “somewhere in the internet”, which you can access through the APIs they provide.

Acme Packet

Not an easy feat, but one that I must question – why? While people have mobile video telephony on their phones (at least those with Android devices and Symbian ones), it never really caught on in terms of usage.

That said, this is no easy feat – I’ve developed and managed a 3G-324M stack in my distant past, so I know how much work that takes.

UPDATE: The above changes were made due to a comment from Acme Packet that can be seen below I stand corrected.

Twelephone

I’ve interviewed Twelephone here already. It seems Chris was busy since then rewriting the whole site from scratch. Here’s how the new service looks like:

This is a work in progress, and the way it is being designed and implemented, it looks like something Chris wants Twitter to acquire.

AnyMeeting

As I wasn’t in the conference, I can’t even tell if AnyMeeting was there. I haven’t heard from them before in the context of WebRTC, but they did announce during the conference week itself a hackathon they are planning for WebRTC.

This is one way of announcing upcoming support of a new technology to a product.

Comments

Acme Packet’s announcement was really about providing gateway functionality between WebRTC and IMS. We demonstrated this capability at a major mobile provider and make calls between Chrome to their multi-vendor IMS core (that includes our SBCs) and various subscriber units on their network using 3G voice. It had nothing to do with 3G-324M.

WebRTC gateway functionality is not all that novel, but we believe this is the first time this functionality has been demonstrated in a multi-vendor context (i.e. we didn’t make the browser and were interacting with elements from several vendors in the IMS core).