My call sign is OZ1TNB.
I am living in Aalborg, Denmark.
IT & Telestyrelsen har tilsyneladende lavet en oversigt over det meste af hvad de har, der er relevant for radioamatører, her.
Frekvens-registret kan gennemsøges her.
Danske fora findes som en nyhedsgruppe, EDR's medlems-forum, et webforum og sikkert flere? For radiospejd er der dette forum.
There is a fine list of software for Ubuntu, and what the debian packages are named, made by the group "Ubuntu Hams Team".
When searching the Internet, I cannot (as of December 2010) find no pre-packaged clients for EchoLink, ready to be installed on Ubuntu. So I wonder if people are using other systems for voice-over-IP and remote control of HAM radio transceivers, or just avoiding that sort of experiments on Linux. Or is there a lot of people compiling apps like QTEL from the SvxLink project?
Or is it working nicely to take the RPM packages and install them via the package converter "Alien"? (Man page for Alien)
QTEL seems to be the only graphical client available for Linux. Svxlink has an app (svxlink-server) that acts as an EchoLink server that can connect to radio hardware, and is run from a command line or as a system daemon. Installation instructions are at http://sourceforge.net/apps/trac/svxlink/wiki/InstallationInstructions .
If the wiki pages does not answer your question, search the mailing list archive.
Installation via 'alien'
I tried to download the newest four relevant packages from rpmfind.net, and convert them with the command "alien -d -k *.rpm" (run in a directory with the downloaded RPM files). The four packages is probably the same as:
http://ftp.crc.dk/fedora/linux//releases/14/Everything/i386/os/Packages/qtel-0.11.2-5.fc14.i686.rpm
When installing the newly converted debian packages, with "Ubuntu Software Center (opening the files with the graphical file manager in Ubuntu 10.10), it shows an error before the installation is started, like "Sorry, 'qtel' is not available for this type of computer (i386).". But all packages installs without additional errors. 'qtel' can be started, and the GUI works fine (I did not try to log in). Note: I install them in the order listed above!
These packages are probably the release version from April 2009. The four debian packages from the conversion are attached at the bottom.
Audio input/output: 'qtel' gives an error on the command line: "open audio device failed: No such file or directory", when qtel is set up to use the OSS (Open Sound System) device file /dev/dsp .
PulseAudio which is the default audio system in many of the popular Linux distributions like Ubuntu and Fedora, has a wrapper command that emulates OSS, called padsp. See
http://linux.die.net/man/1/padsp and
http://www.pulseaudio.org/wiki/PerfectSetup#OSSApplications
Unfortunately qtel and padsp does not seem to work together, as it gives the same error "open audio device failed: No such file or directory".
Update: Oh, an other person reported this same error. The development has shifted to implement the ALSA system instead of the "ancient" OSS. With ALSA, the aduio can go through PulseAudio, and in this way Qtel can co-exist with other applications making sounds on an Ubuntu desktop. On the mailin list, a few people have looked at how to release a debian package with ALSA support and bug fixes from since the 2009 release.
CQInet, the other project with a command line app for Echolink
http://cqinet.sourceforge.net/ is the project the wthe app "EchoLinux" and something for conference calls with VoIP.
http://sourceforge.net/apps/mediawiki/cqinet/index.php?title=Special:AllPages
Related links
http://en.wikipedia.org/wiki/Echolink
Protocol info: http://davidmpye.co.uk/node/23
http://ubuntu-virginia.ubuntuforums.org/showpost.php?p=9266233&postcount=10
http://nsayer.blogspot.com/2009/01/echolink-and-spirit-of-amateur-radio.html
terminal-based "GUI" for the EchoLinux app: http://www.adsb.co.uk/software/echolinux/