Pp configuration file (omm database), Supported instructions, Data section fields – AASTRA SIP-DECT (Release 2.1)- OM System Manual - Installation, Administration and Maintenance EN User Manual
Page 181
SIP – DECT OM System Manual Release 2.1
9 Appendix
depl-1230/1.3
Page: 181 (196)
•
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.
9.7.1
PP Configuration File (OMM Database)
9.7.1.1 Supported Instructions
Instruction
Explanation
start_number
Numbers can be generated automatically.
This instruction defines the start value.
no_of_number
If “start_number” is given, this instruction
defines the maximum of numbers which are
generated.
ac (authentication code)
additional_pin
sip_user
sip_pw
If set to “number”, “ac” will be equal to
number.
If a value is advised, it will be taken as a start
number which will be increased for each new
record.
sos_number
mandown_number
locatable
localization
tracking
If these instructions are set, the value will be
taken as default value for the empty
corresponding field within the data sequence
section records.
SOS/Mandown denote the user specific
numbers. The Locatable, Localization, and
Tracking flags are ignored by Web import.
9.7.1.2 Data Section Fields
The data section contains the following field order:
1 Number
2 Name
3 AC
4 IPEI
5 Additional ID