Standard Jingle on Google

After many year after its creation and early adoption, Google finally announced the switch from their own Jingle variant to the Standard Jingle Version created, approved and maintained by XMPP Foundation.
This comes in the right moment after the previously GIPS Media Company now owned by Google itself, announced the OpenSource WebRTC Project. Which intends to provide multimedia and realtime communication capabilities to Browser like Firefox, Chrome, Opera, etc...

Google intend to bring rich communication also to their other browser products like Orkut, iGoogle and even adSense with Ads that could place direct calls to the announcers.

This will enabled direct compatibility to the already know Jingle Clients Jitsi, OneTeam, Pidgin and others. The amplifier of this announcement is that soon we may be seeing native Jingle Support on Android OS, which will make a great and powerful opposition to Skype Mobile Market.

Nimbuzz was the very first Mobile Company to runs their entirely Voice Services over Jingle since 2007. They would have immediate benefit if they were allowing XMPP Federation, which currently is blocked. For now they support GTalk Calls but requires the user to have a Google account registered (which is not a big problem, but not as handy as it could be).

Hopefully Jingle Nodes will also be adopted soon as the default mechanism for Relay Sharing Discovering for Jingle. Stay tuned for more good news. 

Yet about Google Call

Due the amount of comments and emails received, I will reply to them in a post.

• How does the Authentication works?
• That is one key reason for using their established XMPP channel for placing the calls. The user is already authenticated in GMail and Google Talk. So the request is sent through the authenticated XMPP network to their XMPP Component responsible to offer SIP Gateway. From that moment one the component will convert the Jingle Signaling from the Google Talk to SIP and use your Google credentials to authenticate in their SIP Services.
• Which Codec is being used?
• G711 is the only one that I could trace, although the Plug-In indeed support iLBC and others. The reason behind it, is that G711 is a supported codec in most all PSTN, Media Gateway or other interconnection with Legacy Telecom. Alternatives would be transcode, which is out of the question due CPU load, drop of quality etc... Or use proprietary G729 which requires the payment of extremely high royalties per client/channel.
• Will they succeed in making money?
• Google "Cows" may produce some "milk", but I doubt Google consider that as an important income resource. The feature is much more related with PR and positioning about THE REALTIME company, than anything else. Having most of what Skype does in their closed client, in a browser and using open technologies is a direct confront to Skype's model. IMHO, Phone Numbers are dead, and will be ripped out of the market in less than 5 years from now. 
• Are the API for Audio/Video Streaming available for third-party usage?
• That I could not figure out. Tried document or formal info from Google without success. May someone could assist us on that matter with some Javascript reverse engineering, or a Google guy, that wanna share that with us. Please let us know :)
•  Is there any client supporting it already?
• No, it is not yet available in any client that I'm aware. But I bet that as soon Google appears with a formal specification and documentation, that will happen very very fast.

Thanks for all the questions, I hope I have answered most of it.

Google Call on GMail

Google Call, as I mentioned before in a previous post, was added as a Calling feature direct to the browser.
I hope this take down Skype monopoly built on top of a closed and proprietary fuzzyware.

Google now has the most powerful position on VoIP world and soon will take down Skype eagerness for a proprietary/closed network.

Google's solution is built on top of a plugin, which is embedded on new Chrome and also easy to install on other browsers. They are using Standard XMPP and Jingle at Client Level with SIP in the backend, Streaming RTP with Standard Codecs directly from the browser. ( NO CRAP FLASH TRANSCODE USED! )

Google Call offer several advantages:

• Browser Based
• Open, so they can make use of third-party clients for it ( Do you need more reasons??? )
• VoIP everywhere, browser or in your favorite Client. Solid Model.

Hope Nimbuzz adds support for it soon!

You can try it here: http://www.google.com/chat/voice/


As you asked how it works:
Google is making use of recent acquired GIPS Company Technology to add native RTP streaming directly to the browser.
For PSTN Termination, Google is using Gizmo5, together with previous Google Voice partners.
I promise to post deeper technical information like protocol details and Codec later on.

