iSMS Protocol

Overview

iSMS protocol is an HTTP-based protocol that enables the SMS Site Server to pass a mobile originating (MO) SMS to a content application/service and get a response back from the content application that will be sent back to the originating mobile as a mobile terminated (MT) SMS. iSMS protocol also includes a mechanism of passing a delivery report from SMS Site Server to a content application.

The iSMS protocol defines:
• The HTTP POST request for MO SMS from SMS Site Server to content applications
• The iSML (Interactive SMS Markup Language) that a content application must send
back to SMS Site Server in the HTTP response for MO SMS
• The HTTP GET request for delivery report from SMS Site Server to content
applications
• The HTTP response from content applications to SMS Site Server acknowledging the
delivery report

iSMS Protocol Description

When a mobile sends an SMS that is received by SMS Site Server from the SMSC, SMS Site Server will decide which content application the MO SMS belongs to and forward it to the correct one.

iSML Description

iSML is an XML document that defines the SMS response from a content application.
Example of a simple iSML response:

Hello World!

When SMS Site Server receives the above iSML from a content, it will send an MT SMS
back to the originating mobile containing the text “Hello World!”
Example of an empty iSML response:


When SMS Site Server receives the above iSML from a content, it will not send any MT
SMS back to the originating mobile.

Interactive Session

The previous iSML examples are simple, i.e. a mobile sends an MO SMS and the content
sends back a reply MT SMS and it stops there.

Interactive SMS Session Example

User sends an SMS, which will be routed to the survey content service.
The content service will respond back with an SMS prompting the user to enter his
name.When the system receives the name, it will send back the first survey question and so
forth. This kind of survey application can be implemented with the following iSML
documents:

First document:




Halo, terima kasih atas ketersediaan anda ikut survey
Silakan ketik nama anda.




In the above iSML example, whatever response the user sends will cause the SMS Site Server
to issue an HTTP POST request to URI path /savename.jsp (the same host and port as the
current context), passing the usual header and request parameters (see section 2.1 MO SMS:
HTTP Request From SMS Site Server To Content).
Your application at /savename.jsp should process the SMS, which should contain the user
name. Then your application will produce the following second document (either by
redirecting to another URL or outputting it directly on the response).
Second document (after you process the user name in /savename.jsp in the above example):




<%=username%>, setujukan anda Abubakar Baasyir divonis 4 tahun sebagai
teroris?
SETUJU
TIDAK




This time the above document tells the SMS Site Server to send back an SMS to the user and
present the two options, i.e. SETUJU or TIDAK. When the user responds with an SMS
“SETUJU”, the SMS Site Server knows that it has to issue an HTTP POST request to the
URL /setuju.jsp.

If the user responds with an SMS other than SETUJU or TIDAK (and assuming there is no
other application matching that answer keyword defined for the short code), SMS Site Server will issue an HTTP POST request to URL /showhelp.jsp, as indicated by the nomatch element.

Note that in order to take advantage of this feature, the interactive session must be explicitly enabled for your content application. Please contact the operator administrator.

iSML DTD