API / Docs

API

Auf der Suche nach weiteren Informationen zur Anbindung an unsere Plattform und zur Anwendung unserer Services? Die aktuellsten Versionen unserer API Spezifikationen finden Sie hier:

REST-API Dokumentation
Mobile Message Account
REMOTE365 Web Service

SMPP API Quick Start

Starten Sie mit dem Quick Guide für SMPP und versenden in nur wenigen Minuten SMS über unser Messaging Gateway.

Supported SMPP Version

Unser Messaging Gateway unterstützt SMPP Version 3.4. Den Zugriff auf die offizielle Spezifikation finden Sie hier:

SMPP Version 3.4
Connection Type

Die Verbindung wird über TCP/IP und SSL hergestellt. Es ist erforderlich, dass die IP-Adresse des Benutzers in unserer Firewall aktiviert ist.

Base URL

smpp.secure.api.whatevermobile.com:4002

Wenn die Verbindung unterbrochen wird, warten Sie bitte 30 Sekunden, bevor Sie versuchen, die Verbindung wiederherzustellen. Die Verbindung wird nach 5 Minuten Inaktivität automatisch geschlossen. Um eine Schließung der Verbindung zu vermeiden, müssen “ENQUIRE_LINK” Operationen als "PING" gesendet werden..

Timezone of the Gateway

UTC

Standard Charset

GSM 7bit

Standard Throughput

5 SMS/sec

Standard Connections

1

Window Size Out

1

Window Size In

1

Authentication
Parameter
Description

Login:

required, use field “system_id” within your bind request

Password:

required, use field “password” within bind request

Supported Operation Types

BIND
UNBIND
GENERIC_NACK
SUBMIT_SM
DELIVER_SM
ENQUIRE_LINK

Originator Type of Number (TON)

0=unknown
1=international
2=national
3=shortcode
5=alphanumeric

TON is automatically detected if 0 is submitted.

Delivery Receipts

SMPP bietet die Möglichkeit, Lieferbenachrichtigungen über die PDU deliver_sm anzufordern. In der Lieferavis steht der Lieferstatus der Nachricht, welche die Benachrichtigung angefordert hat. Die Statusinformationen sind in der Kurznachricht angegeben.

Parameter der Operation deliver_sm: Je nachdem, wie ein Messaging-Konto konfiguriert wurde, können Lieferbenachrichtigungen unterschiedlich formatiert sein.

The default formatting is as follows:

id:I sub:S dlvrd:D submit date:YYMMDDhhmmss done date:YYMMDDhhmmss stat:D err:E text:

An alternative formatting omits the seconds in both the submit date and the done date:

id:I sub:S dlvrd:D submit date:YYMMDDhhmm done date:YYMMDDhhmm stat:D err:E text:

Delivery Receipts Message State
Message State
Stat-Field-Value
Description

DELIVERED

DELIVRD

Message is delivered to destination.

EXPIRED

EXPIRED

Message validity period has
expired.

DELETED

DELETED

Message has been deleted.

ACCEPTED

ACCEPTD

Message is in accepted state (i.e.
has been manually read on behalf
of the subscriber by customer
service).

UNKNOWN

UNKNOWN

Message is in invalid state.

REJECTED

REJECTD

Message is in a rejected state.

Response Codes
Code
Error Message

0

OK

1

Service temporary not available

9

Illegal error code

10

Network timeout

11

No further information available

100

Facility not supported

101

Unknown subscriber

102

Facility not provided

103

Call barred

104

Operation barred

105

SC congestion

107

Absent subscriber

108

Delivery fail

110

Protocol error

111

MS not equipped

112

Unknown SC

114

Illegal MS

115

MS not a subscriber

116

Error in MS

117

SMS lower layer not provisioned

118

System fail

119

PLMN system failure

120

HLR system failure

121

VLR system failure

122

Previous VLR system failure

123

Controlling MSC system failure

124

VMSC system failure

125

EIR system failure

126

System failure

127

Unexpected data value

128

Insufficient credit in a prepaid case

129

Number is blacklisted

200

Error in address service center

201

Invalid absolute validity period

202

Short Message exceeds maximum

203

Unable to unpack GSM message

204

Unable to convert to IA5 ALPHABET

205

Invalid validity period format

206

Invalid destination address

207

Duplicate message submit

208

Invalid message type indicator

220

Message validity period has expired

221

Message has been deleted

222

Message is undeliverable

223

Message is in accepted state

224

Message state is unknown

225

SMS was rejected

226

Message buffered

230

Billing ok

231

Timeout while delivering content

232

MS not enabled for billing

233

Billing Transaction unknown

234

Billing Transaction timeouted

235

Operator can not process billing

236

Configuration problem

237

Billing mode not allowed

238

Missing parameters

239

IMSI not checked: unknown operator

240

IMSI not checked: system error

241

IMSI not checked: first request

242

IMSI changed: SIM or provider changed

243

IMSI changed: SIM, APD or provider changed

244

IMSI changed: network changed

245

IMSI changed: single to multi SIM

246

IMSI not changed

247

IMSI not changed: multiSIM, possible APDC

248

IMSI not changed: APD change possible

249

IMSI not checked: call forward active

250

IMSI not checked: not requested

252

Message encoding wrong

253

Billing_transaction_id not found

254

Internal server error

255

Unknown error

901

Checksum error

902

Syntax error

903

Operation not supported by system

904

Operation not allowed

905

Call barring active

906

AdC invalid

907

Authentication failure

908

Legitimization code fails for call

909

GA not valid

910

Repetition not allowed

911

Legit. code fails for repetition

912

Priority call not allowed

913

Legit. code fails for priority cal

914

Urgent message not allowed

915

Legit. code fails for urgent message

916

Reverse charging not allowed

917

Legit. code fails for rev. charging

918

Deferred delivery not allowed

919

New AC not valid

920

New legitimization code not valid

921

Standard text not valid

922

Time period not valid

923

Message type not supported by system

924

Message length invalid

925

Requested standard text not valid

926

Invalid Message type for pager type

927

Message not found in SMSC

930

Subscriber hang-up

931

Fax group not supported

932

Fax message type not supported

933

Address already in list (60 series)

934

Address not in list (60 series)

935

List full, cannot add address

936

RPID already in use

937

Delivery in progress

938

Message forwarded

939

Invalid source address

940

Replace SM failed

941

Invalid esm_class field data

942

submit_sm or submit_multi failed

943

Invalid source address TON

944

Invalid source address NPI

945

Invalid destination address TON

946

Invalid destination address NPI

947

Invalid schedule delivery time

948

Invalid message validity period

949

Exceeded allowed message limit

998

Timeout on waiting for concat parts

999

Internal billing not successful

Code Snippets

Erfahre, wie man eine SMS via HTTP an unser Messaging Gateway übermittelt.