Cisco Unified CallManager Features and Services Guide, Release 4.2(3)
Custom Phone Rings
Downloads: This chapterpdf (PDF - 167.0KB) The complete bookPDF (PDF - 5.71MB) | Feedback

Custom Phone Rings

Table Of Contents

Custom Phone Rings

Introducing Custom Phone Rings

RingList.xml File Format Requirements

PCM File Requirements for Custom Ring Types

Configuring a Custom Phone Ring

Where to Find More Information


Custom Phone Rings


This chapter describes how you can customize the phone ring types that are available at your site by creating your own PCM files and editing the RingList.xml file.

This chapter covers the following topics:

Introducing Custom Phone Rings

RingList.xml File Format Requirements

PCM File Requirements for Custom Ring Types

Configuring a Custom Phone Ring

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.

RingList.xml File Format Requirements

The RingList.xml file defines an XML object that contains a list of phone ring types. Each ring type contains a pointer to the PCM file that is used for that ring type and the text that will display on the Ring Type menu on a Cisco Unified IP Phone for that ring. The C:\ Program Files\Cisco\TFTPPath directory of 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:

<CiscoIPPhoneRingList>
   <Ring>
      <DisplayName/>
      <FileName/>
   </Ring>
</CiscoIPPhoneRingList>

The following characteristics apply to the definition names:

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.


Tip The DisplayName and FileName fields must not exceed 25 characters.


The following example shows a RingList.xml file that defines two phone ring types:

<CiscoIPPhoneRingList>
   <Ring>
      <DisplayName>Analog Synth 1</DisplayName>
      <FileName>Analog1.raw</FileName>
   </Ring>
   <Ring>
      <DisplayName>Analog Synth 2</DisplayName>
      <FileName>Analog2.raw</FileName>
   </Ring>
</CiscoIPPhoneRingList>


Tip You must include the required DisplayName and FileName for each phone ring type. The RingList.xml file can include up to 50 ring types.


PCM File Requirements for Custom Ring Types

The PCM files for the rings must meet the following requirements for proper playback on Cisco Unified IP Phones:

Raw PCM (no header)

8000 samples per second

8 bits per sample

ulaw compression

Maximum ring size—16080 samples

Minimum ring size—240 samples

Number of samples in the ring evenly divisible by 240

Ring starts and ends at the zero crossing.

To create PCM files for custom phone rings, you can use any standard audio editing packages that support these file format requirements.

Configuring a Custom Phone Ring

The following procedure applies to creating custom phone rings for only the Cisco Unified IP Phone models 7940, 7960, and 7970.

Procedure


Step 1 Create a PCM file for each custom ring (one ring per file). Ensure that the PCM files comply with the format guidelines that are listed in the "PCM File Requirements for Custom Ring Types" section.

Step 2 Use an ASCII editor to edit the RingList.xml file. See the "RingList.xml File Format Requirements" section for information on how to format this file, along with a sample RingList.xml file.

Step 3 Save your modifications and close the RingList.xml file.

Step 4 Place the new PCM files that you created in the C:\Program Files\Cisco\TFTPPath directory on the Cisco TFTP server for each Cisco Unified CallManager in your cluster.

Step 5 To cache the new RingList.xml file, stop and start the TFTP service by using Cisco Unified CallManager Serviceability or disable and re-enable the "Enable Caching of Constant and Bin Files at Startup" TFTP service parameter (located in the Advanced Service Parameters).


Where to Find More Information

Related Topics

Cisco TFTP, Cisco Unified CallManager System Guide

Service Parameters Configuration, Cisco Unified CallManager Administration Guide

Additional Cisco Documentation

Cisco Unified IP Phone Administration documentation for Model 7940, 7960, and 7970