Short Message Peer to Peer (SMPP) InterfaceSpecification

http://www.routetd.comsupport@routetd.com

Page 1 / 7Document revision 1.0 | October 2010

Table of ContentsIntroduction.............................................................................................................................3Requirements...........................................................................................................................3RouteTD supported PDU's......................................................................................................4Required Parameters...............................................................................................................5Delivery Reports.....................................................................................................................6Delivery status description......................................................................................................6Possible status and status descriptions.................................................................................................................................................6Useful links.............................................................................................................................7

Page 2 / 7

Introduction

RouteTD Messaging Platform uses the SMPP v3.4 Protocol Specification. Reading this document it is assumed that you are familiar with SMPP v3.4 Protocol Specification.

Requirements

To use RouteTD SMPP messaging system, you need to meet some requirements:

• You need to have RouteTD active account. If you do not have RouteTD account, you can always register and create one at http://routetd.com/en/register/600.html

• You need to have positive account balance. After creating account – you will get 0.2 Eur balance to test system

• You need to have SMPP API's. You can try sourcing an API from the following websites: http://www.kannel.org, http://www.nowsms.com. Once you have sourced an API, you can connect to RouteTD messaging system

Page 3 / 7

RouteTD supported PDU's

RouteTD supports following PDU's from ESME to SMSC:

• bind_receiver

• bind_transmitter

• submit_sm

• enquiry_link

• delivery_sm_resp

• unbind

RouteTD supports following PDU's from SMSC to ESME:

• bind_receiver_resp

• bind_transmitter_resp

• submit_sm_resp

• enquiry_link_resp

• delivery_sm

• unbind_resp

If you meet above mentioned requirements you can use smsc.routetd.com on tcp port: 8888 to connect to RouteTD messaging system.

To successfully bind to RouteTD messaging system, following parameters are required:

• system_id

• password

After successful receiving of 'submit_sm' command, RouteTD will give to message unique message id, or reject message and provide reason of rejection.

Page 4 / 7

Required Parameters

Required parameters for successful submitting of PDU are:

• destination number – Valid GSM number in full international format WITHOUT + or 00 at front.

• source address – for alphanumeric source address, allowed character length is 11 characters. For numeric source address allowed character length is 20 characters.

• destination TON – for alphanumeric source address use destination TON 5, for international formated source address use destination TON 1

• destination NPI – for alphanumeric source address use destination NPI 1, for international formated source address use destination NPI 1

RouteTD supports ISO-8859-1 8-bit text, GSM 03.38 7-bit text and UNICODE data coding

To property encode message, PDU data coding must follow scheme described in table:

Type Data coding

ISO-8859-1 8-bit text 0

GSM 03.38 7-bit 1

UNICODE 8

Long SMS ISO-8859-1 8-bit text 0

Long SMS GSM 03.38 7-bit 1

Long SMS UNICODE 8

Default timeout for enquire_link command is 30 seconds

Page 5 / 7

Delivery Reports

The RouteTD messaging system will return a delivery report for a specific message to the client application when the registered_delivery field, while submitting the message, is set to 1. In order to retrieve the delivery report from our server the client will have to connect to the RouteTD messaging system in the receiver mode.

Delivery status description

• DELIVRD - Message delivered to handset

• ACCEPTD - Message is accepted in our system

• EXPIRED - Message validity period expired

• UNDELIV - Message is undeliverable

• REJECTD – Message is rejected

• DELETED – Message is deleted

• UNKNOWN – Unknown status

Possible status and status descriptions

Status Description

0 DELIVRD

5 EXPIRED

10 DELETED

41 ACCEPTED

15 UNDELIV

58 FAILED

74 REJECTED

99 UNKNOWN

-5 ACCEPTED

13 NO CREDITS

3 NETWORK NOT ALLOWED

8 UNKNOWN ACCOUNT

20 DEST ADDR NOT SET

25 INVALID SOURCE ADDR

60 INVALID TON / NPI

Page 6 / 7

Useful links

SMPP - Short message peer-to-peer protocol on Wikipedia:

http://en.wikipedia.org/wiki/Short_message_peer-to-peer_protocol

Long sms (Concatenated SMS) on Wikipedia:

http://en.wikipedia.org/wiki/Concatenated_SMS

SMS on Wikipedia:

http://en.wikipedia.org/wiki/SMS

Kannel:

http://www.kannel.org

now.sms:

http://www.nowsms.com

Page 7 / 7