Customer Guide
The content of this document are copyright and remain the property of Unicel Technologies Pvt. Ltd. This document
is not to be reproduced in any form, whether electronic, mechanical or by any other means without written permission
of Unicel Technologies Pvt. Ltd.
Table of Contents
Preface............................................................................................................................................. 3
A Few Assumptions ........................................................................................................................ 3
Required Environment: ................................................................................................................... 3
Terminology.................................................................................................................................... 4
Introduction to SMPP Protocol ....................................................................................................... 4
Getting Started ................................................................................................................................ 4
Connecting through SMPP ............................................................................................................. 5
Protocol Description Units (PDUs) supported by Unicel ............................................................... 5
PDUs Description ........................................................................................................................... 5
Delivery reports .............................................................................................................................. 6
Enquire link ..................................................................................................................................... 6
Incoming Messages ......................................................................................................................... 7
Status Codes ................................................................................................................................... 8
Sample PDU.................................................................................................................................... 9
SUBMIT_SM PDU for text message (upto 160 characters) ...................................................... 9
SUBMIT_SM PDU for multipart (concatenated) text messages (153 char message + 6 char
UDH)......................................................................................................................................... 10
SUBMIT_SM PDU for binary message (ringtones, picture messages, WAP Push messages
etc.)............................................................................................................................................ 11
DELIVER_SM PDU for delivery receipt ................................................................................. 12
DELIVER_SM PDU for Incoming MO message ..................................................................... 13
References ..................................................................................................................................... 14
Preface
This guide provides specifications of connecting to Unicel via SMPP. This guide is intended for
developers planning on integrating their systems with SMPP Client/Server Application to
connect to Unicel SMS gateway.
A Few Assumptions
This guide assumes that you are familiar with and have experience applying the following
technologies and concepts:
Required Environment:
In order to transmit messages via SMPP you would need to have the below ports opened along
white listing.
Connecting via SMPP requires a thorough understanding of the SMPP Protocol. Please read the
SMPP 3.4 specifications available from www.smsforum.net before reading the rest of this
document. This document only contains information on how to connect Unicel SMS Gateway
using SMPP.
Getting Started
In order to test Unicel gateway you need a Unicel Demo account for which you could just send an
email to sales@uniceltech.com. After submitting this online form you will immediately receive an
email confirmation for the same. In case you are not receiving it, kindly drop a mail to sales. Once
the account is created by our support team, you will receive account details on your mail along with
an SMS confirmation.
Normally this demo will remain active for 3 days with a SMS credit of 100. During this demo period
our support and sales team will be there to address all your queries. After successful completion of
Demo, our sales team will help you in converting it into live.
Connecting through SMPP
The Unicel Messaging Platform can act as an SMPP SMSC. Customer can directly send a
connection request to Unicels SMPP server by using the below connectivity parameters in their
own SMPP Client or Unicel SMPP Client (refer for understanding Unicels SMPP Client):
PDUs Description
Bind transmitter: If application is bind as transmitter, then the ESME or SMPP Client
sends short messages to the SMSC and receives the corresponding SMPP responses from
SMSC.
Bind-receiver: If application is bind as receiver, then the ESME or SMPP Client receives
short messages from the SMSC and returns a corresponding SMPP message response to
the SMSC.
Submit_SM is used by ESME (External Short Message Entity) or SMPP Client to submit
short message to the SMSC for the transmission of the specified short message entity
(SME).Unicel supports two types of messages 1. Short messages (up to 160 characters)
and large messages (more than 160 characters) in its Calling Application.
Deliver_sm is sued by the SMSC to send message to an ESME or SMPP Client regarding
to the message sent by the Client. SMSC returns one unique ID usually called Message ID
and one Error Code. This Error Code describes, what happens with your message which
you have sent means message delivered successfully or not. These Deliver_sm are sent in
response to SMS message whose registerd_delivery parameter requested them.
Enquire_link specifies whether a message can be sent by either SMPP Client or the SMSC
that is used to provide a confidence check of the communication path between SMPP Client
and the SMSC. On receipt of this request the receiving party sends a response that verifies
the application connection between the SMSC and SMPP Client(ESME).Or in short we can
say that it is used by either SMPP Client or SMSC to ping the other side.
Delivery reports
For each message which has been previously submitted with the submit_sm operation and where
delivery report has been requested via the registered_delivery parameter, RoutoMessaging
SMSC will generate delivery report and submit to the appropriate customer through deliver_sm.
The delivery receipt data relating to the original short message will be included in the
short_message field of the deliver_sm.
In order to receive delivery reports over SMPP, you will need to bind as either transceiver or
receiver, since delivery reports cannot be delivered if the customer is bound exclusively as
transmitter. To ensure proper receiving of delivery reports, you would need to verify that your
SMPP client application is able to handle deliver_sm PDUs.
In delivery reports, all time/date related fields will be in ASCII with the following format:
YYYYMMDDhhmm where:
YYYY digits of the year (e.g. 2011)
MM month (01-12)
DD day (01-31)
hh hour (00-23)
mm minute (00-59)
Enquire link
The enquire link commands are used to check the connectivity between ESME and SMSC and
can be issued from both entities.
Please note that our default timeout for these commands is 30 seconds. In case Routo SMSC
does not receive a valid response within 30 seconds after sending the 'enquire_link' command it
will treat the connection as expired.
A common problem which might appear in case there is an unstable IP connection between
ESME and SMSC is that ESME will not receive a valid 'enquire_link_response'. If that happens,
ESME will usually try to establish another 'bind_transmitter', 'bind_transciever' or 'bind_receiver'
command, thus it will increase the number of parallel connections.
Once this number reaches the maximum allowed for parallel connections, all other attempts to
bind will be rejected which resulting in inability for ESME to connect to SMSC.
In case this happens, the customer should contact our 24/7 support team and ask them to delete
these 'ghosts' connections in order to be able to re-establish a valid connection to our SMSC.
Incoming Messages
Another system which is quite popular is an 'incoming' system which provides a customer with a
dedicated number (long international number, not a short code). This number allows you to
receive the message from any location in the world. In other words the sender always sends the
message to that number regardless of his current location and you will receive it over SMPP
protocol ('deliver_sm' SMPP command).
Status Codes
032 EXP-MEM-EXCD Message rejected because the MS doesn't have enough memory.
b. SMPP - http://en.wikipedia.org/wiki/Short_message_peer-to-peer_protocol