Specifications

i50 Manual (5.10)
Page 48
© 2015 Datalink Systems, Inc.
www.datalinksystemsinc.com
Use the “Query status” command to check which network the i50 is using. This command should be
sent periodically to confirm the i50 is still turned on and connected. Initially, this command can be
sent to the broadcast IP address (255.255.255.255) when connecting via dial-up or Wi-Fi. When the
i50 replies, its IP address will be contained in the from address of the response. Further packets can
then be sent directly to the i50’s IP address.
The “Send message” command is used to send text messages over the network. When an
<Address> parameter is supplied, the message will be forwarded to that email address. Otherwise,
the message will be sent to DataHost/WebGate users. Responses are returned to indicate the status
of the message. “Queued” means the message has been accepted for transmission. “Rejected”
indicates the message has been rejected, or cannot be sent to the destination. The “Sent” response
is returned when the message has been delivered to its destination.
A unique combination of <MsgID> and <UserID> should be used for each message sent. If a
message is already queued with the same ID, the i50 will respond with an “ID exists” response.
11.2 Commands received from i50
When the i50 receives a message, it will output an unsolicited command as follows:
Command
Description
Parameters
Responses
“R”
Message
received
<MsgID><UserID><Subject><Address><Message>
“x”, “r”, “o”
Response
Description
Parameters
“x”
Message rejected
<MsgID><UserID>
“r”
Accepted
<MsgID><UserID>
“o”
Read
<MsgID><UserID>
Where the parameters are:
<MsgID> Message ID (0-16777215)
<UserID> User ID if message is from a DataHost/WebGate user
<Subject> Email subject if message is an email
User name if message is from a DataHost/WebGate user
<Address> Email address if message is an email
<Message> Message body
When such a command is received, an appropriate response must be returned to the i50. If no
response is received, the i50 will retry the message for up to an hour.
Each new message should contain a unique ID, although this is not guaranteed. When a duplicate ID
is received, it may be useful to compare the data fields to confirm whether the message is a retry or
not. When a retry is detected a response must still be returned, in case the previous response was
lost.