
11
Configuration File
6.4
Fig. 11. A sample configuration file
The DAC-P must be provisioned with a configuration file that defines the remotes it will poll. The configuration file is a text
file derived from the TMAS database using utility software. The file is transmitted to the DAC-P via File Transfer Protocol
(FTP).
Note: Every time a configuration file is uploaded to the DAC-P, the unit's memory is completely overwritten. You must
always upload a complete configuration file. If a section of the configuration file is omitted, the default settings for that
section will be used.
A sample configuration file is shown in Figure 10. The file is divided into two sections: #ADDR_CFG and #PHONE_CFG.
A001c00AURR,AK
IRIS Port DCP Address
(1–255)
Device Type
MEFA
(0–31)
Location
(Free-form
text field)
Fig. 12. Elements of an #ADDR_CFG entry
The #ADDR_CFG section defines which remotes the DAC-P will poll, what type of device the remote is, and to which
MEFA to map the device. Valid entries for the address field are 0 to 255. Valid entries for the device type field are: "a" for
DS5000 (single); "b" for DS5000 (dual); and "c" for DS3000 or KDA-E2A. Valid entries for the MEFA field are 0 to 31.
Each line of the #ADDR_CFG section defines an individual remote. Each remote must have a unique address and MEFA.
A001o1-559-454-8167AURR,AK
IRIS Port DCP Address
(1–255)
Outbound,
Primary
or Backup
Phone Number
Phone Number
Location
(Free-form
text field)
Fig. 13. Elements of a #PHONE_CFG entry
The #PHONE_CFG section defines the phone numbers associated with remotes. Each line of the #PHONE_CFG section lists
the address of the remote, the type of phone number, and the phone number.
Each remote can have three phone numbers:
1. "o": Outbound phone number. The phone number the DAC-P will dial to call the remote.
Содержание DAC-P
Страница 42: ......