CRX-POSTX-DIN
DIN Rail PostX IP Reporting Module
Installation Manual | June 2017
19
ArmorIP (TCP)
This format is identical to ArmorIP (UDP) except it uses TCP as the transport layer.
ArmorIP-E (UDP)
This is the encrypted version of the ArmorIP protocol, using UDP as the transport layer. It uses an AES
encryption algorithm that is selectable for 128, 192 or 256 bit encryption. The encryption settings can be
found on the
Advanced
page of the PostX Module. If
Use Default Settings
is selected, make sure that this is
also selected in the ArmorIP server. When this is selected, no other details need to be entered. If you want
to increase the security, use a custom key that must be entered in both the PostX Module and the ArmorIP
server.
ArmorIP Encryption
i
For maximum security it is recommended using an encryption key that contains both letters and
numbers and does not form a known word. The encryption key is case sensitive.
ArmorIP-E (TCP)
This format is identical to ArmorIP-E (UDP) except it uses TCP as the transport layer.
Contact ID (UDP)
This format is an ASCII based format that only contains the Contact ID message. In all instances, the
message will be 16 characters long with the format detailed below.
The form of the message is: ACCT MT QXYZ GG CCC S, where:
ACCT
4 Digit Account Number
MT
2 Digit Message Type
Q
1 Digit Event Qualifier
XYZ
3 Digit Event Code
GG
2 Digit Group Number
CCC
3 Digit Zone Number
S
1 Digit Checksum
To acknowledge this message the server must send back an identical copy of this message. UDP is used
as the transport layer for this protocol.
Contact ID (TCP)
This format is identical to Contact ID (UDP) except it uses TCP as the transport layer.
CSV-IP
This format uses TCP as the transport layer and communicates with central station receivers supporting
that format.
Patriot LS30
This TCP format communicates with the LS30 task in Patriot alarm monitoring software.