
_________________________________________________________________________________
_________________________________________________________________________________
152 TAU-72.IP/TAU-36.IP Universal Network Terminal
9
DESCRIPTION OF CONFIGURATION FILES
This section lists description of a configuration file, used by the device.
For 'cfg.yaml' file description, see Tables 13 to 15.
To edit configuration files, you should:
1
Connect using RS-232 serial port (connection parameters: 115200, 8, n, 1, n; username: admin,
w/o password). Go to Linux console by executing 'shell' command. Configuration file is located in
'etc/config' folder.
2
Edit the file using embedded editor 'joe' (use arrow buttons to move the cursor; exit the editor
without saving: ctrl^c, exit and save changes: ctrl^(kx)): joe /etc/config/cfg.yaml.
3
When you finish editing and exit the editor, save settings with 'save' command.
9.1
Configuration file
–
CFG.YAML
Configuration file formation hierarchy:
#!version 1.0
Node1:
Node2:
Parameter1: Value1
Parameter2: Value2
Configuration file version (#!version 1.0) is used for autoupdate.
When working with CFG.YAML, you should observe the following rules:
—
Do not add/remove nodes.
—
Do not use tab characters '/t'.
—
Use spaces ' ' only.
—
Add the same number a of spaces ' ' before each node with a specific nesting level.
9.1.1
VoIP configuration
Table 13—VOIP configuration
Field name
Description
Values
h323
—
H.323 protocol configuration
enableh323
H.323 protocol
0–disable
1–enable
timetolive
Time period in seconds, for which the device
will keep its registration on a gatekeeper
10-65535
keepalivetime
Time period in seconds, after which the
device will renew its registration on a
gatekeeper
10-65535
h235
Authentication on the gatekeeper with H.235
protocol
0–disable
1–enable
ignore_gcf
Output authentication data in RRQ message
via H.235 protocol
0—only in case of reception of supported
hash method in GCF message
1—in any events