# Incomplete Reports

There are many circumstances that can cause an incomplete report to be delivered. For examples; busy signal detected (no report at all), a premature connection loss, or exceeding the configured report length limits.

This section provides the specification for what happens whenever a report is incomplete for any reason. These specifications apply uniformly to all destination types.

The term contacted is used to indicate that a connection was actually established with the destination.

The precise definition here depends on the destination type as follows:

Destination Type | Considered “Contacted” When:
--- | ---
Voice | Receive DTMF response to initial greeting prompt.
RDT | Begin report delivery after modem carrier established.
Alarmware | Host acknowledges the session request.
Fax | Begin report delivery after all modem negotiations completed.
RCS | Session completed successfully.
Numeric Pager | Receive tone prompt from service provider.
Alpha Pager | Service provider acknowledges the session request.
PBX | After all dialing string characters are processed, if any exists.

The term confirmation is used to indicate that a given report item was delivered and received by the destination. Again, specifics here depend on destination type as follows:

Destination Type | Items Considered “Confirmed” When:
--- | ---
Voice | Any DTMF tone entered after item reported.
RDT | Carrier was up when data transmitted.
Alarmware | The report packet is acknowledged.
Fax | The report page containing the item is confirmed received.
RCS | The packet containing the item is acknowledged.
Numeric Pager | Contacted. NOTE: S ervice providers do not provide end-to-end confirmation. Impossible to know that pager receives the message.
Alpha Pager | Transaction containing item is acknowledged by the service provider. NOTE: Paging service providers do not provide end-to-end confirmation. Can not know that pager receives the message.
PBX | Contacted.

The term session attempt indicates that the RTU is trying to contact some destination. The session rotation refers to the series of session attempts caused by the need to get operator acknowledgment for alarms or to deliver some other report(s).

Please see the Catalyst Operator's Manual, section 1.6, for all the details, rules and specifics about the prioritization of session attempts, session rotation, and call-out precedence. Suffice to say here that anytime a session is re-attempted (in the current rotation), logic will retain the cumulative number of pages/blocks/whatever sent in all prior attempts and never exceed the configured limit. This cumulative count is reset when a new rotation begins.

The term reported is used to indicate that a specific channel state or log file segment has been delivered to a given destination. In general, reports only contain unreported data, and sessions occur if and only if there are unreported states.