User's Manual

Table Of Contents

TReX User Manual v2.14 Firmware

WTE Ack and Confirm Protocol

Introduction

This section describes how to use this protocol to invoke automatic acknowledging and

optionally manual confirmation of messages sent/received. This protocol can also be used to

message TReX units to display confirmation prompts. The use of this protocol is the heart of

making two-way paging or messaging possible.

Monitoring equipment can make decisions based on acknowledge responses whether to

retransmit or notify a communications link issue. Acknowledgements can be either transmitted

or sent through a TCP/IP connection.

A typical application for a confirmation request would be an emergency communications room

messaging several ambulances with TReX units fitted. The message would provide an on-

screen prompt requesting attendance to an event. Any ambulance can then accept the message,

and details of the attending vehicle would then be sent to the communications room.

The WTE Ack and Confirm Protocol can be embedded into the payload of any message.

Typically the protocol message would be attached to the end of a message, so that paging

messages would display normally for typical users.

Note: In order for a TReX unit to acknowledge any message, the receiving TReX RIC codes

used must fall within allowed normal RX receive ranges.

Protocol Usage

-[TTT-A-XXX]

where:

- is the character '-' (marks the start of the ticket ID and ACK Mode)

[ is the character '['

TTT is a 3 digit ticket id

A is the ACK Mode

1 = acknowledge required

2 = acknowledge and confirmation required

3 = confirmation without acknowledgement (when sent to many stations.)

- is the character ‘-’ marking the start of the optional confirmation title.

XXX is the optional confirm title (e.g. "Accept?"). Not specifying this field results in default

of "CONFIRM". This field is only meaningful when ACK mode is 2 or 3. Max length is 14