This document describes the procedure you use to change the default
Music On Hold (MOH) directory. The default directory where the audio files are
dropped is C:\Program Files\cisco\MOH\DropMOHAudioSourceFilesHere. Use this
folder to drop the wav file. This dropped wav file is converted into five codec
files, together with an XML file. All six files are stored in the
Cisco recommends that you have knowledge of Cisco CallManager.
The information in this document is based on Cisco CallManager version
The information in this document was created from the devices in a
specific lab environment. All of the devices used in this document started with
a cleared (default) configuration. If your network is live, make sure that you
understand the potential impact of any command.
Technical Tips Conventions for more information on document
Complete these steps in order to change the default MOH
Create a new directory.
In this example, the new MOH directory is located at
C:\NewDropMOHAudioSourceFileHere. See arrow A in Figure
Figure 1—New Default MOH Drop Directory
Right-click the new MOH directory, and click
Click the Security tab. See arrow A in Figue
Figure 2—Directory Security Setting - 1
Click arrow B. See Figure 2.
The Select Users Or Groups window appears. See Figure 3.
Figure 3—Select Users Or Groups
Select CCMCDR, CCMService, CCMServiceRW, and
CCMUser. See arrow B in Figure
Click Add . See arrow A in Figure 3.
Click OK. Figure 4
Figure 4—Set User Permissions
Assign these added users with appropriate permissions. In order to
do this, check Modify, Read & Execute, List Folder Contents, Read
and Write in the Permissions section for each individual user. See
arrow A in Figure 4.
Click Apply. See arrow B in Figure 4.
Click OK. See arrow C in Figure 4.
Choose Start > Programs > Cisco CallManager
<version number> > CallManager
Click Service in the menu bar and select
Service Parameters. See Figure
Figure 5—Selection of Service Parameters
Select the server name from the Server drop-down list. See arrow A
in Figure 6.
Figure 6—Service Parameters Configuration -
Select Cisco MOH Audio Translator from the Service
drop-down list. See arrow B in Figure
Enter the new directory, which you create in step one, in the MOH
Source Directory field. See arrow A in Figure
Figure 7—Service Parameters Configuration -
Click Update. See arrow B in Figure 7.
Choose Start > Programs > Administrative Tools >
Right-click Cisco MOH Audio Translator, and select
Stop. See Figure 8.
Right-click the Cisco MOH Audio Translator, and
select Start after it stops.
Add an audio file in the new folder.
In two to three seconds, this file is converted to five wav files,
together with an XML file, in this directory:
Note: If the translated files are not found in this location, check in the
folder specified in Default TFTP MOH File Path in the Cisco
CallManager publisher server.
Note: In order to find the Default TFTP MOH File Path, go
to the Cisco CallManager Administration Web page, then
Services> Service Parameters. Choose the
publisher server, and click Cisco MOH Audio Translator
The suffixes for these six files are:
For example, if the audio file is named as atest.wav, these six
converted files are named as atest.alaw.wav, atest.au, atest.g729.wav,
atest.ulaw.wav, atest.wb.wav and atest.xml respectively. See
If you experience a bad quality or no audio for Music on Hold (MOH)
after the conversion procedure mentioned in this document, make sure that the
music audio source files comprise .wav files in
one of these formats:
After you insert the MOH audio file into the Cisco Unified
Communications Manager 6.X server, the music on hold plays dead air. The file
is uploaded and converts fine, but dead air is all that is heard.
This issue can occur if the audio files are not uploaded to all the
servers in the cluster. With Cisco Unified Communications Manager 6.X, before
you configure a MoH audio source, the .wav formatted audio source file must be
uploaded to every MoH server within the cluster. In order to upload the audio
source file, you must navigate to the Unified CM Administration interface on
every MoH server within the cluster and use the upload file function on the MoH
Audio File Management page. You must perform this step for every audio source
file. Only after the audio source file is uploaded to all MoH servers in the
cluster can the audio source be assigned to an MoH Audio Stream Number and
configured as a MoH audio source.
If MOH does not work after you upload a new audio source file, restart
the IPVMS service in order to resolve the issue.