PDF(72.9 KB) View with Adobe Reader on a variety of devices
ePub(71.9 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(66.0 KB) View on Kindle device or Kindle app on multiple devices
Updated:July 29, 2016
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to download a Music on Hold (MoH) file from Cisco Call Manager server.
Contributed by Sankalp Jain, Cisco TAC Engineer.
Cisco recommends that you have knowledge of these topics:
Simple File Transfer Protocol (SFTP) Server Setup
Access to Command line interface (CLI) of Call Manager
The information in this document is based on these software and hardware versions:
CUCM Release 10.5.2.11900-3
Freeftpd SFTP server (Third Party)
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.
From Call Manager 5.x onwards, MoH file needs to be uploaded through CCMAdmin Portal on each node where the file is required, however, there is no provision to download this file from the web interface of the Call Manager .
At times when a specific MoH file is required and is not available elsewhere with the Administrator .
For example, a recorded announcement MoH file is available on one cluster and same MoH is required to be played on another cluster, but the required MoH file is not available with the administrator or the administrator who had the file earlier has left the company and the only way to get the same MoH file, is through the Call Manager. In such scenarios, this specified method to download the MoH file comes very handy.
1. Establish a Secure Shell (SSH) connection to the Call Manager, where the MoH file is uploaded.
SANKALJA-M-H02V:tftpboot sankalja$ ssh email@example.com firstname.lastname@example.org's password: Command Line Interface is starting up, please wait ...
Welcome to the Platform Command Line Interface
VMware Installation: 8 vCPU: Intel(R) Xeon(R) CPU X7560 @ 2.27GHz Disk 1: 120GB, Partitions aligned 8192 Mbytes RAM
2. Check the list of all MoH files available on the server with this command:
file get activelog /mohprep/<name of the MoH file>
To download all MoH files, you can use this command:
file get activelog /mohprep/*.wav
To download all MoH files of a specific codec, use:
file get activelog /mohprep/*.<codecname>.wav
admin:file get activelog /mohprep/SampleAudioSource.g729.wav Please wait while the system is gathering files info ...done. Sub-directories were not traversed. Number of files affected: 1 Total size in Bytes: 332600 Total size in Kbytes: 324.8047
Type Y to proceed.
Would you like to proceed [y/n]? y
Enter Sftp server's details
SFTP server IP: 10.196.121.21 SFTP server port : User ID: cisco Password: ***** Download directory: /
The authenticity of host '10.196.121.21 (10.196.121.21)' can't be established. RSA key fingerprint is 36:26:52:14:85:75:2f:90:a1:c3:c6:05:93:46:d1:ab. Are you sure you want to continue connecting (yes/no)? yes . Transfer completed.
Once the transfer of the MoH is successful, you should be able to find the MoH file in the root directory of your SFTP server.
If you come across error messages like these, it is possible that it is an issue with the SFTP server or connectivity to the SFTP server. In this case, you must verify your SFTP server’s settings and/or Connectivity to the same .
Invalid download directory specified.
The authenticity of host '10.196.121.142 (10.196.121.142)' can't be established.
Could not connect to host 10.196.120.246 on port 22.