title: “EchoLink on Linux: Setting Up SvxLink and QTel Across Distros”

author: “Joe Hallford (W4DXR)” date: 2026-10-27 categories: [“Amateur Radio”, “Linux”, “Voice Over IP”] tags: [“EchoLink”, “SvxLink”, “QTel”, “Debian”, “Ubuntu”, “Arch Linux”, “Audio”] description: “A complete guide to configuring EchoLink on Linux using SvxLink and QTel, with critical fixes for ALSA direct-hardware mapping and audio resampling bottlenecks.”

EchoLink on Linux: Setting Up SvxLink and QTel

Connecting to the global EchoLink network from a Linux workstation or dedicated node machine offers a powerful alternative to proprietary desktop software. Whether you want to spin up a standalone simplex node using SvxLink or connect as a user client via QTel, the Linux audio stack gives you total control-once you navigate a few audio server hurdles.

1. SvxLink vs. QTel: Choosing Your Tool

• QTel (Qt EchoLink Client): The classic user interface client. Perfect for connecting your PC headset or soundcard interface to remote EchoLink nodes or conferences.
• SvxLink: An advanced, highly configurable voice services engine. Commonly used to build repeater controllers, link nodes, and automated EchoLink gateways.

2. Installation Across Distributions

On Debian / Ubuntu

Both packages are available directly in the standard Debian and Ubuntu repositories:

sudo apt update
sudo apt install svxlink qtel

On Arch Linux

Arch users can install QTel and SvxLink through the Arch User Repository (AUR):

yay -S svxlink qtel

3. Common Distro Pitfalls and Troubleshooting

A. Audio Subsystem Bottlenecks (PipeWire and PulseAudio Conflicts)

Modern Linux distributions default to PipeWire or PulseAudio to manage system sound. However, amateur radio soundcard interfaces (like a SignaLink USB or CM108-based USB audio fob) require exact sample rates (typically 48kHz or 8kHz). When PulseAudio or PipeWire attempts to dynamically resample audio streams, it introduces latency and phase distortion that ruins DTMF tone decoding and digital packet audio.

• The Fix: Bypass the sound server entirely by configuring ALSA direct-hardware mapping. In your SvxLink configuration file (/etc/svxlink/svxlink.conf), explicitly specify your USB audio device using the plughw or hw parameters rather than default aliases:

[Audio]
AUDIO_DEV=alsa:plughw:CARD=CODEC,DEV=0
AUDIO_CHANNEL=0

To find your exact card name, run arecord -l in your terminal.

B. DTMF Tone Failures

If remote nodes fail to recognize your DTMF touch-tones when connecting through QTel or SvxLink:

• Check Input Levels: Ensure your microphone or virtual audio cable input isn’t clipping. Run alsamixer in the terminal, select your USB audio card, and verify that capture gain is set moderately (around 50-70%) rather than maxed out.

alsamixer

Conclusion

Running EchoLink on Linux turns your station or shack computer into a robust VoIP node. By locking down direct ALSA hardware access and bypassing audio server resampling, you’ll ensure crystal-clear audio and reliable DTMF control across Debian, Ubuntu, and Arch.