SMS Gateway
Interface Description
Adaptation of SMPP 3.4 v1.1

Document nameAdaptation of SMPP 3.4 v1.1
Document numberEKJ11002SEC
Revision1.1
AuthorMartin Kristell
Date2013-04-15
Information classOpen Information
ReviewerJonas Rexeke
Review date2013-04-15
CompanySPIRIUS AB
VAT/REG number556788-4183
Postal addressBox 67
371 21 KARLSKRONA
Telephone number+46 (455) 65 55 00
Fax number+46 (455) 65 55 19
Home pagewww.spirius.com

© Copyright SPIRIUS AB 2018

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. SPIRIUS AB shall have no liability for any error or damages of any kind resulting from use of this document.

1. INTRODUCTION

1.1 Scope

This document explains valid BIND operations and specifies the combinations of TON and NPI settings that can be used with Spirius SMPP interface. It also specifies the SMPP error codes given from Spirius in response to the “query_sm”-command. In the response a message state will be given along with the error code. Available message states are not specific to Spirius but specified in the SMPP Protocol Specification v3.4 issue 1.2, section 5.2.28.

2. SMPP MODES OF OPERATION

2.1 Valid Bind Combinations

The Bind operation may be viewed as a form of SMSC login request to authenticate the client wishing to establish a connection. A client to Spirius SMPP interface may bind as either transmitter, receiver or transceiver.

Valid BIND combinations for a client to Spirius SMPP interface are:

  • Bind 1 Receiver
  • Bind 1 Transmitter
  • Bind both 1 Receiver and 1 Transmitter
  • Bind 1 Transceiver (duplex mode)

A Spirius account holder can simultaneously bind maximum one receiver and one transmitter. A transceiver will be counted as one of each. Attempting to bind e.g. a transmitter and a transceiver from the same account will result in both sessions being disconnected.

Please refer to section 4 of the SMPP 3.4 specification for further information.

3. TYPE OF NUMBER (TON) AND NUMBER PLAN INDICATOR (NPI) SETTINGS

3.1 Valid Combinations of Ton and NPI

The SMPP specification v3.4 in section 5.2.5 and 5.2.6 defines 7 different Type of Number (TON) and 10 different Number Plan Indicator (NPI) settings, but only the ones that are realistic to use for SMS services are supported by Spirius SMPP interface.

Below is the list different TON and NPI implemented by Spirius SMPP interface:

ValueTON
0Unknown
1International
2National
3Network Specific
5Alphanumeric
ValueNPI
0Unknown
1ISDN (E163/E164)
2Accepted, No Error

The combinations that are valid to use with Spirius SMPP component in combination with source address for the submit_sm command are:

TONNPIExpected result
0 - Unknown0 - UnknownDefined by the receiving SMSC
1 - International1 - ISDN (E163/E164)Accepted, No Error
2 - National1 - ISDN (E163/E164)Accepted, No Error
3 - Network Specific0 - UnknownAccepted, No Error
5 - Alphanumeric0 - UnknownAccepted, No Error

The combinations that are valid to use with Spirius SMPP component in combination with destination address for the submit_sm command are:

TONNPIExpected result
0 - Unknown0 - UnknownDefined by the receiving SMSC
1 - International1 - ISDN (E163/E164)Accepted, No Error
2 - National1 - ISDN (E163/E164)Accepted, No Error

Other combinations will result in one of the error-codes defined in the SMPP specification.

4. SMPP ERROR CODES

SMPP error codes given from Spirius in response to the “query_sm”-command.

4.1 Mobile Terminated Messages

Error CodeLocationDescription
0UnknownUnknown
1No locationNo Error
100HLRPending
101HLRSystem Failure
102HLRData Missing
103HLRUnexpected Data Value
104HLRFacility Not Supported
105HLRUnknown Subscriber
106HLRTeleservice Not Provisioned
107HLRCall Barred
108HLRAbsent Subscriber
198HLRTimeout
199HLRUnknown
200MSCPending
201MSCSubscriber Busy For MT-SMS
202MSCUnidentified Subscriber
203MSCIllegal Subscriber
204MSCIllegal Equipment
205MSCSystem Failure
206MSCData Missing
207MSCUnexpected Data Value
208MSCFacility Not Supported
209MSCMessage Waiting List Full
210MSCSM Delivery Failure
211MSCAbsent Subscriber SM
298MSCTimeout
299MSCUnknown
300GMSCPending
301GMSCError
302GMSCExpired
304GMSCQueued
305GMSCWaiting For Timeout
398GMSCTimeout
399GMSCUnknown

5. APPENDIX

5.1 Document History

RevisionDateSignatureComments
01 BETA2011-01-28KJFirst beta version
1.02011-02-15KJFirst version ready
1.12013-03-11MKSpecified valid combinations of TON and NPI