GNU Free Call Announced, SIP-based VoIP
andrea.sartori sent in the "development plan for GNU Free Call, an open source VoIP service based on the SIP protocol. According to the announcement, it 'aims to be as ubiquitous and usable as the proprietary Skype VOIP service.'"
It will allow the government to track you.
I'm a good cook. I'm a fantastic eater. - Steven Brust
So this has no relation to the two previous articles? http://mobile.slashdot.org/story/11/03/15/0432226/Richard-Stallman-Cell-Phones-Are-Stalins-Dream http://it.slashdot.org/story/11/03/15/1513257/Encrypted-VoIP-Meets-Traffic-Analysis
When was the last time something GNU became "ubiquitous and usable"?
Its aims are going to be crushed by its terrible name. GNU Free Call is a mouthful that even I, knowing what the acronym means, don't like the sound of. If they want adoption they should quit their self-promotion-in-the-name and re-brand, even "GFC" would be a million times better.
In case you're not aware, Ekiga already exists and is a free-software SIP client implementation. See http://ekiga.org/ . At best this should be an extension for Ekiga, not an entirely new project.
-molo
Using your sig line to advertise for friends is lame.
Oh oh! Being GNU, does that mean that my conversations become open sourced by purely communicating over this service? I'm wondering this because technically my voice is being de-compiled into a byte stream and then re-compiled on the other end. Doesn't that make all my conversations bound to the terms in GPL? And how would I attach the source code of my conversation? Would I have to have some sort of text-to-speech implemented (non-proprietary of course) to facilitate this? And if I am discussing something related to application design and as a result of the conversation we implement new features, does my application then become bound to GPL? And if so do I need to attach source code to the GNU VoIP service to my application?
Hmmmmmmm
Empathy, Ekiga, Twinkle... the list goes on. Even pidgin has SIP plugins. Why is this project special or needed?
...and it will never, EVER happen. For one, it would have to be available on smartphones, which seem to give Stallman a rage-boner so hard that it sucks all the blood out of his brain, resulting in this sort of rant: http://mobile.slashdot.org/story/11/03/15/0432226/Richard-Stallman-Cell-Phones-Are-Stalins-Dream Not to mention the myriad other devices that Skype runs on -- there's even a Linux client for it, no less. Freecall is just another one of GNU's pet projects that's never actually going to -go- anywhere, outside of the circle of sad and fanatical folks that still think HURD is going to replace the Linux kernel one day.
Summary:
SIP doesn't even traverse NAT firewalls without help from outside, and even then, barely.
SIP is also too verbose, and therefore it's hard to tweak the network to avoid jitter. (This is a huge problem currently)
A large reason why Skype became so popular is, that it didn't have the same problems as SIP.
IAX2 has none of these problems, supports multiple line trunking, and, it's already supported by lots of software and hardware.
IAX2 was developed out of a need for an efficient call trunking protocol for the free PBX called Asterisk.
In the beginning, the author clearly stated IAX shouldn't be used by others (moving target), but since it's clearly being used already, it's become a sort of de-facto standard since nothing else works as well.
There are many GNU tools prefixed with "GNU/" but in practice the "GNU/" is always dropped in everyday use.
A last moment request to the developers: Please make exiting of the reference client the key sequence ESC:wq\n and not Ctr-X Ctrl-C. Please?!
I hadn't the slightest objection to his spending his time planning massacres for the bourgeoisie... (P.G. Wodehouse)
Congress passed a law requiring US based ITSP's to provide E911 support. If this idea ever went live it would require the same connections to E911. This connection costs money, its not free...
GNU VoIP would have to pay Verizon/Comcast/et cetera to connect to E911 and who is going to pay for that?
Unless congress provides an exemption.. (pfft, yahh)
Seriously, I tried sipwitch on my laptop, and quickly removed it when I realized that it was often using 100% of my CPU. Bad experience. I hope they will improve, because I, too, need a free software alternative to Skype.
Steve Ballmer intimates this is infringing on Microsoft patents; then I'll know it's real.
I miss read the summary at first and thought they are aiming for it to be as stable as Skype, I thought can't you aim a little higher than that guys.
Reminds me of someone talking about how they got 5 nines uptime with Windows, some else asked if they were aiming for 10% next year
If you read a speed reading book, does it take you less time to read the second half?
Think it will ever happen? Or is this just more GNU vaporware
Meh, personally, I hope it goes through, because if you ever have to support it, you'll be in the Gnu Free Call Information Technology group, and get to say to people...
GNU -- FC IT, but how can I help you anyway?
As others noted, it bears some remote resemblence to skype. I wonder why they chose GNU Free Call and decided to go the peer to peer route. I would think having a community hosted, distributed PBX would be a much better solution. I happen to really like SIPXECS at http://www.sipxecs.org./ It lends itself to distribution quite well. Plus, SIPXECS is quite mature as a platform. I cannot help but cast a somewhat dubious eye at GNU Sip Witch.
I was all excited to see what a VoIP program that distinguishes itself as being "free of GNU" really meant. Come to find out, it is just a GNU project with a terrible name.
Whether you like Stallman's politics or not (i think he's a bit of a zealot, but I'm sure he'd agree and think as a compliment) there's a decent history of projects launched and ending up in some kind of Limbo someplace. Even emacs, his pet project, got forked into xemacs because of inactivity. The hurd has gone through many iterations, many underlying microkernels, and seems irrelevant. Even gcc, probably the best known and used FSF project, was forked by the egcs team and moved so much quicker than mainline gcc that it eventually became the new Guardians of gcc. Remember that The Cathedral and the Bazaar used FSF gcc development as the closed Cathedral model.
So, will this be a typical FSF project where they copy something badly (GNU gdbm vs Berkely dbm) just because they can? Or will Stallman realize that the best way to get people to use his code is to get them something actually usable, and not rely on the excuse 'well it's OPEN'.
the op obviously hasn't tried the "latest" 2.1 beta of skype for linux - i expect he's been using skype 5 on windows/osx.
#include <sig.h>
Now Richard Stallman can finally have a regular phone! But not a cell phone of course. They are coming...
Perhaps we need to add steganographic noise to the other elements on your photo-sharing sites, just so that your messages don't stick out like a sore thumb.
The one feature I have not seen on ANY of the VoIP programs, game, phone, or otherwise, is a nifty little system called JACK. To have a VoIP client with the ability to connect with other JACK clients would be downright awesome; this would especially be the case for broadcasters, podcasters, and other types of people who work with sound for a living.
The Penguin Producer
All these have already failed when applied to mail - what makes you think they'll work for telephony?
http://www.cellphonebeta.com/electronics/cell-phones/bmw-162