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

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Sep 18 17:52:12 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
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:                     feedback
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:              
====================================================================== 
Date Submitted:             2008-08-01 14:27 CDT
Last Modified:              2008-09-18 17:52 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...
====================================================================== 

---------------------------------------------------------------------- 
 (0092683) urzedo (reporter) - 2008-09-18 17:52
 http://bugs.digium.com/view.php?id=13222#c92683 
---------------------------------------------------------------------- 
Hi guys,

I believe I could find a way to simulate this issue.

In a fresh Asterisk 1.4.21.2, create some MOH classes in musiconhold.conf
and start Asterisk. If you issue a "moh show classes" command, you should
see the classes in memory.

Now, make any change in musiconhold.conf file, such as adding a new class.
Back to Asterisk CLI, issue "moh reload" command and after that "moh show
classes". If you have added a new class, you will see that only this new
class is in memory, while the other classes (which still exist in
musiconhold.conf) have gone.

Issue "moh reload" command again and you will see that the former classes
are back to memory, but the last created one is not there anymore. And so
on...

Please let me know whether you can simulate it or not.

Regards! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-18 17:52 urzedo         Note Added: 0092683                          
======================================================================




More information about the asterisk-bugs mailing list