Dynamic tables versus static tables, Tables in the loaded ini file, J.6.3.2 – Nortel Networks Mediant TP-1610 SIP User Manual

Page 244: J.6.3.3

Advertising
background image

Mediant 2000 SIP

Mediant 2000 SIP User’s Manual

244

Document #: LTRT-72504

The order of the Data fields in the Format line is not significant (unlike the Index-fields). Field
values in Data lines are interpreted according to the order specified in the Format line.

The sign '$$' in the Data line means that the user wants the pre-defined default value
assigned to the field for the given line.

The order of Data lines is insignificant.

Data lines must match the Format line, i.e., it must contain exactly the same number of
Indices and Data fields and should be in exactly the same order.

A line in a table is identified by its table-name and its indices. Each such line may appear
only once in the ini file.

Tables' dependencies:

Certain tables may depend on other tables. For example, one table may include a field, which
specifies an entry in another table, 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 order of dependency (i.e., if Table
X is referred to by Table Y, then Table X must appear in the ini file before Table Y).

J.6.3.2 Dynamic

Tables

versus Static Tables

Static Table:

The Static table type does not support adding new lines or removing (deleting) an existing line. All
lines in a Static table are pre-configured with default values. Users may modify values in existing
lines. After reset, all lines in a Static table are available.

Dynamic Table:

The Dynamic table type supports adding and removing lines. It is always initialized as an empty
table, with no lines. Users should add lines to the Dynamic table via the ini file or at run-time.

Note:

Certain dynamic tables may initialize a line (or more) at start-up time. If so, it
is documented in the table's specific section.

J.6.3.3 Tables in the Loaded ini File

Tables are grouped according to the applications they configure. For example, several tables are
required to configure SS7, and other tables are required to configure ATM.

When loading the ini file, the policy is to include only tables that belong to applications, which
have been configured (Dynamic tables of other applications are empty, but static tables are not).

Advertising