GMail VoIP Coming Soon

Sooner than we though GMail will integrate VoIP services. This happens right after GIPS acquisition, and quite way too late after Gizmo5 acquisition.
Gizmo5 had for a long long time such widget but was using several layers of software from server side transcode, flash capture and an extra plugin.
I really hope they are thinking hard to have their widget based on embedded browser features. As it would be quite simple to embed a real VoIP(RTP/Codec) API in Google Chrome at least. That will really move the perspective on Broswer based VoIP to a new level!

The whole market will also appreciate if they make such API as open as possible so other could also create their browser based VoIP Clients.
We would even be pleasured if such API to be available also on Android Devices.

Google don't disappoint us.

Google Acquires GIPS

Today was announce the conclusion of the buying process of GIPS by Google.
What does that mean?

Here are some hints:

• HTML5 predicts lots of extra features that needs to be provided by the browser. Which means that they are really looking forward to remove the crappy dependency of Adobe Flash, which currently is required for 99% of all Browser Based Voice Over IP Applications. Which besides the Adobe Plugin requirement, also requires traffic and negotiation passing through Adobe Media Servers... (Adobe shall get what they deserved for their manipulation, never supporting Standard RTP Streams)
• GIPS was the best in the market "Quality Wise". They always offered top quality codecs and APIs to main Real Time Communication Companies from Desktop Skype to Mobile Nimbuzz.
• Goggle already used not only GIPS software but also GIPS iLBC codec. Which is a great quality for low bandwidth Internet Communication with extra awesome packet loss support.

In resume GIPS was a very great choice!

Semi-Fiction Fact:

Google looked for some solution and buying the whole company was the easiest and quickest way to get it done...

Why Skype UI OpenSource?

When legacy proprietary companies start all of a sudden OpenSourcing their software, a lot of questions are raised. Of course they have their own explanations for the facts, although frequently are not the whole true about the fact.
Since Skype announced their OpenSource UI, I received some email asking why would that happen and what are the reasons behind the curtains.
Here is a personal explanation based on some facts:

Background Story:

• Skype started their business in a market almost empty of competition. VoIP indeed existed, but was NOT directed to end users, neither mass market.
• OpenSource would not make sense as it usually (for big companies) takes way more time and money to build solutions on top of standards then creating your own black box with the solutions of your own problems and challenges inside. And the lack of demand for a standard format was about 99%.
• Another reason is the "secret" factor, as the first ones, they have to create all the buzz around their holly grail and of course ensure the domination.
• That is why(among other reasons) Skype made their business on top of proprietary routing algorithms and proprietary protocols and encryption.

Early VoIP Market:

• In the other hand for very small VoIP services the picture is different as they started on top of OpenSource platforms, even in a time that most of them were experimental. The reason is, the target market was massively smaller than Skype targets. And of course the money to invest was way smaller as well.
• SIP adoption was adopted in almost 99% of the rising small providers that started popping up everywhere in the world.
• Interesting fact is that most pioneer small VoIP providers started with virtual PBX system, not even SIP routers and big platforms. Basically "grow on demand" strategy was adopted as well.

Current VoIP Market Snapshot:

• VoIP is way more spread in the world since Skype started the massification. We have large number of companies building equipments, client soft-phones, VoIP platforms etc...
• We have a ridiculous huge number of VoIP providers which anther ridiculous range of different prices and quality.
• SIP is the main driver for major market. It is used on landlines in Europe and US, it is massively used in company PBX and telephony of big companies. Which are the main source of PAYED VoIP services.
• Skype is smaller in amount of users and revenue, if compared to all SIP Providers together.
• Google acquires Gizmo5 a medium VoIP provider fully operated over SIP. Yes it has direct relation.

Consequences to Skype:

