6-2
Cisco Unified IP Conference Station 7937G Administration Guide for Cisco Unified Communications Manager 6.0
OL-11560-01 Rev. B0
Chapter 6 Customizing the Conference Station
Creating Custom Conference Station Rings
Creating Custom Conference Station Rings
The conference station ships with two default ring types that are implemented in hardware: Chirp1 and
Chirp2. Cisco Unified Communications Manager also provides a default set of additional conference
station 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 Communications Manager.
For more information, refer to
Cisco Unified Communications Manager System Guide
,
Release 5.1(1),
“Cisco TFTP” chapter, and
Cisco Unified Communications Operating System Administration Guide,
“Software Upgrades” chapter
.
The following sections describe how you can customize the conference station rings that are available at
your site by creating PCM files and editing the Ringlist.xml file:
•
Ringlist.xml File Format Requirements, page 6-2
•
PCM File Requirements for Custom Ring Types, page 6-3
•
Configuring a Custom Conference Station Ring, page 6-3
Ringlist.xml File Format Requirements
The Ringlist.xml file defines an XML object that contains a list of conference station 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 conference station for that ring. The
Cisco TFTP server for each Cisco Unified Communications Manager contains this file.
The CiscoIPconference stationRingList XML object uses the following simple tag set to describe the
information:
<CiscoIPconference stationRingList>
<Ring>
<DisplayName/>
<FileName/>
</Ring>
</CiscoIPconference stationRingList>
The following characteristics apply to the definition names. You must include the required DisplayName
and FileName for each conference station 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 conference station.
•
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 conference station ring types:
<CiscoIPconference stationRingList>
<Ring>
<DisplayName>Analog Synth 1</DisplayName>
<FileName>Analog1.raw</FileName>
</Ring>
<Ring>
<DisplayName>Analog Synth 2</DisplayName>
<FileName>Analog2.raw</FileName>
</Ring>
</CiscoIPconference stationRingList>
