[Asterisk-Users] Yuck! Error in buffer handling

[mattf]

That's all musiconhold mp3 stuff(mpg123). If you deactivate musiconhold then
it goes away.

The inherant problems with mpg123 can rarely cause crashes and very often
cause lots of mpg123 processes running on your machine. I got rid of it and
just use half-hour-long gsm files for on hold extensions now
[playback(long)].

I even re-encoded my mp3 files to use non-flexible bitrate but it didn't
help in the long run.

Now I have it MoH deactivated and no more errors.

MATT---


-----Original Message-----
From: marrandy [mailto:marrandy at chaossolutions.org]
Sent: Thursday, December 11, 2003 12:13 PM
To: asterisk-users at lists.digium.com
Subject: [Asterisk-Users] Yuck! Error in buffer handling


Hello.

Is this normal.  Or does it mean there is a problem ?

-------------------------
stop now
Beginning asterisk shutdown....
Executing last minute cleanups
  == Destroying any remaining musiconhold processes
Yuck! Error in buffer handling...: Connection reset by peer
Yuck! Error in buffer handling...: Broken pipe
Yuck! Error in buffer handling...: Broken pipe
Asterisk cleanly ending (0).
-------------------------


Also, since I recently CVS upgraded, I'm also seeing this :-

--------------------------
Asterisk Ready.
*CLI> Warning, flexibel rate not heavily tested!
mpg123: Can't rewind stream by 11 bits!
Warning, flexibel rate not heavily tested!
mpg123: Can't rewind stream by 39 bits!
big_values too large!
big_values too large!
mpg123: Can't rewind stream by 733 bits!
mpg123: Can't rewind stream by 23 bits!
big_values too large!
Blocktype == 0 and window-switching == 1 not allowed.

*CLI> show version
Asterisk CVS-12/10/03-11:49:50
------------------------------
Just curious.

Regards...Martin
-- 
If graphics hackers are so smart, why can't they get the bugs out of
fresh paint?

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users