Short Message Peer to Peer Protocol Specification v3

1 Page 1 of 169 Issue Message peer to peer Protocol Specification Version:- 12-Oct-1999 Issue 2 of 169 SMPP Developers Forum Issue Protocol Specification Short Message peer to peer Protocol Specification Issue 1999 SMPP Developers Forum. COPYRIGHTAll rights reserved. This document or any part thereof may not, without the prior writtenconsent of SMPP Developers Forum, be copied, reprinted or reproduced in any material formincluding, but without prejudice to the foregoing and not by way of exception photocopying,transcribing, transmitting or storing in any medium or translating into any language, in any formor by any means, including but not limited to, electronic, mechanical, xerographic, optical,magnetic, digital or other THE GREATEST CARE HAS BEEN TAKEN TO ENSURE THE ACCURACY OF THEINFORMATION AND DATA CONTAINED HEREIN.

2 SMPP DEVELOPERS FORUM DOES NOTWARRANT THE ACCURACY OR SUITABILITY OF SAME FOR ANY SPECIFIC USE. SMPPDEVELOPERS FORUM EXPRESSLY DISCLAIMS ALL AND ANY LIABILITY TO ANY PERSON,WHETHER A PURCHASER OR OTHERWISE, IN RESPECT OF ANY CONSEQUENCES OF ANYTHINGDONE OR OMITTED TO BE DONE BY ANY SUCH PERSON IN PARTIAL OR TOTAL RELIANCE UPONTHE WHOLE OR ANY PART OF THE CONTENTS OF THIS PUBLICATION OR ANY INFORMATION CONTAINED HEREIN IS BELIEVED TO BE ACCURATE AND , SMPP DEVELOPERS FORUM ACCEPTS NO RESPONSIBILITY FOR IT S USE BY ANYMEANS OR IN ANY WAY WHATSOEVER. SMPP DEVELOPERS FORUM SHALL NOT BE LIABLE FORANY EXPENSES, COSTS OR DAMAGE THAT MAY RESULT FROM THE USE OF THE INFORMATIONCONTAINED HOWSOEVER ARISING IN THIS DOCUMENT OR ANY DERIVATIVE 1:THE INFORMATION CONTAINED IN THE WITHIN DOCUMENT AND ANYDERIVATIVE THEREOF IS SUBJECT TO CHANGE WITHOUT 2.

3 THE CORPORATE NAME OF SMPP DEVELOPERS FORUM IS NORTHGROVELIMITED, COMPANY NUMBER 309113, REGISTERED OFFICE GARDNER HOUSE,WILTON PLACE, DUBLIN Protocol Specification Errata Issue SMPP Developers Forum Page 3 of 169 ErrataErratum Description of Correction to address ErratumChange Request ReferenceIn the SMPP Protocol Specification version 30-July-1999 Issue section Bind_Transceiver the interface_version field was inadvertently not included in the bind_transceiver PDU. The erratum was corrected in the SMPP Protocol Specification 12-Oct-1999 Issue as follows:In section Bind_Transceiver the interface_version field was added as a mandatory field to the bind_transceiver PDU.

4 Since it is a mandatory field all implementations of the SMPP Protocol Specification must include the interface_version field when using the bind_transceiver PDU. 4 of 169 SMPP Developers Forum Issue of ContentsSMPP Protocol Specification Table of .. Protocol Protocol Definition .. Session Description .. PDUs .. Network Layer Connections .. messages sent from ESME to Message Response from SMSC to ESME .. SMPP session sequence - ESME Transmitter .. messages sent from SMSC to Message Response from ESME to SMSC .. SMPP session sequence - ESME Message exchange between an SMSC and an ESME.

5 SMPP session sequence - ESME Transceiver .. Error Handling .. Timers .. and Forward Message Mode .. Message Mode .. Message Mode .. Types .. PDU Type and Format PDU - Type Definitions .. Parameter Field Size Notation .. PDU Format - PDU Layout .. PDU Length .. Message length and extended Message Parameters .. Parameter for SMPP Forward for SMPP Backward Compatibility .. PDU BIND Operation .. BIND_TRANSMITTER Syntax .. BIND_TRANSMITTER_RESP BIND_RECEIVER BIND_RECEIVER_RESP .. BIND_TRANSCEIVER BIND_TRANSCEIVER_RESP .. 53 SMPP Protocol Specification Table of Contents Issue SMPP Developers Forum Page 5 of OUTBIND Operation.

