Skype Out - Pidgin In
Recently, myself and my colleagues at Pelagicore decided to try to ditch Skype for an open replacement. We have been suffering stability issues with Skype for a long time, but our customers rely on it for contact with us and most people know how it works. However, recent events such as Microsoft buying Skype and cancelling support for Asterisk motivated us to try the alternatives.
What we want to avoid is some sort of lock-in, and at the same time, we want it to be easy to have people join. After some discussions and tests we decided to go for Jabber and libjingle. This is what Google Talk uses, so anyone using GMail is automatically in. This was a big benefit for us, as we run Google Apps on our domain.
So, first out was trying video and voice directly from within the web interface to Google Apps. Our tests show that this works out of the box on both OS X and Linux, Chrome as well as Firefox. However, this does not take care of the lock-in situation that we wanted to avoid.
Next step - Pidgin! Pidgin is available prepackaged for Windows, OS X, CentOS/RHEL, Fedora, Ubuntu - and as source code of course. Having installed it, video and audio seems to just work. Again - great success. File transfers also work great, so Skype is more or less replaced when it comes to our needs.
So, how is Pidgin configured for this? There are a number of guides for configuring Pidgin with Google Talk using a GMail account. For myself, I had to do some tweaking to get it to work with our Google App setup. So, here is the configuration I'm using:
On the Basic tab:
- Protocol: XMPP
- User name: john.doe
- Domain: example.com
- Resource: where you are right now, home / work / mobile
- Password: I leave this as an exercise to the reader
On the Advanced tab:
- Connect port: 5222
- Connect server: talk.google.com
- File transfer proxies: proxy.eu.jabber.org
During this transition, I tried the Skype integration in Pidgin. Basically - it sucks, and Skype is to blame for that. My recommendation is to use both clients if you need to during a transition period.
And a final tip - if you use the web interface for GMail, you can check out of chat there to avoid it opening a small window each time some calls you and you reply through Pidgin.
Johan Thelin is a consultant working with Qt, embedded and free
software. On-line, he is known as e8johan.
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Introduction to MapReduce with Hadoop on Linux
- RSS Feeds
- New Products
- Weechat, Irssi's Little Brother
- Validate an E-Mail Address with PHP, the Right Way
- Tech Tip: Really Simple HTTP Server with Python
- Poul-Henning Kamp: welcome to
2 min 9 sec ago
- This has already been done
3 min 9 sec ago
- Reply to comment | Linux Journal
48 min 23 sec ago
- Welcome to 1998
1 hour 36 min ago
- notifier shortcomings
2 hours 35 sec ago
3 hours 37 min ago
- Android User
3 hours 39 min ago
- Reply to comment | Linux Journal
5 hours 32 min ago
8 hours 21 min ago
- This is a good post. This
13 hours 34 min ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?