3 pre configuration file rules – AASTRA SIP-DECT (Release 1.8)-Installation- and Administration Guide EN User Manual

Page 94

Advertising
background image

Installation, Administration and Maintenance

Aastra

depl-0900/0.4

Page: 94 (104)

8.3

Pre Configuration File rules

The framework of the text file follows strictly defined rules.

The main framework is divided in two parts:

1. An instruction section is used to drive a generic data creation for

those fields, not filled within data sequence section.

2. A data sequence section defines data record fields. Each of them

are explicitly set

Layout rules in detail are:

• Comments start with “#”
• Each record is terminated by the regular expressions “\r” or “\n”
• Instruction settings are made like: <tag> = <value>.
• Data sequence sections starts with the key word “data_sequence”.

This key word is always mandatory to proceed the file. All
instructions have to be written before this row.

• Data sequence record fields are separated by colon “;”. Colons have

also to be set for empty fields, if at least one follows which is not
empty. Otherwise a position mismatch of fields will occur.

• If fields have several values assigned (that may be true for a few local

RFP configuration fields like ntp_address), they must be separated by
comma “,”.

Notes:

• Because of data sequence fields are separated by colon the content of

that section can possibly be generated by a .csv export of Excel-Sheet
and copied into the configuration file.

• Instructions are only proceeded on those fields, which are left empty

within the data sequence section

Advertising