SMPP Global SMS
The following show examples of bind request and response messages with Automated Originator Selector and without. See Initiate a bind request to register a connection for more information about the parameters.
Note: The Command Length and Message Length fields shown here are for display purposes only. The lengths of these fields are determined when the request message is generated.
bind_transmitter
In this example, the following parameters are used to create an encoded file for a bind_transmitter request an SMPP system type.
Example bind PDU parameters
|
Parameter |
Value |
Description |
|---|---|---|
PDU Header:
|
||
Command Length |
57 octets |
|
Command ID |
0x02 |
BIND |
Command Status |
0x00 |
|
Sequence Number |
357911 |
|
PDU Body:
|
||
System ID |
12345678912345 |
|
Password |
@13bkIlM4W&* |
|
System Type |
SMPP |
|
Interface Version |
34 |
|
Address TON |
0x00 |
|
Address NPI |
0x00 |
|
Address Range |
0x00 |
|
A successful bind request returns an encoded response based on the type of bind request containing the following information. A Command Status of 2 indicates that the bind transmitter connection was successfully initiated and registered.
Example bind_resp PDU parameters
|
Parameter |
Value |
Description |
|---|---|---|
PDU Header:
|
||
Command Length |
31 octets |
|
Command ID |
0x80000002 |
BIND_RESP |
Command Status |
0x00 |
No Error |
Sequence Number |
357911 |
|
System ID |
12345678912345 |
|