[Asterisk-Users] ALSA Sound dies after a while

[venkatesh.seshasayee at wipro.com]

It could be a case of the application trying to send more data than what
the sound driver can handle.
For debugging purposes, in chan_oss.c:181, you could try invoking
sleep() for a few milliseconds, without returning -1 right away. (of
course, for sleep(), the granularity is seconds, so you'd have to use
usleep() ).

     venkat



> -----Original Message-----
> From: asterisk-users-admin at lists.digium.com [mailto:asterisk-users-
> admin at lists.digium.com] On Behalf Of Juan Pablo Morales
> Sent: Thursday, 4 March 2004 6:20 PM
> To: asterisk-users at lists.digium.com
> Subject: [Asterisk-Users] ALSA Sound dies after a while
>
> I am currently running an asterisk server locally on a PC, to see what
> kinds of things it can do. The output device is the sound system, via
> alsa. It starts perfectly and plays the first sounds but after a
minute
> or to the sound dies and several messages
> Mar  3 21:30:29 WARNING[180236]: chan_oss.c:272 sound_thread: Failed
to
> write sound
> Mar  3 21:30:29 WARNING[180236]: chan_oss.c:181 send_sound: Unable to
> read output space
>
> are issued.
> This looks like an alsa lock. I have tried to run the system both with
> and without esd. When running lsof for /dev/dsp only asterik and it's
> child processes are using it.
>
> Has anybody experienced this?
>
> thanks in advance
> Juan Pablo Morales
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.