User's Manual
Table Of Contents
- Introduction
- The Integrator’s Task
- Installing the Modem
- Using the Modem Test Jig
- Testing
- Desense
- Application Development
- Message Routing and Migration
- Appendix A - NCL Interface
- Appendix B - Software Development Kit
- SDK Contents
- System Requirements
- SDK Software Architecture
- NCL Application Programmer’s Interface
- Implementation
- Logical Architecture
- Application Interface
- Opening a Session
- Close Session
- Send Data to a Radio Host
- Receive Data From RPM
- Get RPM Status Information
- Set Configuration ITEMS Within the RPM
- Reset RPM
- Register Event Callback Function
- Enable / Disable Events
- Get Error Description
- Register Wakeup Application
- Deregister Wakeup Application
- Switch RPM On/Off
- Send Generic NCL Command To RPM
- Get Software Version
- SCR Application Programmer’s Interface
- A
- Appendix C – Sample programs
- Appendix D - Wavenet Application Loader
- Appendix E - Numeric Conversion Chart
- Appendix F - Specifications
- Appendix H - Glossary
Boomer II User Manual & Integrator’s Guide ________________________________ Message Routing and Migration
BM210012WT27 101 Wavenet Technology
Host Confirmation Message Header Fields
Length Prefix DataTAC 5000 systems require all SCR
messages to designate the length of the
message. The length count does not include
the length prefix itself, but does include
everything else in the message packet.
Type Code Identifies the type of the SCR message: Use
‘A’ ‘B’ for DataTAC 4000 systems. Use ‘H’
‘C’ for the other systems.
LLI Identifies the subscriber terminal to which the
message is being routed. On DataTAC 4000
systems the field (also known as Terminal ID)
is ASCII-encoded in 8 bytes. On the other
systems it is binary encoded in 4 bytes (the
first four bytes of this 8-byte field are
reserved).
Save Bytes Supplied by the host and used by the network
to tie the confirmation to the original host
request. Save bytes are ASCII for DataTAC
4000 systems. Save bytes can be ASCII or
binary for DataTAC 5000 and 6000 systems.
Response Code Known as Acknowledgment code in
DataTAC 4000 systems, this field indicates
the delivery status of the message to which
the save bytes refer. On DataTAC 4000
systems, acknowledgments are indicated by
the ASCII value ‘00’. On other systems,
acknowledgments are indicted by any value
(ASCII-encoded hex) from ‘08’ through ‘0F’.
NAKs (negative acknowledgments) are in the
range of ‘10’ to ‘A0’ for DataTAC 4000
systems and in the range of 40-97, A0-A5 for
DataTAC 5000 and 6000 systems. DataTAC
5000 and 6000 systems also have these
additional response codes:
‘A1’ Terminal message in progress
‘A2’ Terminal out of service
‘A3’ Invalid session or host ID (invalid
routing info.)
‘A4’ Maximum terminal queue exceeded.