AIP-V3-ANS
The ArmorIP Internet Monitoring Application converts the ArmorIP reporting protocols used by the Protege System and other third party products to Ademco 685 format. The integration process for a monitoring station is seamless and can be done in a matter of minutes allowing an immediate transition to IP reporting without the normal time consuming custom solutions.
Account information is presented in a 'Live View' window that shows the currently online and delinquent accounts, information includes:
All information that is transmitted to the ArmorIP Internet Monitoring Application is logged in a local database that is able to be accessed by third party software or other applications. Sample databases are available that extract information for a particular account or all accounts and these can be executed over a network connection.
Auto Generation HTML Account Status
The account status screen can be replicated to a live HTML page that can be scheduled for FTP to a remote server. This allows a control room to use this information to show the current status of accounts on a primary screen. The export can also be provided to other applications.
All communications have optional configuration with the AES encryption standard in 128, 192 or 256 Bit mode.
Supports for multiple IP reporting formats. For all IP based formats the IP address and port of the monitoring station must be entered:
The ArmorIP (UDP) format communicates with an ArmorIP Server using UDP as the transport layer. When using this format the account code must be set to be the same 8 digit code as is saved in the ArmorIP Server the panel is communicating with. Using UDP to send the messages is faster than TCP as it is a connectionless protocol, the ArmorIP (UDP) protocol includes acknowledge and retry messages to ensure that the message has been received by the server.
The ArmorIP (TCP) format communicates with an ArmorIP Server using TCP as the transport layer. When using this format the account code must be set to be the same 8 digit code as is saved in the ArmorIP Server the panel is communicating with.
The ArmorIP-E (UDP) is the encrypted version of the ArmorIP protocol. It uses an AES encryption algorithm that is selectable for 128, 192 or 256 Bit encryption. 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 panel and the ArmorIP Server.
The ArmorIP-E (TCP) is the encrypted version of the ArmorIP protocol. It uses an AES encryption algorithm that is selectable for 128, 192 or 256 Bit encryption. 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. This format uses the TCP layer as its transport mechanism.
The ArmorIP protocol outputs full textual based transmission that includes the names of the objects (user, area or zone) that generated the reportable event. This information is stored in the database and can be retrieved with the appropriate ContactID data.
The notification of an offline account is presented to the receiver by configuration of an account and appropriate CID message. This allows the monitoring station to configure the automation package in the most optimal manner for reception of alarms, by account, zone or specific account.
