Introduction
The DC-09 driver is an implementation that was done for a specific customer, but it could potentially be used elsewhere. It behaves as if it were a SIA DC-09 compliant panel. There is limited capability to massage the transmitter ID before the message gets transmitted.
Driver file
The DC-09 dispatch driver's file is DC09DispatchProvider.dll.
Configuration file settings
appsettings.json has an object section called "DC-09" that contains all configurations for this driver. The default configuration is shown below, and is fully documented in the file:
"DC-09": {
// Number of characters of the transmitter ID to use for the panel ID
"panelIdLength": 1,
// Number of characters of the transmitter ID to use for the installer ID
"installerIdLength": 2,
// Number of characters of the transmitter ID to use for the authority ID
"authorityIdLength": 3,
"Routes": [
{
// The authority ID that will use this route
"AuthorityId": "CSFD",
//Specifies to which machine and port to send the DC-09 UDP datagrams
"UdpRecipient": "localhost:5000",
// If specified, will encrypt messages with this key. Must be a 128, 192, or 256-bit hex string (32, 48, or 64 characters)
// NOTE: AS THIS IS A KNOWN DEFAULT KEY, DO NOT USE THIS KEY. BUILD A NEW KEY.
// This key must also be configured at the CSR so it can decrypt messages generated with this key.
"EncryptionKey": "12345678901234567890123456789012",
//Specifies to which machine and port to send the DC-09 UDP datagrams if the primary connection fails
"BackupUdpRecipient": "localhost:5001",
// If specified will use this encryption key for the backup connection
"BackupEncryptionKey": "12345678901234567890123456789012",
// This is the UDP port upon which to listen for responses to messages sent. If this is not specified,
// no listener will be started. If specified, the driver will open a DC-09 UDP listen port and log
// incoming signals to the logger only.
"UdpListenPort": 6002,
// This is the encryption key to use when communicating on the receive UDP connection.
"ListenEncryptionKey": "12345678901234567890123456789012",
// If specified, this will be used as the enclosing account number in all DC-09 messages. If this
// is not specified, the system will use the account number (TXID) from the alarm payload as
// the enclosing account.
"EnclosingAccount": "710",
// Number of seconds between NULL line supervision signals. Set to 0 to disable supervision.
"SupervisionSeconds": 10,
// Number of seconds to wait for a response to a signal before attempting a retry.
"ResponseTimeoutSeconds": 5,
// Number of retries to pursue before giving up on sending the signal.
"FailRetryCount": 3,
// If the CSR responds DUH, should we retry the signal?
"RetryDuh": false,
// Installer ID to embed in the transmitter ID
"installerId": 42
}
]
},
Routing
The "Routes" configuration parameter is an array of objects. Each object contains all of the configuration for a route. The driver can have as many routes as necessary for the integration and will use the dealer's contact ID as the route key. So if the dealer's contact ID matches "AuthorityID" in the route, the driver will use that route.
Reverse commands
Just like the CSAA ASAP to PSAP system, this integration requires all three reverse commands to be configured: ALRM, UPD, and VRFY. These reverse commands are configured exactly the same is the CSAA reverse commands, except it will require labels for each parameter, whereas the CSAA implementation uses positional reverse command parameters. These are the three reverse commands you'll need to configure:
ALRM
| Field Type | Data Type | Label | DB Value | Default |
|---|---|---|---|---|
| Database | Text | TXID | Transmitter ID | |
| Database | Text | ZONE | Zone Number | |
| Database | Text | ZONEDESCR | Zone Description | |
| Database | Text | EVCODE | Event Code | |
| Database | Text | AUTHID | Contact Point | |
| Database | Text | POINTID | Point ID | |
| Database | Text | AREA | Original Area | |
| Fixed Value | Text | PROVIDERID | DC-09 |
