Audio setup

From Ekiga
Revision as of 10:18, 8 July 2013 by Eugen (Talk | contribs)
Jump to: navigation, search



I cant get the sound to work!

Check that your audio subsystem is configured correctly.

You can test your actual ALSA configuration using those echo tests:

 $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE -

This will test if your sound card can record and play sounds at 8kHz.

 $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE -

This will test if your sound card can record and play sounds at 16kHz.

You should be able to hear yourself with a small delay. Be sure to have your sound levels up and capture on.

If the test fails, try running the same command with -c 2 instead of -c 1. If you hear yourself now, this fix might help you.

Choppy sound with Ekiga

From ALSA version 1.0.9, DMIX is enabled by default for soundcards that do not support several channels at the same time. The default configuration of DMIX in ALSA does not necessarily provide good results by default for VoIP applications. The solution is to directly use the soundcard preferences in the 'Audio Settings' or to redefine your "default" soundcard as described above.

Choppy sound when switching desktops or under heavy load

Nothing can be done. We suggest not using DMIX if you experience that problem. If you do not use the 'Default' soundcard in the Audio Settings, then DMIX will not be used.

Pulse Audio


Some popular distributions of GNU/Linux now ship with the sound server Pulse audio enabled by default (e.g. Ubuntu, Fedora). Pulse audio work on top of ALSA and is now part of GNOME.

In some cases, Pulse audio and Ekiga do not work well together. If you have issue with sound using Ekiga in such setup, you'll better turn off Pulse audio and use ALSA directly.

Sometimes, you just need to select the proper output with pavucontrol

We are working to fix the issue. If you're willing to give a hand:

Sound Drivers broken with Pulse Audio

Pulse audio is know to have issue with some audio card drivers. You can check if you are using one of them with this command:

 $ lsmod|grep snd

Audio tricks


The purpose of this wrapper is to put the control volumes up ( speakers... ) and stops all sounds applications automatically ( you are prompted via graphic dialog boxs to re-enable after if you want to ) when Ekiga is ringing.
That way, you will hear if you are away from your computer or if you don't have the headset on your head. When ringing stops, the script put control volumes in the proper settings for the headset ( the speakers are turned off, capture is turned on, and headphone turned on too )


- This script require : ekiga alsa alsa-utils sox inotify-tools zenity
- for debian ubuntu distros :

sudo aptitude update; sudo aptitude install ekiga alsa alsa-utils sox inotify-tools zenity

- It's designed to have a small system foot print
To avoid sound card conflicts, I use pulseaudio : with this card :

$ lspci | grep Aud
00:1b.0 Audio device: Intel Corporation 82801JD/DO (ICH10 Family) HD Audio Controller (rev 02)

If I list my controls, I have :

$ amixer -Dhw:0 | awk -F"'" '/^Simple/{print $2}'
Front Mic
Front Mic Boost
Line Boost
Mic Boost
IEC958 Default PCM
IEC958 Playback Source
Input Source
Input Source

You should use such daemons to run this script properly and to have the ability to play 2 sounds in the same time. ( a few second )


chmod +x ekiga
editor ekiga     # You need now to edit the variables on the top of the script to fit your configuration
./ekiga          # use this instead of usual ekiga binary


version 2010-07-14 20:12:46

  • mplayer workaround : require to kill it and replay the full command line later because mplayer can't be paused with SIGSTOP signal
Personal tools