Messages can be sent as email or XML interface.
Satellite modem's serial number + x1@orbcomm.net
Example: m99999999999x1@orbcomm.net
5-byte uplink command. Put this in the subject line:
[COMMAND:ACK]
A message has variable length data. No special subject line is needed to indicate it's a message.
Adding [CONFIRM=#] to the end of the subject will get you a confirmation email response.
3 = Email response on failure to deliver to SC, no email on success.
4 = Email response on failure to deliver to SC, and also on success.
[CONFIRM=4]
The message ID header can be set by the customer in the original SC-terminated message by specifying a unique string of up to 40 characters in a SMTP header field entitled “Message-ID”. This ID will be preserved as part of the OMS Message ID returned in the confirmation. They must be unique.
It will not be delivered to the SC.
Binary messages should carry the field:
Content-Type: application/octet-stream
Additionally, binary messages should be MIME-encoded and should specify that encoding in the message header:
Content-Transfer-Encoding: Base64
The priority of an SC-terminated message can be set using the SMTP header of the same name. ORBCOMM recognizes values of “Non-urgent”, Normal”, and “Urgent”.
Priority: Non-urgent
Raw binary file should be attached, with an 8.3 format filename, ending in .dat. Name does not seem to matter.
test1.dat