Linux.com

Feature: Open Source

Review: Jabbin adds VoIP to Jabber

By Nikos Kouremenos on October 19, 2006 (8:00:00 AM)

Share    Print    Comments   

Most Jabber clients for GNU/Linux and other platforms limit themselves to exchanging text messages. Jabbin, a fork of the Psi Jabber client, focuses on VoIP.

Jabbin is written in C++ and Qt and released under the GNU General Public License. The software's Web site is available in 11 languages. Binary packages are available for Debian, Ubuntu, Fedora, SUSE Linux, and Windows.

Using Jabbin

For the last three years I've used a Jabber client -- Psi or Gajim -- every day. I used them not only for simple text chatting, but also file transfers and chatting with contacts from other IM protocols such as MSN and ICQ.

Jabbin does all of the above, plus something more: voice over IP calls. This means you can call and speak with a contact that uses the GTalk official client or another Jabber client that is compatible with the Jingle specification instead of typing all the time with the keyboard. There is no need for extra services running in the middle, as Jingle is all client-side.

I have several Jabber accounts on various servers, so I tested Jabbin with a wide variety of Jabber servers, including Google Talk. Jabbin didn't have any problems using any of the servers that I tested it against.

The Jabbin user interface

Jabbin's user interface is mostly a copy of the interface of Psi, a client that is notorious for having one of the worst UIs of any IM clients. Psi's developers recently made some changes to its UI to make it easier to use, but Jabbin forked from Psi before those changes were made and don't care about merging them. One obvious potential improvement -- the button that is visible during voice calls, which now indicates "hang on," should become "hang up".

The main window of Jabbin is by default always on top, a bad habit Jabbin inherited from Psi. The first time Jabbin runs, users must face the account creation window (again copied from Psi), which is a disaster in terms of usability and likely to scare users away. An account creation wizard would work much better.

Jabbin client
IM clients should make it easy to type IM text with as few mouse clicks as necessary, but Jabbin doesn't. For example, clicking on the Jabbin window doesn't give focus to the text area; you are expected to click in the window and then click in the text area and start composing your message.

Jabbin does a little better when it comes to security. It lets you encrypt messages with the OpenPGP protocol, thus making it a safe choice for those who care about exchanging sensitive information in real time via instant messaging.

Users migrating from Psi should note that Jabbin uses the same configuration file that Psi does, in the same path. This may be handy for ex-Psi users, but may baffle others, and it's likely to cause problems if Psi decides to change the format of its configuration file and Jabbin goes to read it.

Trying out Jabbin 2.0 beta

Currently Jabbin does VoIP over Jabber using the TINS specification, which one year ago was superseded by the Jingle specification, which was co-written by Jabber Software Foundation and the Google Talk team. Jabbin 2.0 will switch to Jingle, thus making it the first Jingle-compliant open source Jabber client with a GUI that can do VoIP and interoperate with Google Talk. Because Google Talk is expanding into portable devices such as the BlackBerry and the upcoming Sony Mylo, Jabbin users will be able to converse with people running those platforms too. GTalk is expected to interoperate with Skype soon too.

The recently released beta of Jabbin 2.0 is packaged in a proprietary RAR archive -- not something one expects from an open source application, and a choice that probably needs a second thought by the Jabbin team. After installing it, I was able to connect to my Google Talk account (Jabbin 2.0 also adds support for SSL connections), but most of the time I was unable to use VoIP with other contacts that were using the official Google Talk client or Jabbin 2.0, because Jabbin crashed. Twice during my tests I was able to see Google Talk crash too, thanks to, as far as I understand, bad requests from Jabbin.

I also wasn't able to exchange files with Google Talk client users because Google Talk developers chose to implement a custom Jingle-based specification for file transfer which they have not yet published.

Jabbin needs better documentation for its compilation from source procedure, since there is no complete dependency list; parts of it are in the README and INSTALL files and the online forum.

Final thoughts

Overall, Jabbin is a good Jabber client. When Jabbin 2.0 comes out of beta, then hopefully VoIP with Jingle will work consistently, as opposed to sometimes. Jabbin will appeal to those who need to use the GTalk VoIP service but also require their client to be cross-platform or open source.

There are major problems with the usability of Jabbin, especially for someone who has a Skype-like background, and even though there is a Getting Started Guide available, it still is not as easy to install the client, fire it up, and talk with contacts without all the first-time hassle. The interface could be massively improved to be more user-friendly. Some saner default settings would make the overall experience less annoying. Jabbin is not so hard to use, but the first impression says the opposite.

Share    Print    Comments   

Comments

on Review: Jabbin adds VoIP to Jabber

Note: Comments are owned by the poster. We are not responsible for their content.

psi has had this for a while now

Posted by: Anonymous Coward on October 20, 2006 07:05 PM
Psi's UI is quite usable to me. Not perfect, but definitely not the worst. Any IM client with adverts would be worse, to begin with.

