Slashdot Mirror
Google, Jabber, and Jingle
An anonymous reader writes "Jabber has published the experimental draft Jingle specs, which extend XMPP for use in voice over IP (VoIP), video, and other peer-to-peer multimedia sessions.
Google released an open-source library called 'Libjingle' on SourceForge. Libjingle is a set of components provided by Google that let your programs interoperate with Google Talk's peer-to-peer and voice calling capabilities. The package includes source code for Google's implementation of Jingle and Jingle-Audio."
I'm not fat, just big boned...
I have the only w33n0r I think I need to see when logging on.
Now if google would just implement server-to-server jabber connections, this might be useful!
Let's hope someone can now develop a Gtalk pocketpc application with voice. While they are at it: add conference mode to Gtalk; in business environments it's very handy.
Good for you! Meanwhile, for the rest of us who aren't paranoid/Google-bashers, this is a boon, including Jabber users (you know, this will work for your Jabber server too, right? ;)
Besides, Google hasn't implemented Server-to-Server communication yet for reasons posted elseware in this very article; they don't want spam. It's harder to validate posts coming from offserver without actually reading them, which would breech your privacy, right? (On server they have the option of reading it [via EULA], post rate limiting, banning accounts, etc)
So please, next time Google (or $BIG_COMPANY) gives the open source world a donation and a piece of code it's been needing for a while now, take it as a gift, and try not to be so critical about it. Thanks.
"Victory means exit strategy, and it's important for the President to explain to us what the exit strategy is." G.W.Bush
Of all the people to have a broken link... Did anyone else try the "Home Page" link on the SF project description?
There's an old saying that says pretty much whatever you want it to.
I better lock the door before my pointy haired boss comes in: "This looks interesting. I want VoIP before you can go home for Christmas."
Insert `fortune -o` here
last time i checked they didn't have a voip client for linux either. you can use jabber'over'gaim to use gtalk itself but you're unable to make the calls. let's hope this library makes it possible.
...)
until then, i stay with the hype-skype which works rather well (if you don't mind the cpu and network overheads
I'd tell you the chances of this story being a dupe, but you wouldn't like it.
All these instant messagers and voice applications could somehow communicate so would not need to have so many on my computer. Even if the communication was on lowest common denominator, could use the ones I like and atleast communicate somehow with people using others.. oh well.. not likely to happen soon I guess.
Using transcoded XML for binary audio support... I wonder if some bandwidth is wasted just because of the format (XML can't contain random binary data, so there's bit loss). Anyone checked deeper?
...their system where the advertisers call you? It's safe to assume they'll be adopting the platform and munging it with some sort of phone connection to achieve this. This could be just the step they're looking for to lower costs and make more profit. And on top of that, how many other messengers have an open voice protocol? How long before we see extensions etc? And how long before some wisespark tries that Skypecasting thing with it? Since jabber can technically support any mime type, all we would need is for someone to plug theora into it and instantly it can be done.
~HTP~ Hug that tux
Psi, one of the most popular Jabber clients out there has announced that they are working on support for jingle. http://psi-im.org/forum/post/24491
I don't buy this. Spam in Jabber is much more difficult to achieve (some people say it's impossible but they're probably wrong) and Jabber without server to server is not fully Jabber.
... and call their sweet new product Gibber.
There was talk of google potentially buying AOL.. If this happened, they could migrate the existing AIM/ICQ networks over to a jabber based protocol, while maintaining the existing protocol for compatibility..
They could retain gtalk as it is too, and allow server to server jabber communication between both their servers and external jabber services..
AIM already has a large userbase, and with such ease of communication between services it may be large enough to convince yahoo/msn to co-operate too.
http://spamdecoy.net - free throwaway anonymous email - avoid spam!
Too many? Most are proprietary, or not suitable for IM (because of lack of quality NAT traverssal, frex).
SIP could work but is cumbersome when all you want to do is get an RTP voice stream going. Having a standard that is clear, concise and tailormade for IM applications is useful.
IM clients are the obviousplace to strapon VOIP communication. The jabber system would be a perfect VOIP framework. Your "number" will simply be your JabberID. Which is similar to an email address, so it's easy to remember.
You'll simply dial something like "malda@slashdot.org" to complain to Taco about the preponderance of dupes, and Taco can simply add your address "slashbot@cheapisp.com" to his ignore list.
If telemarketers become a problem, some kind of del.ico.us system might enable VOIP users to share a list of banned domains or addresses. Potential for abuse etc, etc.
Key point here is that a system based on "email" like addresses would be batter and easier to remember than the current telecoms number based system.
May the Maths Be with you!
The main Gaim developer was hired by Google and given the low-down on the Jingle project some time ago, and it'll be added to the Gaim-vv system that's apparently coming in Gaim 2.0.
I thought the intention was to use SIP as the underlaying protocol.
Google should implement server-to-server but drop any incoming messages from users that are not on the recieving user's roster. This way people can still talk to their friends on other Jabber servers but unsolicited messages won't be a problem since they'll be dropped outright.
This may cause difficulties for agents that aren't people, such as services and bots, but at least it would open things up a little for person-to-person communication.
Let's not forget that Google want to make a decent profit. But companies have different ways to make a profit.
For instance, some manufacturers take the attitude of building in a short lifespan because then they can get another sale soon after. Others take the view of making a less than reliable product and making a lot of money on spare parts. Others use various means to ensure that any upgrades/consumables for the products will cost a great deal. And a few decide that the best way to trade is to make a great value product because even though you don't get a good short term hit, you build customer loyalty and word-of-mouth. Financially speaking, there's probably no right answer to make money.
They couldn't have come up with something better than libjingle?
What about libjingoober?
Or better yet, just a library without that jingle crap called libgoober?
~ ><>
Incorrect. SIP is a signalling protocol, same as Jingle.
To set up a connection to a SIP-capable device you typically use:
- SIP to signal intent to communicate (and to accept or refuse or redirect, etc)
- SDP to describe the coming transport session (which port, where do I send the data, which codec do I use, etc)
- RTP to use that SDP data to make the actual connection and send the encoded data.
Jingle replaces the SIP/SDP steps. Summary of operation, Romeo tries to call Juliet:
- Romeo initiates a call to Juliet, sends back either "refuse", "redirect" (to a cellphone client, say) or "provisionally accept".
- Romeo offers up several candidate transports that it can use. It either does this all at once (burst) or one by one (dribble), which is specified in the initation message.
- Juliet offers up several candidate transports (RTP, G.711 codec, frex) that it can use.
- Once concensus is reached over a suitable transport, Jingle switches to "in progress" and RTP takes over. If concensus is impossible the connection ends.
- Finally, Jingle politely closes (and confirms) to end the conversation.
The two processes achieve the same endgoal: getting VoIP data from A to B. An advantages here is that SIP isn't very lightweight in terms of correct implementations, while Jingle can be 'spoken' by any client that can do XMPP as long as you add the statemachine.