> > > Ouch ... error while writing audio data: : Broken pipe > > > > If you are talking about the Ouch message, yes lots of people have seen > > the error and its usually the result of some misconfiguration in one of > > your files (likely zapata.conf). > > Correct me if I'm wrong, but isn't that message from mpg123 itself? It > appears in the binary (via strings), and I've seen it at non-asterisk > times too. AFAIK it comes up whenever the parent application (asterisk > in this case) quits without closing it properly (hence, "broken > pipe"). > > As such, this means that the above error simply shows that asterisk > crashed (which they presumably already knew), and has nothing to do > with the problem itself...
The above is one case, however there are lots of other cases where asterisk is still running, the Ouch messages continuously scrolls, and killing asterisk with a -9 becomes necessary. Try misconfiguring a PRI and see what you get. ;) Rich _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
