Nortel Networks TP-1610 SIP user manual Configuring the Call Progress Tones

Mediant 2000 SIP User’s Manual 7. Configuration Files

7 Configuration Files

This section describes the configuration (dat) files that are load (in addition to the ini file) to the gateway. The configuration files are:

•Call Progress Tones file (refer to Section 7.1 below).

•Prerecorded Tones file (refer to Section 7.2 on page 137).

•Voice Prompts file (refer to Section 7.3 on page 137).

•CAS protocol configuration files (refer to Section 7.4 on page 138).

To load any of the configuration files to the Mediant 2000 use the Embedded Web Server (refer to Section 5.11.2 on page 82) 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 B.6 on page 190).

7.1Configuring the Call Progress Tones

The Call Progress Tones, configuration file used by the Mediant 2000 is a binary file (with the extension dat) which contains the definitions of the Call Progress Tones (levels and frequencies) that are detected / generated by the Mediant 2000.

Users can either use, one of the supplied Mediant 2000 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” supplied with the software package. For the description of the procedure on how to convert CPT

ini file to a binary dat file, refer to Section G.1.1 on page 214.

Note that only the dat file can be loaded to the Mediant 2000 gateway.

To load the Call Progress Tones (dat) file to the Mediant 2000, use the Embedded Web Server (refer to Section 5.11.2 on page 82) or the ini file (refer to Section 6.12.1 on page 132).

7.1.1Format of the Call Progress Tones Section in the ini File

Using the CPT section of this configuration file, the User can create up to 16 different Call Progress Tones using up to 15 different frequencies (in the range of 300 Hz to 1980 Hz). Each of these Call Progress Tones is specified by its tone frequency (either single or dual frequencies are supported) and its tone cadence. The tone cadence is specified by 2 sets of on/off periods (you can discard the use of the first on/off cycle by setting the relevant parameters to zero). When a tone is composed of a single frequency, the second frequency field must be set to zero.

For a continuous tone (such as dial tone), only the “First Signal On time” should be specified. 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.

Users can specify several tones of the same type. These additional tones are used only for tone detection. Generation of a specific tone conforms to the first definition of the specific tone. For example, Users can define an additional dial tone by appending the second dial tone’s definition lines to the first tone definition in the ini file. The Mediant 2000 reports dial tone detection if either of the two tones is detected.

The Call Progress Tones section of the ini file format starts from the following string:

•[NUMBER OF CALL PROGRESS TONES] – Contains the following key:

“Number of Call Progress Tones” defining the number of Call Progress Tones that are defined in the file.

Version 4.4 135 July 2005