Protocolo smpp

Solo disponible en BuenasTareas
  • Páginas : 131 (32655 palabras )
  • Descarga(s) : 4
  • Publicado : 21 de enero de 2010
Leer documento completo
Vista previa del texto
Short Message Peer to Peer Protocol Specification v3.4

Document Version:- 12-Oct-1999 Issue 1.2

Page 1 of 169

Issue 1.2

SMPP Protocol Specification v3.4

Short Message Peer to Peer Protocol Specification v3.4 12-Oct-1999 Issue 1.2

© 1999 SMPP Developers Forum.

COPYRIGHT All rights reserved. This document or any part thereof may not, without the prior written consent of SMPPDevelopers Forum, be copied, reprinted or reproduced in any material form including, 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 form or by any means, including but not limited to, electronic, mechanical, xerographic, optical, magnetic, digital or other methodology.DISCLAIMER WHILST THE GREATEST CARE HAS BEEN TAKEN TO ENSURE THE ACCURACY OF THE INFORMATION AND DATA CONTAINED HEREIN, SMPP DEVELOPERS FORUM DOES NOT SMPP WARRANT THE ACCURACY OR SUITABILITY OF SAME FOR ANY SPECIFIC USE. DEVELOPERS FORUM EXPRESSLY DISCLAIMS ALL AND ANY LIABILITY TO ANY PERSON, WHETHER A PURCHASER OR OTHERWISE, IN RESPECT OF ANY CONSEQUENCES OF ANYTHING DONE OR OMITTED TO BE DONEBY ANY SUCH PERSON IN PARTIAL OR TOTAL RELIANCE UPON THE WHOLE OR ANY PART OF THE CONTENTS OF THIS PUBLICATION OR ANY DERIVATIVE THEREOF. THE INFORMATION CONTAINED HEREIN IS BELIEVED TO BE ACCURATE AND RELIABLE. HOWEVER, SMPP DEVELOPERS FORUM ACCEPTS NO RESPONSIBILITY FOR IT’S USE BY ANY MEANS OR IN ANY WAY WHATSOEVER. SMPP DEVELOPERS FORUM SHALL NOT BE LIABLE FOR ANY EXPENSES, COSTS OR DAMAGE THATMAY RESULT FROM THE USE OF THE INFORMATION CONTAINED HOWSOEVER ARISING IN THIS DOCUMENT OR ANY DERIVATIVE THEREOF.

NOTE 1:THE INFORMATION CONTAINED IN THE WITHIN DOCUMENT AND ANY DERIVATIVE THEREOF IS SUBJECT TO CHANGE WITHOUT NOTICE.

NOTE 2:THE CORPORATE NAME OF SMPP DEVELOPERS FORUM IS NORTHGROVE LIMITED, COMPANY NUMBER 309113, REGISTERED OFFICE GARDNER HOUSE, WILTON PLACE, DUBLIN 2.Page 2 of 169

©SMPP Developers Forum

Issue 1.2

SMPP Protocol Specification v3.4

Errata

Errata
Change Request Reference
SMPPV3.405Oct99-01

Erratum In the SMPP Protocol Specification v3.4. version 30-July-1999 Issue 1.1 section 4.1.5 “Bind_Transceiver” the interface_version field was inadvertently not included in the bind_transceiver PDU.

Description of Correction to addressErratum The erratum was corrected in the SMPP Protocol Specification v3.4 version 12-Oct-1999 Issue 1.2 as follows: In section 4.1.5 “Bind_Transceiver” the interface_version field was added as a mandatory field to the bind_transceiver PDU. Since it is a mandatory field all implementations of the SMPP Protocol Specification v3.4 must include the interface_version field when using thebind_transceiver PDU.

Issue 1.2

©SMPP Developers Forum

Page 3 of 169

Table of Contents

SMPP Protocol Specification v3.4

Table of Contents
1. Introduction ................................................................................................................. 8 1.1 SMPP Overview............................................................................................... 8 1.2Scope................................................................................................................ 9 1.3 Glossary ......................................................................................................... 10 1.4 References...................................................................................................... 11 SMPP Protocol Overview......................................................................................... 12 2.1 SMPP Protocol Definition ............................................................................. 13 2.2 SMPP Session Description ............................................................................ 14 2.2.1 Outbind ......................................................................................... 16...
tracking img