AudioCodes Mediant 3000 User Manual

Version 7.0 117 Mediant 3000
User's Manual 10. INI File-Based Management
For general ini file formatting rules, see ''General ini File Formatting Rules'' on page 117.
The table below displays an example of a table ini file parameter:
[ CodersGroup0 ]
FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime,
CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce,
CodersGroup0_CoderSpecific;
CodersGroup0 0 = g711Alaw64k, 20, 0, 255, 0, 0;
CodersGroup0 1 = eg711Ulaw, 10, 0, 71, 0, 0;
[ \CodersGroup0 ]
Note: Do not include read-only parameters in the table ini file parameter as this can
cause an error when attempting to load the file to the device.
10.1.3 General ini File Formatting Rules
The ini file must adhere to the following formatting rules:

The ini file name must not include hyphens "-" or spaces; if necessary, use an
underscore "_" instead.

Lines beginning with a semi-colon ";" are ignored. These can be used for adding
remarks in the ini file.

A carriage return (i.e., Enter) must be done at the end of each line.

The number of spaces before and after the equals sign "=" is irrelevant.

Subsection names for grouping parameters are optional.

If there is a syntax error in the parameter name, the value is ignored.

Syntax errors in the parameter's value can cause unexpected errors (parameters may
be set to the incorrect values).

Parameter string values that denote file names (e.g., CallProgressTonesFileName)
must be enclosed with inverted commas, e.g., CallProgressTonesFileName =
'cpt_usa.dat'.

The parameter name is not case-sensitive.

The parameter value is not case-sensitive, except for coder names.

The ini file must end with at least one carriage return.

AudioCodes Mediant 3000 Specifications

General

Brand	AudioCodes
Model	Mediant 3000
Category	Gateway
Language	English