[mpg123-devel] [ mpg123-Bugs-3406214 ] using mpg123 as a streaming source for Asterisk, stream dies

[SourceForge.net <no...@so...>]

Bugs item #3406214, was opened at 2011-09-08 08:45
Message generated for change (Tracker Item Submitted) made by luckman212
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=733194&aid=3406214&group_id=135704

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mpg123
Group: 1.13.3
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Luke H (luckman212)
Assigned to: Nobody/Anonymous (nobody)
Summary: using mpg123 as a streaming source for Asterisk, stream dies

Initial Comment:
Hi guys,
I filed a bug to the Asterisk team around 8 months ago and it hasn't gotten too much attention (none really) so I figured I'd ask here.  I am pretty sure this is some kind of Asterisk bug but -- maybe it's actually a problem with mpg123, not sure!  The details of the bugreport can be viewed here: 
https://issues.asterisk.org/jira/browse/ASTERISK-17474

Basically to sum up what happens is that using mpg123 to pipe in streaming audio (mp3 source) for a music-on-hold channel in Asterisk 1.8.  Everything starts off great, but as soon as Asterisk's musiconhold module (res_musiconhold.so) gets reloaded -- which happens quite often when making configuration changes -- the stream dies.  Normally when that module reloads, it finds the PID of the running mpg123 instance and kill -9s it, and then restarts it.  This all happens but for some reason the newly spawned instance stops streaming, doesn't receive packets anymore (I have seen this via tcpdump trace).  

The interesting thing is that the non-streaming (straight mp3 playback without using mpg123) music-on-hold sources continue to work in this case, only the mpg123 streams are going dead.  So there is a chance maybe that this is some kind of problem in mpg123 itself.  Anyway if any of the developers here have any idea why this might be happening please comment!  thank you so much!

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=733194&aid=3406214&group_id=135704