Table of Contents
Advertisement
IridiTRAK Installation & User Manual
Send a message to IridiTRAK
Using Short Burst Data: SBD
Short Burst Data, SBD, can be used to delivery Position Tracking reports to
predetermined email addresses. The email addresses are programmed with your
Service Provider to send directly from the Iridium gateway. SBD must be provisioned
for this IMEI for this to operate. SBD email destinations are setup on the SBD
provisioning website for your particular Iridium IMEI of your IridiTRAK. Once SBD
has been activated with your Service Provider, you can simply activate position
tracking via SBD in the LMS.
In order to send a MT message from the Vendor Application to the Field Application,
the Vendor Application must send the message to the GSS (Gateway Server) where
it will be queued for delivery awaiting contact from the ISU (IridiTRAK) to retrieve it.
The message will remain in the queue for up to five (5) days awaiting contact from
the ISU to retrieve it. After five days the message is removed from the queue
automatically by the GSS.
• Messages sent to an ISU from the VA are sent to the email address:
data@sbd.iridium.com
• Placing at least one, and up to a total of four, IMEI(s) into the subject line of the
email identifies the destination ISU(s) (IridiTRAK). If there is more than one
destination IMEIs then list the additional IMEIs on the subject line separated with a
single space between each IMEI.
• The email message must contain a properly formatted sender ("From:" address),
otherwise the message will be dropped by the Gateway Server.
• The data message (e.g. IridiTRAK remote command) to the ISU must be carried
as an attachment to the email:
• The attachment name must have a '.sbd' file name extension: E.g.
'importantdata.sbd'
• File names can be up to 80 characters. (Including the .sbd extension.) File
names are not case sensitive.
• The maximum size of the binary message (not the Base64 version) is ISU
specific and is between one byte and the maximum MT message size. The
GSS will reject message sizes that are too large for a particular ISU type.
• The attachment must use standard Multipurpose Internet Mail Extensions
(MIME) Base64 encoding as defined in RFC 2045.
Page 36 of 46
Advertisement
Table of Contents