Also, Jabbin is NOT the first client to have voice support, because I've used Psi itself with jingle for quite a while now. Maybe they've renamed the branch due to issues with getting the patches into Psi?

#

Re:psi has had this for a while now

Posted by: Anonymous Coward on October 20, 2006 08:15 PM
Psi latest UI is better than the one that it used to have (and thus the one Jabbin has more or less).

Jabbin has a thing you can install and talk, whereas with Psi you can't just get it from their website and install it and talk.

I think this is a huge difference. Moreover Jabbin 1.0 did VoIP over Jabber long before Psi did the Jingle branch.

That is all,
Nikos Kouremenos

#

Re:psi has had this for a while now

Posted by: Anonymous Coward on October 20, 2006 08:55 PM
This isn't actually true, Psi released their Jingle branch before Jabbin released with their (already obsolete) TINs support.

#

Re:Yessssss!

Posted by: Anonymous Coward on October 20, 2006 08:11 PM
I think you missed the next sentence:

Psi's developers recently made some changes to its UI to make it easier to use, but Jabbin forked from Psi before those changes were made and don't care about merging them.

Also what is said about clicking in the text area, and then start to write, is also true.

Last but not least, Justin AFAIK is more in the library than in the UI, and I recall Psi once shipped with a checkbutton to disable getting your own vcard, just because a developer of Psi was using it via a portable device that even one kb less would make sense.

Now if you can call this, good UI, I'll propose to Justin not to get a UI job (not that he planned to AFAIK again)

The fact that Jabbin is a fork of Psi and does not crash when it does basic xmpp and gpg encryption, I think proves the obvious, that Psi was and is a 'working good' client.

Have fun,
Nikos Kouremenos

#

Re:Yessssss!

Posted by: Administrator on October 20, 2006 09:16 PM
We know.<nobr> <wbr></nobr>:)

#

Its not all that bad

Posted by: Anonymous Coward on October 20, 2006 08:24 PM
I have been using jabbin for sometime now and I must say that its good. It works well. All the issues reported here are known issues. Developers are working to improve it.

#

Jabber rules!

Posted by: Anonymous Coward on October 20, 2006 08:47 PM
<a href="http://www.jabber.org/" title="jabber.org">Jabber</a jabber.org> rules!
It uses the open source <a href="http://www.xmpp.org/" title="xmpp.org">XMPP</a xmpp.org> protocol. It is really cool, I downloaded a library and was able to code a bot in no time.
I always am connected to Jabber using a SSL secured connection.

<a href="http://en.wikipedia.org/wiki/Jabber" title="wikipedia.org">Jabber on Wikipedia</a wikipedia.org>

#

Re:how about psi-jingle?

Posted by: Anonymous Coward on October 20, 2006 08:58 PM
It's also interesting to note that the jingle support for Jabbin appears to be a backport from the Psi development branch of Psi's jingle code.

#

Re:how about psi-jingle?

Posted by: Anonymous Coward on October 20, 2006 09:00 PM
The reason we stopped development on the psi-jingle branch was that it was merged into the mainline code some time ago.<nobr> <wbr></nobr>/Kev

#

Re:how about psi-jingle?

Posted by: Administrator on October 21, 2006 01:04 AM
meaning the latest version of psi itself has voice support? i havent checked in a long while now..so no clue..:-/

#

rant or review ?

