SMPP connectivity
SMPP Account & Enterprise SMS Connectivity
Enterprise SMPP v3.4 connectivity for business SMS
Connect your messaging applications with TXTPro's SMPP v3.4 service. Choose Transceiver (TRX) or separate Transmitter (TX) and Receiver (RX) binds, with variable TPS configurations and IP-whitelisted connectivity.
SMPP v3.4 bind options
Illustrative example- TRXTransceiverSubmit SMS and receive receipts on one session
- TXTransmitterOutbound submit_sm
- RXReceiverDelivery receipts via deliver_sm
What is SMPP?
SMPP, the Short Message Peer-to-Peer protocol, is the open industry protocol that SMS applications use to exchange messages with an SMS gateway or Short Message Service Centre (SMSC). An SMPP account gives your application a system ID, a password and connection details so it can connect to that gateway directly.
Unlike an HTTP API, where each message is a separate web request, SMPP runs over a persistent TCP connection. Your client opens the connection, authenticates with a bind request and keeps the resulting SMPP session open. It sends each SMS as a submit_sm request and receives the gateway’s submit_sm_resp with a message ID. When a delivery receipt is requested, the result comes back on the session as a deliver_sm request, which your client acknowledges.
SMPP is common in SMS gateway software, aggregator platforms, CPaaS products and enterprise systems that send continuous volumes of OTPs, alerts and notifications, many of which ship with a built-in SMPP client.
Confirmed capabilities
Why TXTPro SMPP?
These capabilities are confirmed for TXTPro SMPP accounts. Connection details and account-specific parameters are agreed during onboarding.
SMPP v3.4
Connect any SMPP v3.4-compliant client, SMS gateway or messaging platform.
Transceiver (TRX) bind
One session that submits SMS and receives delivery receipts.
Transmitter (TX) bind
A session dedicated to submitting outbound SMS.
Receiver (RX) bind
A session dedicated to receiving delivery receipts.
Separate TX + RX
Run submission and delivery receipts on separate sessions when your platform prefers it.
Variable TPS
Throughput is configured per account, based on your requirements and service plan.
IP-whitelisted access
Connections are accepted only from the public IP addresses registered for your account.
SMS delivery receipt integration
Receive delivery receipts as deliver_sm on a TRX or RX session, subject to routing and receipt configuration.
Bind types
Flexible SMPP bind options
Choose a single transceiver session, or separate transmitter and receiver sessions.
| Bind type | SMS submission | DLR reception |
|---|---|---|
| TRX — Transceiver | Yes | Yes |
| TX — Transmitter | Yes | No |
| RX — Receiver | No | Yes |
| Separate TX + RX | Through TX | Through RX |
TRX connection
One transceiver session supports SMS submission and receiving delivery receipts. It is the simplest setup: a single connection to monitor, with submit_sm going out and deliver_sm coming back on the same session.
Separate TX/RX connections
A transmitter session handles outbound SMS submission, while a receiver session handles incoming delivery receipts. Platforms that scale submission and receipt processing independently, or that were built before transceiver binds existed, often prefer this split.
Protocol
SMPP v3.4 features
| Concept | What it does |
|---|---|
bind_transceiver | Opens a session that can both submit messages and receive deliver_sm (TRX). Introduced in v3.4. |
bind_transmitter | Opens a submit-only session (TX). |
bind_receiver | Opens a session that only receives deliver_sm, such as delivery receipts (RX). |
submit_sm | Submits one short message: source and destination addresses, data coding, registered_delivery and the message body. |
submit_sm_resp | The SMSC’s answer to submit_sm. A command_status of 0 means accepted, and the message_id identifies the message for later receipts. |
deliver_sm | Sent by the SMSC to your client: delivery receipts (with the receipt flag set in esm_class) or inbound messages. |
deliver_sm_resp | Your acknowledgement of each deliver_sm. Without it, the SMSC may resend the receipt. |
enquire_link | A keepalive that either side can send to confirm the session is still alive; the peer answers with enquire_link_resp. |
unbind | Ends the session cleanly before the TCP connection is closed; answered with unbind_resp. |
| Sequence number | A number your client assigns to every request; the response carries the same number so requests and responses can be matched. |
| Message ID | Assigned by the SMSC in submit_sm_resp and referenced again in the delivery receipt. |
registered_delivery | Requests a delivery receipt: 0 = none, 1 = on final success or failure, 2 = on failure only. |
| TON / NPI | Type of Number and Numbering Plan Indicator for each address, for example international (TON 1) with E.164 (NPI 1), or alphanumeric (TON 5) for sender headers. |
data_coding | How the body is encoded: 0 = SMSC default alphabet, 3 = Latin-1, 8 = UCS-2 (used for Unicode, including Indian scripts). |
| Unicode SMS | UCS-2 text fits 70 characters in a single SMS, compared with 160 GSM 7-bit characters. |
| Multipart SMS | Long messages are split into segments joined with a User Data Header (UDH) or SAR parameters, or sent in message_payload where supported. |
Message encoding matters for cost and readability. Text in the GSM 7-bit alphabet fits 160 characters in one SMS; Unicode text such as Hindi, Telugu or Tamil uses UCS-2 and fits 70. Longer messages are split into segments of 153 (GSM) or 67 (UCS-2) characters, each counted as an SMS. The SMPP integration guide explains each operation with code examples.
Throughput
Flexible SMPP throughput configuration
TPS (transactions per second) is the rate at which your client may submit submit_sm requests. TXTPro provides variable SMPP throughput configurations based on customer requirements and applicable service plans. Contact our team to discuss your expected sending volume and TPS needs.
- Submission rate. TPS limits how quickly messages leave your queue: the time to submit a campaign is roughly the number of messages divided by your permitted TPS.
- Plans and configuration. The rate for your account depends on your requirements and service plan, and it is configured during onboarding.
- Rate control in your client. Pace submissions below the configured rate with a token bucket or fixed interval, and spread the load across binds only as agreed for your account.
- Throttling. If submissions exceed the permitted rate, the gateway can reject them; SMPP v3.4 defines
ESME_RTHROTTLED(0x58) for this. Back off, then retry the rejected message. How throttling is signalled for your account is confirmed during onboarding. - Throughput is not delivery speed. TPS describes acceptance of submissions. Final delivery time depends on operators, handset availability and network conditions.
Access control
IP-whitelisted connectivity
TXTPro accepts SMPP connections only from the public IP addresses registered for your account. Your servers, or the NAT gateway in front of them, must use a fixed public IP address; connections from any other address are refused before a bind can succeed.
Proposed onboarding workflow
A proposed operational workflow for new SMPP accounts. The final steps are aligned with TXTPro’s onboarding process for your account.
- 01
Request an SMPP account
Share your use case, preferred bind type, monthly volume and expected TPS.
- 02
Requirement review
TXTPro reviews your integration requirements and the applicable DLT setup for your SMS traffic.
- 03
Share source IPs
You provide the public source IP address or addresses your SMPP client will connect from.
- 04
IP access configured
TXTPro configures permitted IP access for your account.
- 05
Connection details shared
Connection details are shared securely through an approved channel, never on public pages.
- 06
Connection and submission test
You bind, run test submissions and confirm submit_sm responses.
- 07
Delivery receipt validation
You confirm that delivery receipts arrive and are matched to your messages.
Illustrative
SMPP connectivity flow
How a message travels from your application to the recipient, and how its delivery receipt returns on your SMPP session.
Message path
Customer application
Your platform creates the message.
SMPP v3.4 client
Binds and sends submit_sm.
TXTPro SMPP connection
IP-whitelisted session.
Messaging infrastructure
Routes the message onward.
Mobile network
Delivers to the handset.
Recipient
Receives the SMS.
Delivery receipt return path
Mobile network → messaging infrastructure → TXTPro SMPP connection → deliver_sm on your TRX or RX session → your client sends deliver_sm_resp and updates the message status.
Use cases
SMPP use cases
SMPP suits platforms that already speak the protocol or send continuous volumes. Delivery timing and operator acceptance are never guaranteed.
High-volume business SMS
Platforms that submit large volumes continuously benefit from persistent sessions and pipelined submissions.
OTP messaging
Submit one-time passwords from authentication systems on DLT-registered transactional or service templates.
Transactional notifications
Order, payment, banking and account alerts generated by core systems.
Promotional campaigns
Campaign engines that submit approved promotional templates, subject to customer preferences, consent and applicable rules.
CRM and ERP integration
Enterprise systems with built-in SMPP connectors can submit messages and store delivery receipts.
SMS gateway applications
Gateway software, aggregator platforms and SMS routers that speak SMPP natively.
Enterprise communication platforms
CPaaS, contact-centre and notification platforms that manage SMPP connections for several applications.
SMS DLT compliance for SMPP traffic
SMPP account access does not remove applicable Indian SMS DLT obligations. Every SMS submitted over SMPP is commercial SMS like any other and must meet the same rules:
- Principal Entity registration on an operator DLT platform applies where required for SMS.
- Registered headers (sender IDs) must be used as the source address.
- Approved SMS templates must match the content you submit, and the applicable operator rules on categories and consent apply.
- How DLT entity and template identifiers are passed with SMPP submissions for your account is confirmed during onboarding.
SMPP connectivity is separate from RCS bot onboarding. RCS bot registration is separate from SMS DLT registration. A DLT registration or PE ID is not required for TXTPro's RCS bot onboarding. RCS onboarding follows its own business verification and agent launch process. See the RCS registration guide.
For SMS setup, read the DLT registration guide and the Bulk SMS service page.
FAQs
SMPP FAQs
Can’t find your answer? Contact our team.
What is an SMPP account?
An SMPP account is a set of credentials (a system ID and password) and connection details that let your SMS application connect to a provider’s SMS gateway over the Short Message Peer-to-Peer protocol. Your client opens a persistent session, submits messages and receives delivery receipts on it.
Does TXTPro support SMPP v3.4?
Yes. TXTPro provides SMPP v3.4 connectivity, so any SMPP v3.4-compliant client, gateway or messaging platform can connect.
Does TXTPro provide TRX connections?
Yes. A transceiver (TRX) bind is supported: a single session submits SMS and receives delivery receipts.
Can I use separate TX and RX sessions?
Yes. You can bind a transmitter (TX) session for submission and a receiver (RX) session for delivery receipts, instead of a single TRX session.
What TPS does TXTPro provide?
Throughput is variable and configured per account, based on your requirements and service plan. TXTPro does not publish fixed TPS figures; share your expected volume and peak TPS when you request an account.
Is IP whitelisting required?
Yes. TXTPro SMPP connections are accepted only from the public IP addresses registered for your account. IP whitelisting is an access control and does not encrypt traffic.
What is an SMPP bind?
A bind is the first request on a new SMPP connection. Your client authenticates with its system ID and password and chooses the session type: bind_transmitter (TX), bind_receiver (RX) or bind_transceiver (TRX).
How are SMPP delivery receipts received?
When you request a receipt with registered_delivery, the SMSC sends it as a deliver_sm PDU on your TRX or RX session, and your client acknowledges it with deliver_sm_resp. SMPP receipts arrive over the SMPP session, not as HTTP webhooks. Receiving them also depends on message routing and receipt configuration.
Is DLT registration required for SMPP SMS traffic in India?
Yes, where applicable. SMPP is only a connection protocol: SMS sent over SMPP is subject to the same DLT requirements as any other SMS, including Principal Entity registration, registered headers and approved templates.
What is the difference between SMPP and HTTP SMS API?
SMPP keeps a persistent, stateful session open for submission and delivery receipts. An HTTP SMS API sends each message as a separate request, with delivery reports usually delivered by webhook or retrieved by polling. Neither is automatically faster or cheaper; the right choice depends on your platform.
Can SMPP be integrated with an existing SMS platform?
Usually, yes. Most SMS gateways, aggregator platforms and CPaaS products include SMPP v3.4 client connectors. You configure the connection details, bind type and IP whitelisting, then test submission and receipts.
How can I request an SMPP account?
Use the Request SMPP Account form on this page. Share your use case, monthly volume, expected TPS and preferred bind type; the TXTPro team will review the requirement and explain the onboarding steps.
Need an SMPP account for your business?
Discuss your integration requirements, preferred bind type, sending volume and TPS needs with TXTPro.
Prefer to call? +91 90304 02858 · Email info@txtpro.in
