An application must be connected to the hub to send messages to other applications.
bind_transmitter command can be used by an application to establish a session for only sending messages.
bind_transceiver can be used for both receiving messages and sending them.
data_sm is used by the application to send a message for another application to the hub. The hub will respond with a
data_sm_resp containing a message identifier for the submission.
The message content for the destination application is contained in:
- submit_sm: short_message or message_payload TLV field
- data_sm: message_payload TLV field
See communication protocol for details.
Depending on the message mode specified in the application profile or in the message submission, the destination application does not need to be connected to the hub at the time the sending application sends the message to the hub. See message modes below:
|Store and forward (default)||If the destination application is unable to accept the message, it will be stored and re-attempted until it expires.|
A destination application may not be able to accept a message if it is not connected to the hub or it returns a negative acknowledgement when delivery to it is attmepted.
|Datagram||Not currently supported|
|Transaction||Not currently supported|
Updated 4 months ago