I am calling into an asterisk machine using console/dsp initially I head the voice just fine on the speaker, after about 30 seconds or so I get the error: [Dec 31 09:51:36] NOTICE[11724]: chan_alsa.c:642 alsa_write: Error -11 on write << Hangup on console >> I am running alsa 1.4.22 , dahdi 2.0.0 and dahdi_dummy. centos 5.2 kernel 2.6.18-91.1.13 Of course the call hangs up at that point. What might be wrong here? Jerry
On Wednesday 31 December 2008 08:54:56 Jerry Geis wrote:> I am calling into an asterisk machine using console/dsp > initially I head the voice just fine on the speaker, after about 30 > seconds or so > I get the error: > > [Dec 31 09:51:36] NOTICE[11724]: chan_alsa.c:642 alsa_write: Error -11 > on write > << Hangup on console >> > > I am running alsa 1.4.22 , dahdi 2.0.0 and dahdi_dummy. > centos 5.2 kernel 2.6.18-91.1.13 > > Of course the call hangs up at that point. > What might be wrong here?Error 11 is "Resource temporarily unavailable", so it sounds like something else is accessing the sound port. Check the other services running on this machine. For example, are you running a desktop environment that might send sounds to the speaker? -- Tilghman
> > Error 11 is "Resource temporarily unavailable", so it sounds like something > else is accessing the sound port. Check the other services running on this > machine. For example, are you running a desktop environment that might > send sounds to the speaker? > >Tilghman, I am not even running the desktop environment on this box. Nothing else is really running except asterisk on this box. Where else might I look? Jerry
On Wednesday 31 December 2008 10:07:01 Jerry Geis wrote:> > Error 11 is "Resource temporarily unavailable", so it sounds like > > something else is accessing the sound port. Check the other services > > running on this machine. For example, are you running a desktop > > environment that might send sounds to the speaker? > > I am not even running the desktop environment on this box. > Nothing else is really running except asterisk on this box. > Where else might I look?I spent some time looking at this and I may have identified a possible problem. Please try the patch located here: http://bugs.digium.com/view.php?id=14153 -- Tilghman