Google switches GTalk's VOIP protocol to Jingle
1–10 of 50 posts
Re: Google switches GTalk's VOIP protocol to Jingle
#2My original email had more details:
We are pleased to announce that we have launched support for Jingle XEP-166 and XEP-167 for Google Talk calls to and from Gmail, iGoogle, and Orkut. We have also added the same level of support to libjingle (http://code.google.com/p/libjingle), which is used by many native clients. From this point on, it will be our primary signalling protocol, and the old protocol will only remain for backwards compatibility. We also plan to soon update Google Talk on Android to speak Jingle, but we do not plan on updating the Google Talk Windows application.
We suggest all clients that interop with Google Talk to switch to using Jingle rather than the old protocol. We will remain backwards compatible with legacy clients by continuing to speak the old protocol as well. If you wish to continue working with legacy clients, such as the Google Talk application for Windows, you may also wish to continue speaking the old protocol. But the future is Jingle, and the old protocol will eventually go away.
Finally, we are still working on implementing XEP-176 (ICE-UDP). In the meantime, you'll need to use our draft-06 version of ICE, which is implemented both in libjingle and in libnice, two open source libraries.
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.
Re: Google switches GTalk's VOIP protocol to Jingle
#3The annoucement email itself: http://mail.jabber.org/pipermail/jingle/2011-June/001640.htm...
This is great news. Google has been one of the driving forces behind Jingle, but as they were implementing it far in advance of being standardised, the drafts/standards have since changed. Other implementations have to maintain support for several close but not quite the same dialects. Google updating their software will make interop much easier.
I've been somewhat critical of Google's attempts in this direction (http://senko.net/en/gmail-videochat-the-good-the-bad-and-the...), and I'm very glad to see I was wrong :)
Re: Google switches GTalk's VOIP protocol to Jingle
#4I wonder what impact this will have on 3rd party devices like the great Obihai that interface with Google Voice?
Re: Google switches GTalk's VOIP protocol to Jingle
#5I wonder why the Windows client will officially not be updated to Jingle? If it was just "not at the moment," they would have either kept mum or said so, but to actually say that it won't be updated..... that says a lot.
Re: Google switches GTalk's VOIP protocol to Jingle
#6Well, I am not sure why Google went with XMPP when the rest of the telecom and networking industry is gravitating towards IETF SIP as signaling protocol. There are so may overlaps in both of them in the sense that they use the same components such as SDP and ICE. Can anyone from Google or otherwise throw some more light on
- Why Google prefers XMPP over SIP - In what areas XMPP is better that SIP
I am not stating that one is better than the other, but would like to understand the core differences and advantages.
Also with Google moving on with XMPP and other major vendors converging on SIP, where do you see the inter-operability issue heading towards?
Re: Google switches GTalk's VOIP protocol to Jingle
#7For information on support in GNOME's Empathy IM client and on Maemo/MeeGo, see http://blog.barisione.org/2011-06/broken-gtalk-calls/
Re: Google switches GTalk's VOIP protocol to Jingle
#8Smells like FaceTime is coming soon for google chrome.
Re: Google switches GTalk's VOIP protocol to Jingle
#9Can iChat speak Jingle?
I just tried the combination of web-based Gmail iChat and the web client can see that the iChat client has a camera and I can initiate a call but iChat never shows an incoming one.
If I go iChatiChat over Google's XMPP server I can make a call. Does iChat speak yet another incompatible video call extension if it used with an XMPP network?
Adium can't do AV either.... Can anyone recommend a OS X client? Video chat is currently the last thing that stops me from uninstalling Flash.
Re: Google switches GTalk's VOIP protocol to Jingle
#10Well, I am not sure why Google went with XMPP when the rest of the telecom and networking industry is gravitating towards IETF SIP as signaling protocol. There are so may overlaps in both of them in the sense that they use the same components such as SDP and ICE. Can anyone from Google or otherwise throw some more light on - Why Google prefers XMPP over SIP - In what areas XMPP is better that SIP I am not stating tha…
I guess SIP has weak support for Instant Messaging, which was the primary use case for Google Talk before video chat came along.
On the other hand the Jingle spec [1] contains many references to SIP:
"Furthermore, Jingle is not intended to supplant or replace existing Internet technologies based on the Session Initiation Protocol (SIP; RFC 3261). Because dual-stack XMPP+SIP clients are difficult to build, Jingle was designed as a pure XMPP signalling protocol. However, Jingle is at the same time designed to interwork with SIP so that the millions of deployed XMPP clients can be added onto existing Voice over Internet Protocol (VoIP) networks, rather than limiting XMPP users to a separate and distinct network."