[asterisk-bugs] [Asterisk 0014534]: Chan Alsa reports that the audio device is busy when using Pulseaudio

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jun 25 13:51:26 CDT 2009


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14534 
====================================================================== 
Reported By:                obnauticus
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   14534
Category:                   Channels/chan_alsa
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-02-23 17:20 CST
Last Modified:              2009-06-25 13:51 CDT
====================================================================== 
Summary:                    Chan Alsa reports that the audio device is busy when
using Pulseaudio
Description: 
I have recently installed pulseaudio on my system with alsa, aplay -Dpulse
[a wave file] seems to work through pulseaudio, however asterisk doesn't
want to function with it, instead it consistently says the card is in use.

Whenever I try to load the module chan_alsa Asterisk CLI gives me the
following error:

asterisk*CLI> module load chan_alsa.so
[2009-02-23 15:07:10] ERROR[8569]: chan_alsa.c:368 alsa_card_init:
snd_pcm_open failed: Device or resource busy
[2009-02-23 15:07:10] ERROR[8569]: chan_alsa.c:368 alsa_card_init:
snd_pcm_open failed: Device or resource busy
[2009-02-23 15:07:10] ERROR[8569]: chan_alsa.c:486 soundcard_init: Problem
opening alsa I/O devices

Here are the users who are currently accessing my sound devices:

(~)-(root at asterisk)--> fuser /dev/snd/* /dev/dsp /dev/snd
/dev/snd/controlC0:   3250
/dev/snd/pcmC0D0c:    3250m
/dev/snd/pcmC0D0p:    3250m
(~)-(root at asterisk)--> ps aux | grep 3250
root      3250  0.6  1.7   8108  2812 pts/1    S+   00:04   6:03
pulseaudio

My overall goal and reasoning for installing pulseaudio was to have
mpg123-alsa be able write to the output on my sound card (speaker out)
while I am listening to the audio from the radio's output on asterisk in
real time (i.e. line-in on the sound card). The best solution I found which
was an Abstraction layer which controlled access to the audio devices, this
would make it so I could have access read from the card's input, and have
mpg123-alsa write to the output. However, Asterisk keeps saying the device
is busy.
====================================================================== 

---------------------------------------------------------------------- 
 (0106990) qwell (administrator) - 2009-06-25 13:51
 https://issues.asterisk.org/view.php?id=14534#c106990 
---------------------------------------------------------------------- 
Per pulseaudio folks, the issue appears to be with you not using "default"
as the sound device in /etc/asterisk/alsa.conf.  If you are using
"default", then it is likely an issue in your alsa setup.

If you get past the error on snd_pcm_open, then we can look at it further. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-25 13:51 qwell          Note Added: 0106990                          
2009-06-25 13:51 qwell          Status                   new => resolved     
2009-06-25 13:51 qwell          Resolution               open => no change
required
2009-06-25 13:51 qwell          Assigned To               => qwell           
2009-06-25 13:51 qwell          Status                   resolved => closed  
======================================================================




More information about the asterisk-bugs mailing list