Receiving mobile originated SMS messages
Eseye's AnyNet Messaging Service and SMS API enable customers to intercept SMS messages sent to an MSISDN and deliver them to a customer's SMS application.
When IoT devices and other SMS applications send SMS messages to the designated MSISDN (API MSISDN) linked to the customer's Infinity Classic account, the AnyNet Messaging Service intercepts the SMS messages and delivers them to the customer's application.
To receive mobile originated SMS messages from the SMS API, customers must first:
- Set up a HTTP endpoint application – this application receives SMS messages from the SMS API.
- Provide details to Eseye Support – these details are typically provided when ordering the SMS API and include the URL of the HTTP endpoint to which the AnyNet Messaging Service will forward messages.
- Enable reception of SMS messages in Infinity Classic – using the Infinity Classic web interface.
- Send a test MO SMS message – checks that the system is working as intended.
Set up a custom HTTP endpoint application
To receive MO SMS messages, the customer must create an application (HTTP endpoint) that is capable of receiving HTTP POST messages from the SMS API. The SMS message contents (text or data) from the device are contained in the message payload.
MO message format
The AnyNet Messaging Service sends MO SMS PDU messages that may include the fields listed in the table below.
The specific fields depend on the type of PDU (Deliver-SM, Submit-SM, Status-Report, etc) and the information supplied by the originating network.
| Field | Type | Description |
|---|---|---|
| source | string |
The source MSISDN of the originator of the message. If omitted, the source was an SMS API. |
| destination | string | The destination MSISDN, which is link to the customer's HTTP SMS endpoint. |
| message_id | string | A unique identifier for the message that can be used for tracking. |
| text | string |
The human-readable SMS message content. |
| binary | hexadecimal string |
Hexadecimal representation of the Submit-SM PDU. To decode the contents, use an SMS decoder. Click here for an online SMS PDU decoder. |
Provide details to Eseye Support
Once the endpoint application is created, customers must send the following information to Eseye in order to configure their MO SMS application.
- The URL of the HTTP endpoint application , which is stored as the MO destination URL in the Infinity Classic web interface.
-
The Infinity Classic account to which the application is to be linked.
This will determine the charges (if any) for the messages from the SMS API to the customer's application.
Enable reception of MO SMS messages
The AnyNet Messaging Service collects mobile originated (MO) SMS messages and sends them to the customer server when the following conditions are met:
- SMS MO is enabled on the customer's SMS API configuration (MO Enable option in Infinity Classic)
- The source device MSISDN is included on the SMS allowed list
- If an optional IP address allowed list exists, the source device is included
To enable reception of MO SMS messages:
- Log in to the Infinity Classic web interface using the customer account to which the SMS API is linked.
- Display the Settings > Messaging API page.
- Under Actions, select
. - Select the Mobile Originated Enable check box.
- If required, edit the Mobile Originated POST URL, which is the URL of the customers HTTP endpoint application.
- Select Save.
Test MO SMS message reception
Once configured and enabled, the customer can send an SMS message from an IoT device (or application) to the MSISDN (API MSISDN) linked to their Infinity Classic account. The AnyNet Messaging Service will intercept the message, look up the MSISDN and re-route it to the customer's application.
