Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000Version 4.4 133 July 20056.13 Configuration Files ParametersThe configuration files (Call Progress Tones, PRT, Voice Prompts and CAS) can be loaded to theMediant 2000 via the Embedded Web Server (refer to Section 5.11.2 on page 82), or via TFTPsession.¾ To load the configuration files via TFTP, take these 3 steps:1. In the ini file, define the files to be loaded to the device. You can also define in the ini filewhether the loaded files should be stored in the non-volatile memory so that the TFTPprocess is not required every time the device boots up.2. Locate the configuration files you want to load and the ini file in the same directory.3. Invoke a BootP/TFTP session; the ini and configuration files are loaded onto the device.Table 6-8 below describes the ini file parameters that are associated with the configuration files.Table 6-8: Configuration File Parametersini File Field Name Valid Range and DescriptionCallProgressTonesFilename The name of the file containing the Call Progress Tones definitions. Refer to Section7 for additional information on how to create and load this file.VoicePromptsFileName The name (and path) of the file containing the Voice Prompts definitions. Refer toSection 7.2 on page 137 for additional information on how to create and load thisfile.CASfilename This is the name of the file containing specific CAS protocol definition (such as‘E_M_WinkTable.dat’). These files are provided to support various types of CASsignaling.CASfilename_x It is possible to load up to 8 different CAS files (x=0 to 7), by repeating theCASFileName parameter. Each CAS file can be associated with one or more of thegateway trunks, using "CASTableIndex_x" parameter.CASTablesNum Number, 1 to 8. Specifies how many CAS configuration files are loaded.PrerecordedTonesFileName The name (and path) of the file containing the Prerecorded Tones.SaveConfiguration Set to 1 to store the CPT, PRT, CAS and Voice Prompts files in the non-volatilememory.
