User's Manual

Boomer II User Manual & Integrator’s Guide ______________________________________________ SDK SCRAPI
BM210012WT27 153 Wavenet Technology
SCR_DI Disconnect Indication
SCR_AR Activity Request
SCR_AC Activity Confirmation (response to AR)
SCR_RS Receiver Suspend
SCR_RR Receiver Resume
DataTAC
®
5000 and DataTAC
®
6000 Network Messages
The following message types are common to the DataTAC 5000 and
6000 networks:
SCR_MI Message Indication message for receiving data from a
wireless device.
SCR_HR Host Request message for sending data to a wireless
device
SCR_HC Host Confirmation for acknowledgment of data sent to a
wireless device
Data Header
All data messages (MI, HR, OB, IB, TO_NET, FROM_NET) contain a
data header field. This field is used to route messages to the correct
server from client RPM devices. The data header is also sometimes
referred to as the session, and this is reflected in some of the NCL API
function parameters. For example, the szHostId parameter in
nclSendData and in the data header for the nclReceiveData functions.
This data header is represented in the SDK as a NULL terminated
string.
Refer to section Message Routing and Migration sub section SCR
Header charts for the formatting of the header fields. How the use of
the Data Header field varies between the network types is described
below.
For DataTAC 4000 and 6000 networks, a host slot is used to route data
from the wireless client to the correct server. RPM devices can be
configured with up to five host slots, each routed to a different server
application. When the client application sends a message, the data
header is used to specify which host slot to send on, and hence which
server application the data will be sent to. The host slot is represented
by a single ASCII digit from 1 to 5. This digit must be given as the last
character of the data header. For example, a data header of I would
route the information on host slot 1, whereas a data header of TE3
would route the data on host slot 3.
For the DataTAC 5000 network, a 2-character session ID is used for
routing data from the wireless client to the correct server. RPM devices
may be configured with many sessions, each routed to different server
applications. The session ID is made up of any two characters from A
to Z or 0 to 9. When a client application sends data to a server