User`s manual

Mediant 1000
H.323 User's Manual 304 Document #: LTRT-83401
11.5.2 Table Permissions
Each column has a 'permission' attribute that is applied to all instances in the column. This
permission determines if and when a field can be modified. Several permissions can be
applied to each column.
The following permissions are available:
 Read: The value of the field can be read.
 Write: The value of the field can be modified.
 Create: A value for the field must be provided at creation time (the default values, set
to all fields, determine the initial values).
 Maintenance Write: The value of the field can only be modified when the entity
represented by the line is in maintenance state (each table includes rules that
determine when it is in maintenance state).
In the example in Table 11-1 it is assumed that the columns ‘User Name’ and ‘User
Password’ have Read-Create permissions. The column ‘Time Connected’ has a Read
permission, and the column ‘Permissions’ has Read-Create-Maintenance Write
permissions.
11.5.3 Dynamic Tables vs. Static Tables
 Static Tables: Static tables don’t support adding new lines or removing (deleting)
existing lines. All lines in a Static table are pre-configured with default values. Users
can only modify the values of the existing lines. After reset, all lines in a Static table
are available.
 Dynamic Tables: Dynamic tables support adding and removing lines. They are
always initialized as empty tables with no lines. Users should add lines to a Dynamic
table via the ini file or at run-time via the Embedded Web Server for example.
Note: Certain dynamic tables may initialize a line (or more) at start-up. If so, it is
explained in the specific table's documentation.
11.5.4 Secret Tables
A table is defined as a secret table if it contains at least a single secret data field or if it
depends on another secret table. A secret data field is a field that mustn’t be revealed to
the user. For example, in the IPSec application, IPSec tables are defined as secret tables
as the IKE table contains a pre-shared key that must be concealed. Therefore, the SPD
table that depends on the IKE table is defined as a secret table as well.
There are two major differences between tables and secret tables:
 The secret field itself cannot be viewed via SNMP, Web or any other application.
 ini file behavior: Secret tables are never displayed in an uploaded ini file (e.g., when
performing a 'Get ini File from Web' operation). Instead, there is a commented title that
states that the secret table is present at the gateway and is not to be revealed.
Secret tables are always kept in the gateway’s non-volatile memory and can be over-
written by new tables that are provided in a new ini file. If a secret table appears in an
ini file, it replaces the current table regardless of its content. To delete a secret table
from the gateway, provide an empty table of the same type (with no data lines) as part
of a new ini file; the empty table replaces the previous table in the gateway.