User`s manual
MediaPack SIP User’s Manual 16. Configuration Files
Version 4.6 241 June 2005
16 Configuration Files
This section describes the configuration dat files that are loaded (in addition to the ini file) to the
gateway. The configuration files are:
• Call Progress Tones file (refer to Section
16.1 on page 241).
• Prerecorded Tones file (refer to Section
16.2 on page 246).
• FXS/FXO Coefficient files (refer to Section
16.3 on page 247).
To load either of the configuration files to the MediaPack use the Embedded Web Server (refer to
Section
5.8.2 on page 159) or alternatively specify the name of the relevant configuration file in
the gateway’s ini file and load it (the ini file) to the gateway (refer to Section
5.8.2.1 on page 160).
16.1 Configuring the Call Progress Tones and
Distinctive Ringing File
The Call Progress Tones and Distinctive Ringing, configuration file used by the MediaPack is a
binary file (with the extension dat) that is comprised of two sections. The first section contains the
definitions of the Call Progress Tones (levels and frequencies) that are detected / generated by
the MediaPack. The second section contains the characteristics of the distinctive ringing signals
that are generated by the MediaPack.
Users can either use, one of the supplied MediaPack configuration (dat) files, or construct their
own file. To construct their own configuration file, users are recommended, to modify the supplied
usa_tone.ini file (in any standard text editor) to suit their specific requirements, and to convert it
(the modified ini file) into binary format using the TrunkPack Downloadable Conversion Utility. For
the description of the procedure on how to convert CPT ini file to a binary dat file, refer to Section
D.1.1 on page 272.
Note that only the dat file can be loaded to the MediaPack gateway.
To load the Call Progress Tones (dat) file to the MediaPack, use the Embedded Web Server
(refer to Section
5.6.4 on page 145) or the ini file (refer to Section 5.8.2.1 on page 160).
16.1.1 Format of the Call Progress Tones Section in the ini File
Users can create up to 32 different Call Progress Tones, each with frequency and format
attributes.
The frequency attribute can be single or dual-frequency (in the range of 300 Hz to 1980 Hz), or
an Amplitude Modulated (AM). In total, up to 64 different frequencies are supported. Only eight
AM tones, in the range of 1 to 128 kHz, can be configured (the detection range is limited to 1 to
50 kHz). Note that when a tone is composed of a single frequency, the second frequency field
must be set to zero.
The format attribute can be one of the following:
• Continues - (e.g., dial tone) a steady non-interrupted sound. Only the ‘First Signal On time’
should be specified. All other on and off periods must be set to zero. In this case, the
parameter specifies the detection period. For example, if it equals 300, the tone is detected
after 3 seconds (300 x 10 msec). The minimum detection time is 100 msec.
• Cadence – A repeating sequence of on and off sounds. Up to four different sets of on / off
periods can be specified.
• Burst – A single sound followed by silence. Only the ‘First Signal On time’ and ‘First Signal
Off time’ should be specified. All other on and off periods must be set to zero. The burst tone
is detected after the off time is completed.