Posted by: Anonymous Coward on October 20, 2006 10:07 PM
Mr. Kouremenos is a developer for another jabber client, gajim (<a href="http://www.gajim.org/dev.php?lang=en" title="gajim.org">http://www.gajim.org/dev.php?lang=en</a gajim.org>) . So we have one developer criticizing other clients and their developers...

The review is supposed to be about VoIP and the only thing said is: "I was able to connect to my Google Talk account (Jabbin 2.0 also adds support for SSL connections), but most of the time I was unable to use VoIP with other contacts that were using the official Google Talk client or Jabbin 2.0, because Jabbin crashed. Twice during my tests I was able to see Google Talk crash too, thanks to, as far as I understand, bad requests from Jabbin."

2 sentences? What about quality of sound ? bandwith usage ? There are so many VoIP stuff to talk about, all these are covered in just 2 sentences...wow!

That's mostly a rant and not a review...

nice work Mr. Kouremenos...

#

Re:rant or review ?

Posted by: Anonymous Coward on October 20, 2006 10:51 PM
Hello Anonymous.
First of all try reading what I just found out

"A very honest review of jabbin by Nikos Kouremenos, which we totally agree with." from the Jabbin website.
<a href="http://www.jabbin.com/int/2006/10/20/jabbin-reviewed-on-linuxcom/" title="jabbin.com">http://www.jabbin.com/int/2006/10/20/jabbin-revie<nobr>w<wbr></nobr> ed-on-linuxcom/</a jabbin.com>

Mr. Kouremenos is a developer for another jabber client, gajim (<a href="http://www.gajim.org/dev.php?lang=en" title="gajim.org">http://www.gajim.org/dev.php?lang=en</a gajim.org>) . So we have one developer criticizing other clients and their developers...

In my Article Query I wrote clearly that I'm a developer in a open source jabber client and that Gajim was reviewed by Linux.com last year. That's not a hidden thing, it's a good thing<nobr> <wbr></nobr>:) because I know what I'm talking about.

"The review is supposed to be about VoIP"

No. The review is about Jabbin jabber client, which does VoIP as the one extra thing.

"2 sentences? What about quality of sound ? bandwith usage ? There are so many VoIP stuff to talk about, all these are covered in just 2 sentences...wow!"

I also talk about the fact of the changes in the specification, and what this means to Jabbin. I can't talk in all the review VoIP is just a feature of this client and the user is more interested in knowing if he can use this client rather than me saying that the speex codec which was just made compatible by the Google Talk official client team does this and that but the foo other codec succeeds in doing more hrats hruts.

That's mostly a rant and not a review...
One thing I failed to note was that libjingle (the open source library that Google published in sourceforge has not been updated nor bugs were fixed, nor cvs is being used there, so you can say it's dead. Moreovere GTalk official client is no more 100% compatible with libjingle [according to the main developer of Jabbin] and they replied to him and said they have no roadmap, no whatsoever about libjingle in sourceforge]

nice work Mr. Kouremenos...

Thank you very much Mr. Anonymous, Have fun

#

Coccinella

Posted by: Anonymous Coward on October 20, 2006 11:35 PM
IMO a better solution for VoIP is <a href="http://hem.fyristorg.com/matben/" title="fyristorg.com">Coccinella</a fyristorg.com>:
* Support for Jingle (instead of the obsolete TINS)
* Support for Jingle IAX (Speex will be probably adde in the future)
* A Tcl/tk application that is more beautiful than several Qt applications (it helps that Coccinella can use tileqt, native Aqua, native Windows, amonst others, of course<nobr> <wbr></nobr>;-) )
* Jingle video is planned

#

Re:Coccinella

Posted by: Administrator on October 21, 2006 05:55 AM
Indeed. Coccinella is a good client, but TK looks really baaaad in GNU/Linux among other things.

#

Re:how about psi-jingle?

Posted by: Anonymous Coward on October 21, 2006 03:06 AM
The libjingle code from Psi (the same that Jabbin later backported to their project) has been in the mainline branch for quite a while now with a<nobr> <wbr></nobr>./configure switch. We haven't been enabling it by default because we don't believe it's mature enough yet, particularly as the protocol isn't settled on the Jingle spec yet (libjingle implements something similar but different, confusingly) and as such compatability is likely to break between clients (the latest Google Talk client, for example, is no longer compatible with either Psi or Jabbin). As you observe, Psi is one of the clients known for it's stability, and we're not happy yet shipping out default builds which might not work ideally, as the voip builds of Psi and its derivatives like Jabbin don't seem to yet. It's there and easily available though for anyone who wants to try it.<nobr> <wbr></nobr>/Kev

#

Yessssss!

Posted by: Administrator on October 20, 2006 08:38 AM
Jabbin's user interface is mostly a copy of the interface of Psi, a client that is notorious for having one of the worst UIs of any IM clients.


[20:22:32] <halr9000> 'a client that is notorious for having one of the worst UIs of any IM clients.'


[20:23:39] <Justin Karneges> yesssss!


[20:23:48] <halr9000> we win!!


[20:24:06] <halr9000> Justin, your years of effort at UI design have FINALLY paid off



--hal-the-psi-webmaster

#

how about psi-jingle?

Posted by: Administrator on October 20, 2006 12:33 PM
I have used psi-jingle since long and it works really well..and i dont think there has been any development on it after december last..wonder why<nobr> <wbr></nobr>:-/

#

Thanks

Posted by: Administrator on October 21, 2006 02:56 AM
Thanks Nikos Kouremenos for the article,


BOCQUET Ludovic

Jabbin Team


<a href="http://www.jabbin.com/" title="jabbin.com">http://www.jabbin.com/</a jabbin.com>

#

UI efforts

Posted by: Administrator on October 21, 2006 06:35 PM
Thanks Nikos for the review, i'm personally agree with almost all your comments but not with the comment when you say "Psi, a client that is notorious for having one of the worst UIs of any IM clients" i think that the psi team have done a lot of efforts in this issue, and i'm comfortable with the IU, yes i know that several improvements can be done in order to make it more user-friendly. We have to improve the usability and make the jabbin installation a easy process for any user can enjoy. We have working in more features with VoIP.

Regards.
Emilio C.

Jabbin Team (spain)
ecasbas@jabber.org

#

This story has been archived. Comments can no longer be posted.



 
Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya