# Remote Data Terminal

The Remote Data Terminal (RDT) destination type is most commonly used in conjunction with a Log File. This is the destination that is called on a specific schedule, or when the log file exceeds the memory percentage threshold of the high-water mark.

The data that is delivered to the RDT is determined by:

- The content of the log file. All information downloaded to the Remote Data Terminal must already be stored/saved in the log file to be retrieved.
- The individual portions of data selected to be included in the download. These include logged channel state transitions, and logged Catalyst events.
- The range of data selected. This can include all data available, only undelivered data, or a specific range of dates or times.
- All reports have a cover page, similar to the specification for FAX destinations.
- Outgoing calls from the Catalyst can be scheduled, including log, status, and notification reports, using all the destination configuration options.
- Incoming calls to the Catalyst can only get a log file report. The Alarmware "Transfer Options" are used for the parameters of an incoming call.
- Incoming calls to the Catalyst are refused unless the Log File scan is enabled.
- Incoming calls to the Catalyst require a PIN only if PINs are configured.
- Incoming calls to the Catalyst will not delete any log file segment.

Note: The RDT has two strengths; it is fast and all it needs is a modem. However, RDT has one weakness, it is not a reliable transfer server. There is no error detection, correction, or way to pinpoint when or where a lost connection occurs. Some data will be lost if a connection is lost. The solution is to use a more reliable transfer server protocol: FAX, Email, or Alarmware.