6 OUTBIND UNBIND UNBIND .. UNBIND_RESP .. GENERIC_NACK PDU .. GENERIC_NACK Syntax .. SUBMIT_SM Operation .. SUBMIT_SM Syntax .. and Destination Addressing .. Replace operation in SUBMIT_SM .. SUBMIT_SM_RESP .. SUBMIT_MULTI Operation .. SUBMIT_MULTI Syntax .. Address definition .. List (DL) definition .. SUBMIT_MULTI_RESP deliveries .. DELIVER_SM Operation .. DELIVER_SM Syntax .. DELIVER_SM_RESP Syntax .. DATA_SM Operation .. DATA_SM Syntax .. DATA_SM_RESP Syntax .. QUERY_SM QUERY_SM Syntax .. QUERY_SM_RESP Syntax .. CANCEL_SM Operation .. CANCEL_SM Syntax.

7 CANCEL_SM_RESP REPLACE_SM REPLACE_SM Syntax .. REPLACE_SM_RESP Syntax .. ENQUIRE_LINK Operation .. ENQUIRE_LINK Syntax .. ENQUIRE_LINK_RESP Syntax .. ALERT_NOTIFICATION Operation .. ALERT_NOTIFICATION Syntax .. Parameter Command Header .. Command set .. SMPP Parameters .. 116 Page 6 of 169 SMPP Developers Forum Issue of ContentsSMPP Protocol Specification , source_addr_ton, dest_addr_ton, , source_addr_npi, dest_addr_npi, .. Optional Parameter Parameter Tag Optional Parameter Tag definitions .. 147 SMPP Protocol Specification Table of Contents Issue SMPP Developers Forum Page 7 of.

8 Error Codes .. Message Definitions .. Time Time Format .. Definitions .. 165 Appendix A .. 166 Appendix B .. 167 Appendix C .. 169 Page 8 of 169 SMPP Developers Forum Issue Protocol Specification OverviewThe Short Message peer to peer (SMPP) Protocol is an open, industry standard protocoldesigned to provide a flexible data communications interface for transfer of Short Message databetween a Message Center, such as a Short Message Service Centre (SMSC), GSMU nstructured Supplementary Services Data (USSD) Server or other type of Message Centerand a SMS application system, such as a WAP Proxy Server, EMail Gateway or otherMessaging.

9 For sake of brevity, the term SMSC will be used throughout this document to describeany SMPP server entity to which an SMPP client , termed an External ShortMessage Entity (ESME), can be Release supports Digital Cellular Network technologies including:- GSM IS-95 (CDMA) ANSI-136 (TDMA) iDENU sing the SMPP Protocol , an SMS application system called the External Short MessageEntity (ESME) may initiate an application layer connection with an SMSC over a TCP/IP network connection and may then send Short messages and receive Short messages to andfrom the SMSC respectively. The ESME may also query, cancel or replace Short messagesusing SMPP.

10 SMPP supports a full featured set of two-way messaging functions such as:- Transmit messages from an ESME to single or multiple destinations via the SMSC An ESME may receive messages via the SMSC from other SME s ( mobilestations). Query the status of a Short Message stored on the SMSC Cancel or replace a Short Message stored on the SMSC Send a registered Short Message (for which a delivery receipt will be returned by theSMSC to the Message originator) Schedule the Message delivery date and time Select the Message mode, datagram or store and forward Set the delivery priority of the Short Message Define the data coding type of the Short Message Set the Short Message validity period Associate a service type with each Message voice mail notificationSMPP Protocol Specification Introduction Issue SMPP Developers Forum Page 9 of document defines Version of the SMPP Protocol and specifies the command andresponse format to be used when implementing an SMPP Protocol interface.