[Home]

Summary:ASTERISK-01150: Microphone doesn't work with ALSA
Reporter:antonverburg (antonverburg)Labels:
Date Opened:2004-03-04 05:56:29.000-0600Date Closed:2004-09-25 02:52:18
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Using Asterisk in Console-mode, my microphone works fine with OSS. Also, in Alsa-> OSS emulation, it works (I am only getting a warning like: Mar  4 11:23:51 WARNING[245776]: chan_oss.c:685 oss_indicate: Don't know how to display condition -1 on OSS/dsp  and Mar  4 11:30:08 WARNING[245776]: chan_oss.c:526 soundcard_writeframe: Error reading output space )
But as soon as I am trying to use chan_alsa, the micropone refuses working. With arecord, I can get sound at hw:0,0, but asterisk can't. Using fuser /dev/dsp tells me nothing but asterisk is using the audiodevice. When using asterisk with chan_alsa, I get also an warning, and can't hear the audio on Clientside nor when using the echo-test funcion of Asterisk;
Mar  4 11:31:46 WARNING[245776]: chan_alsa.c:779 alsa_indicate: Don't know how to display condition -1 on ALSA/hw:0,0


****** ADDITIONAL INFORMATION ******

I am getting this error with CVS stable and unstable version ( v1-0_stable and CVS-03/04/04-10:33:49) at Redhat 8.0 and Fedora Core 1.

Using kernel 2.4.18-14 (RH8.0) and 2.4.22-1.2174.nptl (FC1)



Using Alsa 0.9.6-1 (RH8.0) and Alsa 1.0.2-2 (FC1)

At Fedora Core 1 I changed the set_*_near funcions to set_* in order to be able to use chan_alsa


modules.conf (for use of alsa);

[modules]
autoload=yes
noload => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
noload => app_intercom.so
load => chan_modem.so
load => res_musiconhold.so
load => chan_alsa.so
noload => chan_oss.so

globally

[global]
chan_modem.so=yes
Comments:By: antonverburg (antonverburg) 2004-03-04 06:01:21.000-0600

Hm, I forgot to tell that I am using sweex-soundcards, with the CMedia with CMI8738 chipset.

By: antonverburg (antonverburg) 2004-04-02 02:33:54.000-0600

This should be fixed by the patch for bug 1297

By: Mark Spencer (markster) 2004-04-04 17:31:34

Fixed in CVS