01-03-2008 05:51 AM - edited 03-15-2019 08:01 AM
Does anyone know a good way to limit the number of ring tones available to users on their IP phones in a CCM5.1 system? TIA
Solved! Go to Solution.
01-03-2008 05:59 AM
Hi Steven,
Hope all is well with you this new year!
You can narrow this down to the two default rings (that are in the phone hardware) by probably just renaming the file so the phones can't find it. You could also use the process shown below to actually edit out all the rings that you don't want;
The Cisco Unified IP Phone ships with two default ring types that are implemented in hardware: Chirp1 and Chirp2. Cisco Unified CallManager also provides a default set of additional phone ring sounds that are implemented in software as pulse code modulation (PCM) files. The PCM files, along with an XML file (named Ringlist.xml) that describes the ring list options that are available at your site, exist in the TFTP directory on each Cisco Unified CallManager server.
The following sections describe how you can customize the phone rings that are available at your site by creating PCM files and editing the Ringlist.xml file:
The Ringlist.xml file defines an XML object that contains a list of phone ring types. This file can include up to 50 ring types. Each ring type contains a pointer to the PCM file that is used for that ring type and the text that will appear on the Ring Type menu on a Cisco Unified IP Phone for that ring. The Cisco TFTP server for each Cisco Unified CallManager contains this file.
The CiscoIPPhoneRinglist XML object uses the following simple tag set to describe the information:
The following characteristics apply to the definition names. You must include the required DisplayName and FileName for each phone ring type.
DisplayName defines the name of the custom ring for the associated PCM file that will display on the Ring Type menu of the Cisco Unified IP Phone.
FileName specifies the name of the PCM file for the custom ring to associate with DisplayName.
--------------------------------------------------------------------------------
Note The DisplayName and FileName fields must not exceed 25 characters.
--------------------------------------------------------------------------------
This example shows a Ringlist.xml file that defines two phone ring types:
From this doc;
Custom Phone Rings
Introducing Custom Phone Rings
Cisco Unified IP Phones ship with two default ring types that are implemented in hardware: Chirp1 and Chirp2. Cisco Unified CallManager also provides a default set of additional phone ring sounds that are implemented in software as pulse code modulation (PCM) files. The PCM files, along with an XML file (named Ringlist.xml) that describes the ring list options that are available at your site, exist in the TFTP directory on each Cisco Unified CallManager server.
You can get a copy of the Ringlist.xml file from the system using the following admin cli "file" commands:
admin:file
file list*
file view*
file search*
file get*
file dump*
file tail*
file delete*
Customizing and Modifying Configuration Files
You can modify configuration files (for example, edit the xml files) and add customized files (for example, custom ring tones, call back tones, phone backgrounds) to the TFTP directory. You can modify files and/or add customized files to the TFTP directory in Cisco Unified Communications Platform Administration, from the TFTP Server File Upload page.
Hope this helps!
Rob
01-03-2008 05:59 AM
Hi Steven,
Hope all is well with you this new year!
You can narrow this down to the two default rings (that are in the phone hardware) by probably just renaming the file so the phones can't find it. You could also use the process shown below to actually edit out all the rings that you don't want;
The Cisco Unified IP Phone ships with two default ring types that are implemented in hardware: Chirp1 and Chirp2. Cisco Unified CallManager also provides a default set of additional phone ring sounds that are implemented in software as pulse code modulation (PCM) files. The PCM files, along with an XML file (named Ringlist.xml) that describes the ring list options that are available at your site, exist in the TFTP directory on each Cisco Unified CallManager server.
The following sections describe how you can customize the phone rings that are available at your site by creating PCM files and editing the Ringlist.xml file:
The Ringlist.xml file defines an XML object that contains a list of phone ring types. This file can include up to 50 ring types. Each ring type contains a pointer to the PCM file that is used for that ring type and the text that will appear on the Ring Type menu on a Cisco Unified IP Phone for that ring. The Cisco TFTP server for each Cisco Unified CallManager contains this file.
The CiscoIPPhoneRinglist XML object uses the following simple tag set to describe the information:
The following characteristics apply to the definition names. You must include the required DisplayName and FileName for each phone ring type.
DisplayName defines the name of the custom ring for the associated PCM file that will display on the Ring Type menu of the Cisco Unified IP Phone.
FileName specifies the name of the PCM file for the custom ring to associate with DisplayName.
--------------------------------------------------------------------------------
Note The DisplayName and FileName fields must not exceed 25 characters.
--------------------------------------------------------------------------------
This example shows a Ringlist.xml file that defines two phone ring types:
From this doc;
Custom Phone Rings
Introducing Custom Phone Rings
Cisco Unified IP Phones ship with two default ring types that are implemented in hardware: Chirp1 and Chirp2. Cisco Unified CallManager also provides a default set of additional phone ring sounds that are implemented in software as pulse code modulation (PCM) files. The PCM files, along with an XML file (named Ringlist.xml) that describes the ring list options that are available at your site, exist in the TFTP directory on each Cisco Unified CallManager server.
You can get a copy of the Ringlist.xml file from the system using the following admin cli "file" commands:
admin:file
file list*
file view*
file search*
file get*
file dump*
file tail*
file delete*
Customizing and Modifying Configuration Files
You can modify configuration files (for example, edit the xml files) and add customized files (for example, custom ring tones, call back tones, phone backgrounds) to the TFTP directory. You can modify files and/or add customized files to the TFTP directory in Cisco Unified Communications Platform Administration, from the TFTP Server File Upload page.
Hope this helps!
Rob
01-03-2008 06:44 AM
Thanks Rob! HNY to you as well and all the best for 2008. Cheers!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: