Receiving an SMS using HTTP

Overview

The MX Telecom SMS Server allows SMS messages to be received using HTTP. This page details the format of the HTTP requests which are send by the MX Telecom SMS Server to allow the receipt of SMS text messages by external software systems.

Contents

• Receiving SMS messages using HTTP
• Message format
• Response to the server
• Security considerations

Receiving SMS messages using HTTP

The MX Telecom SMS Server will push received SMS messages by making an HTTP GET to the provided URL to indicate the receipt of an SMS message.

Message format

On receipt of an SMS we will send an HTTP GET request to your server, using the parameters included in the table below:

Parameter	Description
smsfrom	Originator of the message
smsto	Shortcode or MSISDN of virtual mobile/sim card
smsdate	Format: yyyy-MM-dd HH:mm:ss
*network	Network (if known). Required for messages to shortcodes. Click here for a table of network codes.
smsid	Unique ID for this message
smsmsg	Message body (in ISO-8859-15) or if bits=8 hex encoded 8bit data
bits	Describes the content of the smsmsg parameter 7 - 7bit text 8 - 8bit hex-encoded data 16 - best-effort 7bit text representation of the UCS2 data carried in the smsucs2 parameter
*smsudh	UDH
*smsc	SMSC (if known - currently only used with SIM card receivers).
*smsucs2	For unicode messages - hex encoded UCS2 message body

Note that optional parameters are marked with a *

When sending HTTP GETs we will attempt up to 10 message deliveries, until successful, with an exponential delay between sending (30 seconds, 60 seconds, 120 seconds etc).

It is the customers' responsibility to filter duplicate requests (based on smsid) - these might occur if for some reason we did not receive the HTTP response from a previous attempt within 60 secs (perhaps because the reply took longer than that or there was a network outage etc).

https://server.com/drpt.cgi?smsfrom=447931123456&smsmsg=Hello+World&
  smsto=913&smsid=17221293&smsdate=2002-04-30+21%3A58%3A00 

Response to the server

The customer's server should respond with an HTTP 200 response with a non-empty body. This response must be given in a timely manner (sub 10 seconds) currently we do not abandon a request (waiting for the HTTP response) until 60 seconds have passed but this might be reduced in future.

Security considerations

To ensure the authenticity of the HTTP requests you should only accept requests from the following MX Telecom IP addresses:

• 83.166.68.0/23 (ie 68.0 -> 69.255)

The HTTP endpoint can be an HTTPS (SSL) URL to protect the data whilst in transit.

About MX Telecom MX Telecom is a leader in wireless technology. MX Telecom offers an easily accessible gateway to data, voice and video messaging services including 2-way and premium SMS, multimedia messaging, interactive voice response, location-based services, video short codes, Internet and TV related solutions. For more information, MX Telecom can be reached on 0845 666 7778, or via email at sales@mxtelecom.com.