I wonder what impact this will have on 3rd party devices like the great Obihai that interface with Google Voice? http://www.obihai.com
I don't know how Obihai works, but if it uses SIP to talk to Google Voice, this will not effect them.
Google switches GTalk's VOIP protocol to Jingle
11–20 of 50 posts
Re: Google switches GTalk's VOIP protocol to Jingle
#12Can 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 iChat iChat 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…
http://www.apple.com/macosx/whats-new/features.html#ichat6
iChat in Lion will features service plugins.
Re: Google switches GTalk's VOIP protocol to Jingle
#13I 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.
The official client never got video chat support either. It's received very little love over the past couple of years.
Personally I think the only native client they are interested in anymore is Gmail in Chrome...
Re: Google switches GTalk's VOIP protocol to Jingle
#14Can 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 iChat iChat 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…
http://www.apple.com/macosx/whats-new/features.html#ichat6 iChat in Lion will features service plugins.
It's not clear whether this includes audio and video? It may be only for text chats.
Re: Google switches GTalk's VOIP protocol to Jingle
#15My 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 rema…
In light of interoperability, could you please address the Google rationale for going with XMPP rather then SIP, as there is considerable support for SIP in existence, e.g. IMS on 4G networks, VoIP providers, PSTN gateways, Skype Connect, etc.?
Re: Google switches GTalk's VOIP protocol to Jingle
#16I 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.
The official client never got video chat support either. It's received very little love over the past couple of years. Personally I think the only native client they are interested in anymore is Gmail in Chrome...
We care about gmail on all browsers :).
Re: Google switches GTalk's VOIP protocol to Jingle
#17Well, 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…
If this had happened for email, we would have had to deal with a myriad of different clients, servers and 'interworking' gateways.
I really don't understand why the likes of Google, Apple, Microsoft and the telcos can't agree on a standard. Guess business reasons are behind this. After all, walled gardens are great if you are the incumbent, it's how Skype got to be so valued.
Maybe the FCC should step in and take this on.
Re: Google switches GTalk's VOIP protocol to Jingle
#18Earlier quoted context omitted.
The official client never got video chat support either. It's received very little love over the past couple of years. Personally I think the only native client they are interested in anymore is Gmail in Chrome...
We care about gmail on all browsers :).
What about people who don't like or use the Gmail web UI (I use it over IMAP) but would still like to use Google Talk to stay in touch with friends? Is my only option to use third-party clients? I like Google Talk but dislike Gmail, and tying the two together doesn't really work out in my favour.
Re: Google switches GTalk's VOIP protocol to Jingle
#19My 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 rema…
In light of interoperability, could you please address the Google rationale for going with XMPP rather then SIP, as there is considerable support for SIP in existence, e.g. IMS on 4G networks, VoIP providers, PSTN gateways, Skype Connect, etc.?
I'm one of the authors of the XEP and was part of the Google Talk team back in the day. I haven't been working on it in quite a while so I really don't speak for the current team.
First off, I'm super proud of these guys finishing off this work. It was a long time coming.
As for why we chose XMPP over SIP: The team had made the choice to base the core IM product on XMPP before I joined. That decision was based on the ease of implementation and interoperability. XMPP for IM is much simpler than SIP/SIMPLE. The easiest answer here is that it was the most logical fit to the product we had built at the time.
My personal opinion of SIP is based on a 6 year old snapshot of the technology. Things have undoubtedly changed in the meantime. Based on that snapshot, I wasn't a fan at the time.
- It is an amazingly complex and confusing technology. It is worth noting that SIP is the longest IETF RFC out there. Meanwhile, the core XMPP spec is easy to understand and implement. It is also an IETF standard. Extensions are well modularized and documented.
- The security is hacked on after the fact and, at the time, was unevenly implemented. In basic SIP, one unauthenticated UDP packet makes a phone ring. XMPP security is based on TLS and DNS and is a required part of the core.
- Federation was a patchy mess and showed SIP's telecom roots. You pretty much had to get the lawyers involved to do anything. Federation in XMPP is a DNS SRV lookup.
The world has moved forward since then so hopefully this provides some context for the decision at the time.
Re: Google switches GTalk's VOIP protocol to Jingle
#20Earlier quoted context omitted.
http://www.apple.com/macosx/whats-new/features.html#ichat6 iChat in Lion will features service plugins.
It's not clear whether this includes audio and video? It may be only for text chats.
Lion supports Yahoo’s AV protocol, and I assume it’s integrated using the new plugin architecture.