Scribd
Upload
57 views

World-Text API SMPP Intergration Specification

This document provides specifications for integrating with the World-Text API using SMPP protocol version 3.3 or 3.4. It describes connection settings including host/port information and required authentication parameters. It also outlines various message handling behaviors and status codes. Source addresses are initially limited but can be customized, and proper TON/NPI settings are specified for alphanumeric sources versus destinations.

Uploaded by

Hafedh Trimeche
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
57 views

World-Text API SMPP Intergration Specification

This document provides specifications for integrating with the World-Text API using SMPP protocol version 3.3 or 3.4. It describes connection settings including host/port information and required authentication parameters. It also outlines various message handling behaviors and status codes. Source addresses are initially limited but can be customized, and proper TON/NPI settings are specified for alphanumeric sources versus destinations.

Uploaded by

Hafedh Trimeche
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

World-Text API

SMPP Intergration Specification

World-Text API SMPP Intergration Specification


Version: 1.61 Document Number: Author: Neil E. Vince Last Modified: 15 Jun 2005

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

Table of Contents
1 SMPP Version .............................................................................3 1.1 SMPP Commands........................................................................... 3 2 Connection Settings................................................................... 4 2.1 Firewall............................................................................................ 4 2.2 Host & Port Information................................................................... 4 2.3 Simulator Host & Port Information................................................... 4 2.4 System ID & Password.................................................................... 4 2.5 System Type.................................................................................... 5 2.6 SMPP Version................................................................................. 5 3 Miscellaneous Settings............................................................... 6 3.1 Enquire Link..................................................................................... 6 3.2 Query SM......................................................................................... 6 3.3 SMPP Server Restarts..................................................................... 6 3.4 Server Rebinds................................................................................ 6 3.5 Custom Status Values..................................................................... 7 4 Source Addresses....................................................................... 8 4.1 TON and NPI Settings..................................................................... 8

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

1 SMPP Version
The provided SMPP support is SMPP version 3.3 and a cut down version 3.4, the full SMPP specification can be downloaded from the World-Text web site at www.world-text.com/smpp and www.smpp.org for the 3.4 specification. Version 5.0 SMPP support is expected Q4 2005. More information on SMPP and additional documentation can be obtained from the SMS forum at www.smpp.org.

1.1 SMPP Commands


The following list contains all the commands supported by our API:

Bind Transmitter Bind Transmitter Response Bind Receiver Bind Receiver Response Bind Transceiver Bind Transceiver Response Unbind Unbind Response Submit SM Submit SM Response Deliver SM Deliver SM Response Query SM Query SM Response Enquire Link Enquire Link Response Generic Nack

Additional commands can be supported on request.

1.2 Optional Parameters


Optional parameters (v3.4) are not supported, this is due to the lack or varied level of support by operators that we connect to.

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

2 Connection Settings
2.1 Host & Port Information
Host Name TX Port RX Port TRX Port smpp.world-text.com 8010 8010 8010

Please check back regularly with the World-Text web site for updates to this information as we add additional SMPP resilience to our network.

2.2 Simulator Host & Port Information


Host Name TX Port RX Port TRX Port smpp.world-text.com 2775 2775 2775

2.3 System ID & Password


The System ID is made up of the word two characters sm and your Account ID, this account ID can be is on your account adminstration page which can be accessed by logging into your account from www.world-text.com. Example: Account ID: 1000 System ID : sm1000 The password is the same as that chosen when you signed up to World-Text. These fields are required for the Bind Transmitter/Receiver/Transceiver PDU's. Currently SMPP accounts needs to be activated by World-Text support who you should contact at [email protected].

2.4 System Type


The System Type should always be set to: SMPP

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

2.5 SMPP Version


The SMPP Version must always be set to ether 0x33 (hex 33) for version 3.3 or 0x34 (hex 34) for version 3.4. If this is not set your bind will be rejected.

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

3 Miscellaneous Settings
3.1 Enquire Link
Our servers dispatch Enquire Link PDU's every 90 seconds, if a correctly sequenced Enquire Link Response PDU is not received the link will be disconnected without an Unbind request and the socket closed. Enquire links to our server should be sent no more that once in every 60 second period.

3.2 Query SM
Delivery receipts are returned for all messages irrespective of final message status, the maximum period for delivery receipts is 72 hours from dispatch. Therefore it is not necessary to dispatch Query SM PDU's to our servers unless your application does not support them. Messages that have already reached a final status will not be available to Query SM requests.

3.3 SMPP Server Restarts


From time to time the SMPP server is restarted to allow for upgrades and configuration changes, although we try to keep these to a minimum they are required. During a restart clients are disconnected and all Submit SM PDUs that have been successfully responded to with a Submit SM Response, but have not yet been dispatched, are cached to disk. On start-up these data files are reloaded so that no submitted data is lost.

3.4 Server Rebinds


In the event of a receiving an Unbind request from the server you should acknowledge the request with an Unbind Response and disconnect,i f they do not disconnect the connections are forceably closed. Once disconnected your application should automatically rebind to the server, the frequency of rebinds should not be more that once every 30 seconds.

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

3.5 Custom Status Values


In addition to the standard SMPP status values returned in SMPP Message Header, the following are also valid vendor specific values. Value 0x400 Meaning Insufficient credit remaining on prepay account or credit limit reached (invoiced accounts)

1.61

Version: 1.61

World-Text API

SMPP Intergration Specification

4 Source Addresses
When the SMPP account is activated it is created only to allow transit of messages with the alphanumeric source address World-Text or SMSAlert. If you require to use a different source address then please see the information on our web site.

4.1 TON and NPI Settings


When creating your SMPP packets for alaphnumeric source addresses you should use a Type of Number setting of 5 and a Numbering Plan Indicator of 6. For your destination address the TON and NPI should both be set to 1.

1.61

Version: 1.61

You might also like