eSMSAfrica
SMPP 3.4 · smpp.esmsafrica.io

Persistent binds.
Carrier routes.
Africa-wide.

IP-allowlisted binds, throughput set per account, and operator DLR pass-through - on the same routes that power our REST API. One host, three bind modes.

2775
Standard port
3.4
SMPP spec
3
Bind modes
100
Typical msg/s
smpp.esmsafrica.io : 2775 · IP allowlist
← TCP connected from an allowlisted IP

→ bind_transceiver
     system_id           = "your_system_id"
     password            = "••••••••"
     interface_version   = 0x34
← bind_transceiver_resp
     command_status      = 0x00000000  ESME_ROK
     system_id           = "ESMSAFRICA"

→ submit_sm
     source_addr         = "eSMSCo"
     destination_addr    = "+254712345678"
     data_coding         = 0x00 GSM-7
     registered_delivery = 0x01 request DLR
     short_message       = "Your OTP is 482910. Valid 5 min."
← submit_sm_resp
     command_status      = 0x00000000  ESME_ROK
     message_id          = "8A2F91C4"

── 4.2 s later ─────────────────────────────
← deliver_sm  DLR from operator SMSC
     short_message = "id:8A2F91C4 sub:001 dlvrd:001
                      submit date:2605030812
                      done date:2605030812
                      stat:DELIVRD err:000"
→ deliver_sm_resp
     command_status      = 0x00000000  ESME_ROK

→ enquire_link    keepalive every 30 s
← enquire_link_resp
bind_transceiver active · keepalive running
Connection

One host. Three bind modes.

Point your SMPP client at smpp.esmsafrica.io:2775. Connections are accepted only from the IP addresses on your bind's allowlist.

Connection parameters
Host smpp.esmsafrica.io
Port 2775 (plain TCP, IP allowlist)
Protocol version SMPP 3.4 (interface_version = 0x34)
Transport TCP (no TLS on the SMPP port)
Bind timeout 30 seconds
Keepalive enquire_link every 30 s
Throughput Set per bind, typically 100 msgs / s
Higher throughput On request, subject to route capacity
Over the limit submit_sm_resp ESME_RTHROTTLED (0x58)
RECOMMENDED
bind_trx

Send and receive on a single bind. Handles both submit_sm and deliver_sm - the right choice for most integrations.

bind_tx

Submit messages only. Use when you want to isolate outbound sending from inbound DLR reception.

bind_rx

Receive inbound messages and DLRs only. Pair with a TX bind for split-architecture deployments.

Capabilities

Built to spec.

Standard SMPP 3.4

Transceiver, transmitter and receiver binds, submit_sm, deliver_sm, enquire_link and unbind, with optional TLVs. Works with any SMPP 3.4 client library.

IP-allowlisted binds

Port 2775 is closed to the internet. It accepts connections only from the IP addresses on your bind's allowlist. TLS is not offered on the SMPP port; the HTTP API uses HTTPS (TLS 1.2 or 1.3).

Throughput set per bind

Each system_id has its own limit, typically 100 messages per second. Higher limits are available on request, subject to route capacity.

Long SMS, Unicode, Binary

UDH concatenation for multi-part messages. UCS-2 for Unicode (data_coding=8): 70 characters per single SMS, 67 per part. Binary payloads use data_coding=4.

End-to-end DLR pass-through

Operator delivery receipts arrive verbatim via deliver_sm. Error codes and timestamps from the carrier SMSC are preserved.

Route failover

If a destination route degrades, traffic can fail over to a backup route. enquire_link keeps idle binds alive; your client should rebind with back-off if the connection drops.

Supported PDU types

  • bind_transceiver / bind_transmitter / bind_receiver (+ _resp)
  • submit_sm / submit_sm_resp
  • deliver_sm / deliver_sm_resp
  • enquire_link / enquire_link_resp
  • unbind / unbind_resp
  • generic_nack

Supported encodings

0x00
GSM-7
160 chars / segment - default for Latin script
0x03
Latin-1 (ISO-8859-1)
140 chars / segment - 8-bit Western European
0x08
UCS-2 (UTF-16)
70 chars / segment - Unicode, Arabic, Amharic, CJK
0x04
Binary (8-bit)
140 bytes / segment - binary payloads
Architecture

How your message travels.

Every bind lands on our routing infrastructure, passes through licensed carrier routes, and delivers to the handset. No grey routes, no SIM farms.

Your SMPP client
smpplib · node-smpp · go-smpp · java-smpp
smpp.esmsafrica.io:2775
IP allowlist · SMPP 3.4
eSMS routing layer
Routing · throughput · DLRs
Operator SMSC
Operator routes across Africa

← DLR returns the same path: operator deliver_sm → eSMS routing layer → your bind → deliver_sm PDU

Client examples

Connect in any language.

Any SMPP 3.4 client library works. These snippets use the most popular open-source clients - swap in your credentials.

python node.js go
# pip install smpplib
import smpplib.client, smpplib.gsm, smpplib.consts

# Connect from an IP on your bind's allowlist

client = smpplib.client.Client(
    'smpp.esmsafrica.io', 2775,
    allow_unknown_opt_params=True,
    timeout=30,
)
client.connect()
client.bind_transceiver(
    system_id='YOUR_SYSTEM_ID',
    password='YOUR_PASSWORD',
)

# Register DLR handler (deliver_sm callbacks)
def dlr_received(pdu):
    msg = pdu.short_message
    if isinstance(msg, bytes):
        msg = msg.decode('latin-1')
    print(f"DLR: {msg}")

client.set_message_received_handler(dlr_received)

# Send a message (GSM-7, with DLR)
parts, enc, msg_type = smpplib.gsm.make_parts('Your OTP is 482910')
for part in parts:
    resp = client.send_message(
        source_addr_ton=smpplib.consts.SMPP_TON_ALNUM,
        source_addr_npi=smpplib.consts.SMPP_NPI_UNK,
        source_addr='eSMSCo',
        dest_addr_ton=smpplib.consts.SMPP_TON_INTL,
        dest_addr_npi=smpplib.consts.SMPP_NPI_ISDN,
        destination_addr='+254712345678',
        data_coding=enc,
        esm_class=msg_type,
        short_message=part,
        registered_delivery=1,
    )
    print(f"Queued: {resp.message_id}")

# Block and process inbound PDUs
client.listen()

Python and Java bind examples in the SMPP credentials guide →

FAQ

Common questions

Get started

Ready to go direct?

We provision bind credentials and validate the connection on a test SMSC before you go live.