Chapter 6 Customizing the Cisco Unified IP Phone

Creating Custom Phone Rings

Ringlist.xml File Format Requirements

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:

<CiscoIPPhoneRingList>

<Ring>

<DisplayName/>

<FileName/>

</Ring>

</CiscoIPPhoneRingList>

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:

<CiscoIPPhoneRingList>

<Ring>

<DisplayName>Analog Synth 1</DisplayName> <FileName>Analog1.raw</FileName>

</Ring>

<Ring>

<DisplayName>Analog Synth 2</DisplayName> <FileName>Analog2.raw</FileName>

</Ring>

</CiscoIPPhoneRingList>

Cisco Unified IP Phone Administration Guide for Cisco Unified CallManager 5.1 (SIP), Cisco Unified IP Phones

 

OL-11524-01

6-3

 

Page 169
Image 169
Cisco Systems 7970G manual Ringlist.xml File Format Requirements