[asterisk-bugs] [Asterisk 0013222]: Asterisk commands "moh reload" or "reload res_musiconhold.so" causes MOH not to work properly

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13222 
====================================================================== 
Reported By:                urzedo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13222
Category:                   Resources/res_musiconhold
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 unable to reproduce
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-08-01 14:27 CDT
Last Modified:              2008-10-06 11:23 CDT
====================================================================== 
Summary:                    Asterisk commands "moh reload" or "reload
res_musiconhold.so" causes MOH not to work properly
Description: 
SIP peer A is calling SIP peer B. When A put B on hold, B starts to listen
to the MOH configured in the parameter "mohsuggest" of the peer A. If I
look at Asterisk's verbose, I can see "Started music on hold..." and
"Stopped music on hold..." stuff while peer A press the hold button.

During the above conversation, if someone runs "moh reload" or "reload
res_musiconhold.so", than peer B is not able anymore to listen to the MOH
when A press the hold button. In the Asterisk's verbose, I cannot see
"Started music on hold..." and "Stopped music on hold..." anymore.

If "moh reload" or "reload res_musiconhold.so" commands are executed
again, than everything starts to work again. And so on...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-06 11:23 blitzrage      Resolution               open => unable to
reproduce
======================================================================