CRX-ARMORIP

Protege ArmorIP Internet Monitoring Application

Use part no. PRT-GX-SRVR when orderingCRX-ARMORIP

Product Description

The ArmorIP Internet Monitoring Application converts the ArmorIP reporting protocols used by the Protege System, PostX, PostX Plus 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.

Feature Highlights

  • Converts the ICT ArmorIP reporting protocol for use in any Ademco 685 compliant monitoring station application.
  • Windows XP, Vista, Server 2003, Server 2008 and Windows 7 compliant application.
  • ‘Live View’ shows the current accounts that are online with next poll options.
  • Supports AES encryption in 128, 192 and 256 Bit keys
  • Automatic HTML export of account status for live presentation to remote web location with FTP upload support.
  • Free edition for use on up to 20 accounts. Flexible licensing in 250 account blocks.

Account Information

Account information is presented in a ‘Live View’ window that shows the currently online and delinquent accounts, information includes:

  • Last time the panel completed a poll and the next time the panel should poll based on the configuration parameters.
  • Countdown of seconds to next poll
  • The current IP address of the account, this allows the ability to remote access the IP device if required.
  • Name of the account

Data Storage and Reports

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.

Encryption Support

All communications have option configuration with the AES encryption standard in 128, 192 and 256 Bit mode.

PostX Support

The PostX supports seven IP reporting formats and two PSTN reporting formats. For all IP based formats the IP address and port of the monitoring station must be entered:

  • ArmorIP (UDP)
  • ArmorIP (TCP)
  • ArmorIP-E (UDP)
  • ArmorIP-E (TCP)
  • Contact ID (UDP)
  • Contact ID (TCP)
  • Alarm NZ
  • Patriot LS30

ArmorIP (UDP)

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 PostX 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.

ArmorIP (TCP)

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 PostX is communicating with.

ArmorIP-E (UDP)

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 PostX and the ArmorIP Server.

ArmorIP-E (TCP)

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.

Contact ID (UDP)

The Contact ID (UDP) 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)

The Contact ID (TCP) 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. TCP is used as the transport layer for this protocol.

Alarm NZ

The Alarm NZ format communicates with Alarm NZ’s central monitoring station alarm receivers using TCP.

Patriot LS30

The Patriot LS30 TCP format communicates with the LS30 task in the Patriot Alarm Monitoring software.

Full Textual Transmission

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.

Offline Account Notification

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.

ISCS – ICT Protege ArmorIP Internet Monitoring Application