Mobile Originated Messages#
A subscriber can reply to a Partner’s message. To enable this, the Partner should configure the ability to receive incoming Mobile Originated messages.
Please contact your supervising manager to activate this functionality. Be prepared to provide the following information:
The keyword with synonyms (or a regular expression) to identify Partner’s messages.
The service name to which the service will be provided.
The message text to be sent to the subscriber if the Partner’s server is unavailable.
The deliver_sm
PDU is used to send messages from the Service Provider’s platform to the Partner’s service.
The Partner responds to the deliver_sm
packet with the deliver_sm_resp
packet where command_status
= 0.
If no response is received from the Partner within the specified timeout period, the message from point 3 will be sent to the subscriber.
The table below describes the parameters used in the Service Provider’s request when processing incoming messages.
Parameter |
Type |
Description |
---|---|---|
source_addr |
string |
Sender. The subscriber’s phone number. |
destination_addr |
string |
Receiver. The service name. |
short_message |
string |
Text of the message from the subscriber.
Long messages made up of multiple parts can be sent to the Partner in different ways:
|
data_coding |
integer |
Encoding scheme/type of the message text.
Depending on the content, the text is sent in one of two encodings:
It is also possible to use the ASCII encoding for |
If necessary, additional TLV parameters containing extended message information can be included in the packet.