Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword or section
Like this
28Activity

Table Of Contents

0 of .
Results for:
No results containing your search query
P. 1
Short Message Peer to Peer Protocol Specification v3.4

Short Message Peer to Peer Protocol Specification v3.4

Ratings:

5.0

(1)
|Views: 5,884 |Likes:
Published by Sharon Gilmore

More info:

Published by: Sharon Gilmore on Dec 15, 2009
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

06/26/2013

pdf

text

original

 
Page 1 of 169 Issue 1.2
Short Message Peer to PeerProtocol Specification v3.4
Document Version:- 12-Oct-1999 Issue 1.2
 
Page 2 of 169
©SMPP Developers Forum Issue 1.2
SMPP Protocol Specification v3.4
 
Short Message Peer to Peer Protocol Specification v3.412-Oct-1999 Issue 1.2
©
1999 SMPP Developers Forum.
COPYRIGHT
All 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 methodology.
DISCLAIMER
W
HILST
 
THE
 
GREATEST
 
CARE
 
HAS
 
BEEN
 
TAKEN
 
TO
 
ENSURE
 
THE
 
ACCURACY
 
OF
 
THEINFORMATION
 
AND
 
DATA
 
CONTAINED
 
HEREIN
, SMPP D
EVELOPERS
F
ORUM
 
DOES
 
NOTWARRANT
 
THE
 
ACCURACY
 
OR
 
SUITABILITY
 
OF
 
SAME
 
FOR
 
ANY
 
SPECIFIC
 
USE
. SMPPD
EVELOPERS
F
ORUM
 
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
 
DERIVATIVETHEREOF
.T
HE
 
INFORMATION
 
CONTAINED
 
HEREIN
 
IS
 
BELIEVED
 
TO
 
BE
 
ACCURATE
 
AND
 
RELIABLE
.H
OWEVER
, SMPP D
EVELOPERS
F
ORUM
 
ACCEPTS
 
NO
 
RESPONSIBILITY
 
FOR
 
IT
S
 
USE
 
BY
 
ANYMEANS
 
OR
 
IN
 
ANY
 
WAY
 
WHATSOEVER
. SMPP D
EVELOPERS
F
ORUM
 
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
 
THEREOF
.NOTE 1:THE INFORMATION CONTAINED IN THE WITHIN DOCUMENT AND ANYDERIVATIVE THEREOF IS SUBJECT TO CHANGE WITHOUT NOTICE.NOTE 2:THE CORPORATE NAME OF SMPP DEVELOPERS FORUM IS NORTHGROVELIMITED, COMPANY NUMBER 309113, REGISTERED OFFICE GARDNER HOUSE,WILTON PLACE, DUBLIN 2.
 
SMPP Protocol Specification v3.4
ErrataIssue 1.2
©SMPP Developers Forum Page 3 of 169
Errata
ErratumDescription of Correction toaddress ErratumChangeRequestReference
In the SMPP Protocol Specificationv3.4. version 30-July-1999 Issue 1.1s
ection 4.1.5 “Bind_Transceiver”the
interface_version
field
 
wasinadvertently not included in the
 bind_transceiver
PDU.The erratum was corrected in theSMPP Protocol Specification v3.4version 12-Oct-1999 Issue 1.2 asfollows:In section 4.1.5 “Bind_Transceiver”the
interface_version
field
 
wasadded as a
mandatory
field to the
 bind_transceiver
PDU.Since it is a mandatory field allimplementations of the SMPPProtocol Specification v3.4
must
include the
interface_version
field
 
when using
 
the
 
 bind_transceiver
PDU.
SMPPV3.4-05Oct99-01

Activity (28)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
nenadstefanovic liked this
Volodymyr Sapiha liked this
Anna Trossing liked this
elbio5151 liked this
Anna Trossing liked this
Mehta S.D. liked this
Mehta S.D. liked this

You're Reading a Free Preview

Download
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->