[Asterisk-Users] Asterisk 1.0.5-BRIstuffed-0.2.0-RC5 crashes with Ouch ... error while writing audio data: : Broken pipe

[Remco Barende]

Yes, I do think the segfault problem is in bristuff. I just noticed 
another problem though!

If there is one ongoing conversation and a new call is coming in, as soon 
as the new call is answered, the call that was going on goes dead on one 
end (the other party can hear the person callingfrom the * end 
but the reverse audio is not transmitted).

I think these are bugs in bristuff RC5.



On Mon, 31 Jan 2005, Lubomir Christov wrote:

> If the problem is in mpg123 than way just not to replace it?
> Here is one very good example how to do it:
> http://www.voip-info.org/wiki-Asterisk+mpg123+faking+it
>
> but I think that the problem maybe is coming from the BRIstuffed * - the 
> patches and etc.
>
> Lubo
>
>
> ---------
> AppRadius Project: Full RADIUS AAA support for Asterisk PBX
> http://appradius.minitelecom.org/
> ---------
>
>
>
>
> Remco Barende wrote:
>> On Sun, 30 Jan 2005, Martin List-Petersen wrote:
>> 
>>> Citat Remco Barende <asterisk at barendse.to>:
>>> 
>>>> I have Asterisk 1.0.5-BRIstuffed-0.2.0-RC5 up and running. Everything
>>>> seems to be running fine but after some time asterisk just goes crazy
>>>> (even withouth any incoming or outgoing call activity perviously).
>>>> 
>>>> If I leave the box up for some time * goes haywire and the console is
>>>> flooded with this message:
>>>> Ouch ... error while writing audio data: : Broken pipe
>>>> 
>>>> At that time I can see that there are multiple instances of mpg123 
>>>> active.
>>>> 
>>>> The solution to this problem is to kill-9 mpg123, do the same for *,
>>>> unload the modules and then load the modules again and start 
>>>> asterisk. If
>>>> I do not unload re-load the modules I cannot access the ISDN line nor 
>>>> do
>>>> incoming calls work.
>>>> 
>>>> I really don't know where to look for this problem. Is it possible to
>>>> completely disable music on hold? Asterisk combined mpg123 is causing
>>>> nothing but problems anyway, the current stable still leaves 
>>>> abandoned
>>>> mpg123 processes.
>> 
>> 
>> It doesn't work :( Asterisk doesn't go haywire flooding the console but 
>> now simply bombs out with :
>> 
>> *CLI>
>> Segmentation fault
>> 
>> I guess that qualifies it as a bristuff bug?
>> _______________________________________________
>> 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
>> 
>> 
> _______________________________________________
> 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
>