AudioCodes Mediant 600 - General Ini File Formatting Rules

Version 6.4 85 March 2012
SIP User's Manual 7. INI File-Based Management

Data lines must match the Format line, i.e., it must contain exactly the same number
of Indices and Data fields and must be in exactly the same order.

A row in a table is identified by its table name and Index field. Each such row may
appear only once in the ini file.

Table dependencies: Certain tables may depend on other tables. For example, one
table may include a field that specifies an entry in another table. This method is used
to specify additional attributes of an entity, or to specify that a given entity is part of a
larger entity. The tables must appear in the order of their dependency (i.e., if Table X
is referred to by Table Y, Table X must appear in the ini file before Table Y).
For general ini file formatting rules, see 'General ini File Formatting Rules' on page 85.
The table below displays an example of an ini file table parameter:
[ CodersGroup0 ]
FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime,
CodersGroup0_rate, CodersGroup0_PayloadType, CodersGroup0_Sce;
CodersGroup0 0 = g711Alaw64k, 20, 0, 255, 0;
CodersGroup0 1 = eg711Ulaw, 10, 0, 71, 0;
[ \CodersGroup0 ]
Note: Do not include read-only parameters in the ini file table parameter as this can
cause an error when attempting to load the file to the device.
7.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.