• Skype ubiquity is restricted by their Desktop Client or their very limited IPhone client.
• Skype still growing the amount of Desktop users. But the amount of paying users is still and tends to get lower.
• Skype interoperability is null, as it is based on proprietary system and specifications.
• Competition makes more money and the migration from old Skype users to new VoIP alternatives is big. As educated users knows now how to change and why to change to cheaper and flexible services.
• We have more SIP enabled equipment and computers than Desktops with Skype client installed.

Skype Strategy Turn:

• OpenSource their SILK codec as already mentioned in this blog.
• Open SIP Gateway for Business Users. In order to start competing in a very profitable market slice.
• Bought the patent of their VoIP routing solutions. In order to prepare for an interoperability round.
• Aim for alternative and relatively "virgin" markets like mobile, Linux, netbooks etc:
• Release more usable mobile clients.
• OpenSource as much as possible for Linux as current client is really crap and also Linux users in general don't use closed source applications.

The Reason in Resume:
Skype wants its ubiquity and revenue back, and for that they are investing huge resources in Openness and Standardization, as it is what their market needs and demands nowadays.

In a mash-able hyper-connected world, who is closed and not interoperable will fade.

URL Shortener XMPP Bot

zaptin@xmppguru.appspotchat.com

XMPP Provides easy and clean ways to build XMPP Bots, as I showed on the previous post, we can use Google AppEngine to create 24h online, zero-maintenance Bots. Yes, I don't need to host this. Google is doing the job for now, for free, let it be.

You can use the xmppguru extension to Short URL simply add it to your GTalk's / Jabber Contacts: zaptin@xmppguru.appspotchat.com

Examples of general usage
To request a Short Version of your URL just send a message containing the URL.

Chat Message: http://pixagle.appspot.com
zaptin@xmppguru.appspot.com: http://zapt.in/D5 -> http://pixagle.appspot.com

Chat Message: xmppjingle.org
zaptin@xmppguru.appspot.com: http://zapt.in/D1 -> http://xmppjingle.org

This is quite handy, avoiding all the hassle to visit one of the other URL Shorteners just to have a smaller URL.

XMPP Bots - XMPPGuru

xmppguru@appspot.com

XMPP Provides easy and clean ways to build XMPP Bots, as I showed on the previous post, we can use Google AppEngine to create 24h online, zero-maintenance Bots.


One interesting Bot is a Guru One, the main objective of this Bot is to clarify topics, answer general knowledge questions and retrieve hints for general opinion.
You can add it to your GTalk's / Jabber Contacts: xmppguru@appspot.com


Examples of general knowledge:
Question: What is Aerosmith?
xmppguru: Aerosmith is an American hard rock band, sometimes referred to as "The Bad Boys from Boston" and "America's Greatest Rock and Roll Band".

Question: What is an atomic bomb?
xmppguru: nuclear weapon: an explosive device whose destructive power is due to the uncontrollable release of energy from the fission of heavy nuclei, usually uranium-235 or plutonium-239, by neutrons sustaining a rapid chain reaction

Question:  Who invented the harpoon?
xmppguru: Endangered Species question: Who invented the harpoon cannon? Sven (or Svend) Foyn (1809-1894) was a whaler born in Tønsberg in southeast Norway. In 1856, he invented the bow ... 

Examples of general opinion:

Question: What is a good song?

xmppguru: What is a good song to "give" someone who you are …

Question: Do you trust god?

xmppguru: The Bible tells us to have faith: (Hebrews 11:6 NIV) And without faith it is impossible to please God, because anyone who comes to him must believe that he exists and that he ...

The Bot is not meant to have conscience neither deep lexical interpretation, the goal is to answer your question when possible, something directly with a straight answer, but something also vague hints.

For unknown answers the principe is the same of Horoscope, but in a scientific way. 

the best way of discovering how it works, purpose and functionality is by testing it.

Sometimes you will be surprised even asking by your full name. In the same way you will be surprised by crappy answers. Enjoy!

Google App Engine XMPP Services Example

Google App Engine released the XMPP Services a while ago. The service started very basic and bad, but since then, it is improving a lot and have potential to be really worthy to build XMPP Services over it.
Unfortunately currently you might only be able to write bots. Which is not that bad specially for developers that are starting with XMPP and App Engine.

