<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">\subsection{Destination (0x05)}

CATS packets can optionally have one or more destinations. This can be useful for e.g. sending a message to another amateur radio operator, or for communicating with a service. The destination consists of a UTF-8 callsign and an SSID byte. \textbf{A valid CATS packet may contain zero or more destination whiskers.}

The destination whisker also allows requesting an acknowledgement from the station, to confirm that the packet was received successfully. This is specified in the acknowledgement byte. If the byte is 0, no acknowledgement is requested. Otherwise, an acknowledgement ID is specified in the 7 least significant bits. The MSB must be cleared. To acknowledge, a CATS packet must be crafted with a destination of the original station's callsign. The acknowledgement byte must have the same acknowledgement ID, but with the MSB set. The MSB is how acknowledgement requests are differentiated from acknowledgement responses.

\subsubsection{Structure}

\begin{tabular}{|l|l|l|l|}
  \hline
  \textbf{Byte offset} &amp; \textbf{Length} &amp; \textbf{Value} &amp; \textbf{Description} \\
  \hline
  0 &amp; 1 &amp; 0x05 &amp; Whisker type \\
  \hline
  1 &amp; 1 &amp; $N$ &amp; Whisker length in bytes \\
  \hline
  2 &amp; 1 &amp; &amp; Acknowledgement byte \\
  \hline
  3 &amp; $N - 2$ &amp; &amp; UTF-8 callsign \\
  \hline
  $N + 1$ &amp; 1 &amp; &amp; SSID \\
  \hline
\end{tabular}
</pre></body></html>