| |||||||||||||
A trojan for SkypeA trojan for SkypePosted Sep 3, 2009 11:22 UTC (Thu) by rwmj (subscriber, #5474)Parent article: A trojan for Skype
No one is going to willingly switch to Ekiga and/or SIP, because the software and the SIP protocol SUCK. I'm a computer expert and I couldn't get either to work reliably. You have to tweak dozens of settings, and then it still doesn't work. Epic fail. Why it's so hard to make a VOIP system that just works I don't know, but Skype did it, and that's why people use it. Rich.
(Log in to post comments)
A trojan for Skype Posted Sep 3, 2009 16:22 UTC (Thu) by shredwheat (guest, #4188) [Link]
I must agree. Ekiga is too difficult for me to understand. Skype is click and talk (assuming PulseAudio does not interfere on my end)
Ekiga Posted Sep 3, 2009 16:51 UTC (Thu) by cry_regarder (subscriber, #50545) [Link]
After trying (and finally succeeding on my end) in getting ekiga to work as far as a succesfull connection to the echo server (sip:500@ekiga.net), I now understand why people are angry about pulse and other sound.
I have a bog common HDA intel audio. Q965 chipset. I had to go in to gst-mixer and enable the Microphone (it wanted to enable the Front microphone which I don't use 'cause it has a 60hz hum). Then I had to enable two recording device (Capture and Capture 1). I had to unmute the microphone on Capture which let pulse hear the mike. Then I had to unmute mike on Capture 1 which let non-pulse Alsa hear the mike. I had to disable the Mixer because otherwise the mike was linked to the speakers and instant echo ensued.
I also had to bump Fedora 11 to the 2.6.30 kernel in testing.
Finally everything was working. Then I couldn't get the distant end to be able to connect to ekiga.net from behind their NAT. And I've been working on and with linux since 1994 everyday since 1994 (I even have a freerunner as my daily phone).
I decided to try empathy instead. Not even close to being close to connecting. Tried gossip. Good luck! Linphone? Not a hope.
First time I've come close to crying since I had a double disk failure on my raid 5 last year. (which I fully recovered from with no data loss by the way thanks to Neil Brown and the others on the raid list).
Vent :-)
Cry
Ekiga Posted Sep 4, 2009 10:31 UTC (Fri) by rmano (subscriber, #49886) [Link]
Agreed. And moreover, Skype offer a cheap, with clearly published rates, service to call normal landphones all over the world. I'd like a viable open alternative, but I cannot find any.
Ekiga Posted Sep 4, 2009 14:43 UTC (Fri) by foom (subscriber, #14868) [Link]
There's a *ton* of alternatives for landline call-out and call-in.
Personally I'm using Callcentric.com service with a "hard" phone (e.g. not a computer-based phone)
A trojan for Skype Posted Sep 3, 2009 17:50 UTC (Thu) by droundy (subscriber, #4559) [Link]
Agreed. I used ekiga for over a year to meet with students I advise, and we never were able to get the audio to be consistently comprehensible, and ended up just chatting on the phone much of the time. We're now using skype, and it works way better. I hate the fact that I'm using nasty proprietary software running a proprietary protocol, but it works, and ekiga doesn't.
A trojan for Skype Posted Sep 3, 2009 20:31 UTC (Thu) by davide.del.vento (guest, #59196) [Link]
Yes, I hate skype, but ekiga is just terrible and useless. I was able (without much effort) to have it working on my computer and a on a couple of friends' ones. But the voice quality is bad, and the video is painful worst. On the same network skype works just fine (unfortunately, because I hate it!)
A trojan for Skype Posted Sep 3, 2009 21:46 UTC (Thu) by Cato (subscriber, #7643) [Link]
This is most likely down to the Global IP Sound codec licensed by Skype, which is highly resistant to packet loss, delivering pretty good quality on a range of connections as well as being the same on all Skype clients. I also find it better than the expensive Nortel VoIP softphone client that I use for work - also SIP based, but the real issue is the codecs.
A trojan for Skype Posted Sep 4, 2009 9:42 UTC (Fri) by tpo (subscriber, #25713) [Link] I had similar problems with VoIP SW under Linux and have, as everybody else here, made the rounds and installed every possible Linux VOIP client in the universe. I've settled on Twinkle. In my opinion it's easier to use and to configure than the other clients and also more resilient and tolerant. I'd even go as far as to say that, that I like the software which is in contrast to many of the other clients which were painful.
|
|||||||||||||