[asterisk-bugs] [Asterisk 0018800]: Res_musiconhold Kills Mpg123 Upon Initial Start or Reload if a Streaming Source Defined

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18800 
====================================================================== 
Reported By:                vmikhelson
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18800
Category:                   Resources/res_musiconhold
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.2.3 
JIRA:                       SWP-3141 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-02-12 17:34 CST
Last Modified:              2011-03-01 01:14 CST
====================================================================== 
Summary:                    Res_musiconhold Kills Mpg123 Upon Initial Start or
Reload if a Streaming Source Defined
Description: 
Added a streaming source to MOH. Static MOH works fine, streaming MOH
produces silence.

mpg123 1.13.1

Asterisk 1.8.2.3
FreePBX 2.8.1.0

Was unable to test with branch/1.8 as voicemail application locks up upon
the initial Asterisk load and consequentially prevents full system load.
====================================================================== 

---------------------------------------------------------------------- 
 (0132473) vmikhelson (reporter) - 2011-03-01 01:14
 https://issues.asterisk.org/view.php?id=18800#c132473 
---------------------------------------------------------------------- 
Preloaded res_musiconhold.so in modules.conf.

That resolved the issue.  So far I do not see any adverse effects.

I still think it is a work around, not a true solution.

-Vladimir 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-03-01 01:14 vmikhelson     Note Added: 0132473                          
======================================================================