07.06.2014 Views

2 - Raspberry PI Community Projects

2 - Raspberry PI Community Projects

2 - Raspberry PI Community Projects

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Since the IRC protocol is very old, many clients are available to cater for many<br />

user groups; examples include XChat and Smuxi (graphical clients based on<br />

GTK+), Irssi (text mode), Erc (integrated to Emacs), Chatzilla (in the Mozilla<br />

soware suite), and so on.<br />

QUICK LOOK<br />

Video conferencing with<br />

Ekiga<br />

Ekiga (formerly GnomeMeeting) is the most prominent application for Linux<br />

video conferencing. It is both stable and functional, and is very easily used<br />

on a local network; seing up the service on a global network is much more<br />

complex when the firewalls involved lack explicit support for the H323 and/or<br />

SIP teleconferencing protocols with all their quirks.<br />

If only one Ekiga client is to run behind the firewall, the configuration is rather<br />

straightforward, and only involves forwarding a few ports to the dedicated<br />

host: TCP port 1720 (listening for incoming connections), TCP port 5060 (for<br />

SIP), TCP ports 30000 to 30010 (for control of open connections) and UDP<br />

ports 5000 to 5013 (for audio and video data transmission and registration to<br />

an H323 proxy).<br />

When several Ekiga clients are to run behind the firewall, complexity increases<br />

notably. An H323 proxy (for instance the gnugk package) must be set up, and<br />

its configuration is far from simple.<br />

Configuring the Server Setting up a Jabber server is rather straightforward. After installing<br />

the ejabberd package, executing dpkg-reconfigure ejabberd will allow customizing the default<br />

domain, and create an administrator account. Note that the Jabber server needs a valid<br />

DNS name to point at it, so some network administration can be required beforehand. The Falcot<br />

Corp administrators picked jabber.falcot.com for that purpose.<br />

Once this initial set up is over, the service configuration can be controlled through a web interface<br />

accessible at hp://jabber.falcot.com:5280/admin/. The requested username and password<br />

are those that were given earlier during the initial configuration. Note that the username<br />

must be qualified with the configured domain: the admin account becomes admin@jabber.<br />

falcot.com.<br />

The web interface removes the need to edit a configuration file, but does not always make the<br />

task easier, since many options have a peculiar syntax that needs to be known. /usr/share/<br />

doc/ejabberd/guide.html is therefore a recommended read.<br />

Jabber Clients GNOME provides Empathy (in the similarly-named package), a minimalist<br />

client that integrates in the notification area of the desktop (on the top-right corner in the default<br />

GNOME configuration). It also supports many instant messaging protocols beyond Jabber.<br />

KDE provides Kopete (in the package of the same name).<br />

Chapter 13 — Workstation<br />

367

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!