User`s manual

SIP User's Manual 292 Document #: LTRT-83303

Mediant 1000 & Mediant 600

4.2 The ini File Structure

The ini file can contain any number of parameters. The ini file can contain the following

types of parameters:

 Individual parameters, which are conveniently grouped (optional) by their functionality

(refer to ''Structure of Individual ini File Parameters'' on page 292)

 Table parameters, which include multiple individual parameters (refer to ''Structure of

ini File Table Parameters'' on page 293)

4.2.1 Structure Rules

The ini file must adhere to the following format 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.

4.2.2 Structure of Individual ini File Parameters

The structure of individual ini file parameters in an ini file is shown below:

[Subsection Name]

Parameter_Name = Parameter_Value

; REMARK