<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/google/google-talk-adopts-jingle-as-default-voip-protocol.asp" />
  <link rel="self" type="application/atom+xml" href="http://blog.tmcnet.com/blog/tom-keating/atom.xml" />
  <id>tag:blog.tmcnet.com,2013:/blog/tom-keating//4/tag:blog.tmcnet.com,2011:/blog/tom-keating//4.46966-</id>
  <updated></updated>
  <title>Comments for Google Talk Adopts Jingle As Default VoIP Protocol</title>
  <subtitle>VoIP &amp; Gadgets blog - Latest news in VoIP &amp; gadgets, wireless, mobile phones, reviews, &amp; opinions</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.38</generator>
  <entry>
    <id>tag:blog.tmcnet.com,2011:/blog/tom-keating//4.46966</id>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/google/google-talk-adopts-jingle-as-default-voip-protocol.asp" />
    <link rel="service.edit" type="application/atom+xml" href="http://blog.tmcnet.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=46966" title="Google Talk Adopts Jingle As Default VoIP Protocol" />
    <published>2011-06-24T13:55:30Z</published>
    <updated>2011-06-24T14:19:02Z</updated>
    <title>Google Talk Adopts Jingle As Default VoIP Protocol</title>
    <summary>Google has adopted Jingle as the default protocol for Google Talk. Jingle is an extension of the XMPP which allows for peer-to-peer and session control (signalling) for multimedia interactions such as VoIP and videoconferencing.The protocol was developed by Google, Collabora,...</summary>
    <author>
      <name>Tom Keating</name>
      <uri>http://blog.tmcnet.com/blog/tom-keating/</uri>
    </author>
    
    <category term="Google" />
    
    <category term="SIP" />
    
    <category term="Skype" />
    
    <category term="TMCnet" />
    
    <category term="Video Conferencing" />
    
    <category term="VoIP" />
    
    <category term="p2p" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.tmcnet.com/blog/tom-keating/">
      <![CDATA[<img class="mt-image-none" src="http://blog.tmcnet.com/blog/tom-keating/images/jingle-logo.jpg" alt="jingle-logo.jpg" width="245" height="293" /><br />Google has adopted Jingle as the default protocol for Google Talk. Jingle is an extension of the XMPP which allows for peer-to-peer  and session control (signalling) for multimedia interactions such as VoIP and videoconferencing.<br /><br />The protocol  was developed by Google, Collabora, Yate, Tandberg and Jabber Inc. Others that support it include Asterisk, FreeSWITCH, Nimbuzz, and Pidgin. Imagine a P2P protocol that lets the thousands of Asterisk-based PBXs to communicate with each other using XMPP. Taking the Asterisk ecosystem along with other large user bases from Nimbuzz, Google Talk, and potentially others could potentially build the largest P2P VoIP / video conferencing network in the world. Bigger than Skype. Least, that's the promise XMPP holds.<br /><br />Peter Thatcher of Google said in his announcement to the Jingle developers list that &ldquo;the future is Jingle,&rdquo; and went on
<blockquote>
<p>&ldquo;I hope that this will be a support to the Jingle  community and futher our efforts to have open standards for voice and  video communication.&rdquo;</p>
</blockquote>
It would be nice to see a s<strong>tandardized P2P VoIP protocol</strong> and even see Skype support it, though I doubt that will happen. With Google announcing plans to build a VoIP client into the browser <a href="http://blog.tmcnet.com/blog/tom-keating/google/google-building-skype-like-app-in-the-browser.asp">just a couple days ago</a>, and now today's news, Google is clearly making aggresive steps within the VoIP arena. I wouldn't be surprised if a new entirely revamped version of Google Talk is released soon.<br /><br /><em>Via <a href="http://xmpp.org/2011/06/the-future-is-jingle/">XMPP Standards Foundation</a></em>]]>
      
    </content>
  </entry>

</feed>