The documentation is not that good so far, but it was enough to create an EchoBot Demo App, you can download the full source here.
To use it, just explode the folder, make sure you have Google App Engine SDK configured, set your application ID, and deploy.
I strongly recommend to use Eclipse AppEngine Plugin for those tasks.

Quick Tutorial

Receiving Messages are handled by your application like an HTTP Post Request:

@SuppressWarnings("serial")

public class XmppbotServlet extends HttpServlet {

public void doPost(HttpServletRequest req, HttpServletResponse res)

throws IOException {

Parsing Received Messages is piece of cake. AppEngine API is handy in that sense:

XMPPService xmpp = XMPPServiceFactory.getXMPPService();

        Message message = xmpp.parseMessage(req);

Creating a Response Message is also very simple:

JID fromJid = message.getFromJid();

String body = message.getBody();

// Create an Echo Message

Message response = new MessageBuilder().withMessageType(

message.getMessageType()).withBody(body)

.withRecipientJids(fromJid).build();

Now we send it back, without any specialist XMPP Knowledge required.

boolean messageSent = false;

SendResponse status = xmpp.sendMessage(response);

messageSent = (status.getStatusMap().get(fromJid) == SendResponse.Status.SUCCESS);

if (!messageSent) {

// An Error Occurred

}

Now you can create an XMPP Bot with just a few line of simple Java code.

Remarks:

• Your Bot will auto accept every XMPP contact add request, which is quite handy too. To test your Bot, just open your XMPP Account in your preferred Client. And add the contact: YourAppName@appspotchat.com
• It will auto-accept your request, and if your service is running, it will be shown as available.
• You can also use aliases like: Whatever@YourAppName.appspotchat.com

Gizmo5 is Now Part of Google's Family

+

Yesterday Google announced the purchase of Gizmo5, a SIP Service provider, that is being around for quite sometime. And I already received some emails questioning about Jingle's future in Google, as Gizmo is a fully SIP based services. So here comes the summary:

Why Gizmo5 and not Skype or other VoIP Service Providers?

• Gizmo uses SIP, which is an Open Standard. Buying anything closed and proprietary would cost Google a lot of money and huge drawback on integrations.
• Gizmo is a much more open and known for its interoperability with other SIP Providers. Skype has absolute ZERO interoperability and it is mainly a closed P2P service, which Google already solved in a way more elegant way.
• Main focus on calling from and to PSTN. Last thing it needs is another P2P Service.

What happens with Jingle on GTalk now?

Nothing! Google needs the flexibility that it offers and specially the natural integration with XMPP Wave Services. I don't see Google releasing Wave Services over SIP for now.
Jingle is by far the best solution for Internet Calling, and this is not a fact only mentioned by XMPP fans, but also by SIP Developers (Asterisk, SER, YATE, etc...).

Will GTalk support SIP now?
That is a tricky question, as there are two very close solutions, with pros and cons that I can't judge from Google's perspective what is better. Basically Google can solve it through:

1. Jingle/SIP Gateway, XMPP has a very reliable way to interconnect legacy gateways. Nimbuzz for instance already have all its SIP Services working through their XMPP Jingle Clients. They support third party SIP Providers and recently they also have released an embedded solution for calling to PSTN called NimbuzzOut.
2. Include a SIP Stack in Google Talk Clients. Which is not big deal. As we are plenty of SIP client side solutions and it is very easy to embed.

The point here is that I personally don't think Goggle is willing to implement SIP on  their widgets of web chat voice/video solutions like we have already on GMail. Making Jingle/SIP a necessity anyhow if they also want to allow their users place calls to PSTN also from a Website Flash Widget.

IMHO Google will probably go for a Jingle/SIP gateway, solution that I quite like for two reasons:
I already build such solution, and it works incredibly good! And has great scalability as well.
I also worked last year in the draft specification document that describes the integration Jingle/SIP Interoperability in Media Sessions.
If Google allows me to suggest: Go for Jingle!