Quick Answer
SMPP connectivity is a persistent Short Message Peer-to-Peer (v3.4) link between your messaging platform and an SMS gateway, used by banks, fintech, large platforms and SMS resellers for high-volume A2P traffic. In India every submit_sm must carry DLT data such as the principal entity ID and template ID. SMSGatewayHub provides SMPP v3.4 binds with configurable throughput per session, real-time delivery receipts, a 99.9% uptime SLA and free integration support.
SMPP connectivity vs SMPP API vs HTTP API: what is the difference?
All three send the same DLT-registered SMS from one SMSGatewayHub account. This page covers enterprise and reseller SMPP connectivity: binds, throughput, DLT parameters and failover.
| Option | What it is | Who it is for | Throughput & receipts |
|---|
| SMPP connectivity (this page) | Dedicated enterprise SMPP v3.4 binds with throughput agreed per session, DLT TLVs and failover planning | Banks, fintech, telecom and ISP platforms, large aggregators sending lakhs of SMS a month | 10,000+ SMS per minute; DLRs pushed back as deliver_sm on the bind |
| SMPP API | Standard SMPP account for resellers and high-volume senders, with SOP and reseller documentation | Resellers and wholesale partners starting on SMPP | Persistent session; DLRs on the same session |
| HTTP / HTTPS API | Stateless request per call from any language | Websites, apps and CRMs with moderate volume | Up to about 1,000 SMS per minute; reports, API pulls or webhooks |
Not sure which fits? Start on the developer API and move to SMPP as volume grows; your DLT headers and templates stay the same.
What changed for SMPP traffic under the latest DLT rules?
DLT scrubbing happens at the operator, so the data you put in each submit_sm decides whether a message is delivered or rejected.
Entity and template ID on every message
Each submit_sm must carry your DLT principal entity (PE) ID and the content template ID, usually as optional TLV parameters, so the operator can match the text to an approved template.
PE-TM chain binding
Your traffic must follow the PE-to-telemarketer chain declared on DLT, and an SMPP hash value representing that chain is now passed with each message. Unmatched traffic is blocked. See PE-TM chain binding.
Typed template variables
Templates now tag values as {#numeric#}, {#alphanumeric#}, {#url#}, {#cbn#} and similar, so the short_message you submit must match the typed template exactly. See sample templates.
Header suffixes
Operators append -T, -S, -P or -G to the header you send in source_addr, so register each template in the right category. See sender ID and suffixes.
Why SMSGatewayHub
Why choose SMSGatewayHub over other SMPP providers?
An SMPP link is only as good as its uptime, its DLT handling and the team behind it. Here is what you get.
Persistent, high-throughput binds
Bind once and submit continuously, with no re-authentication per message and configurable throughput limits per SMPP session.
Multi-operator routing with failover
Traffic is routed across operators with automatic failover, for 2-6 second typical delivery and a 99.9% uptime SLA.
DLT handled with you
Our team helps map PE IDs, template IDs and chain details and fixes rejections fast. DLT priority support
Certified security
ISO 27001, ISO 9001:2015, SOC 2 and VAPT tested, with IP whitelisting on binds. Trust Center
Free integration support
Engineers help you connect from Java, Python, PHP, .NET or C++ clients, and our 24/7 team is a toll-free call away on 1800 102 1822.
| Question to ask any SMPP provider | SMSGatewayHub |
|---|
| Which SMPP version and operations do you support? | SMPP v3.4 with bind_transceiver, submit_sm, deliver_sm and enquire_link. |
| Can throughput be set per session? | Yes, throughput limits are configurable per SMPP session. |
| Do delivery receipts come back on the bind? | Yes, real-time DLRs are returned as deliver_sm. Live delivery reports |
| How do I pass DLT entity and template IDs? | As TLV parameters on submit_sm; exact tags are in your onboarding document. |
| What happens if an operator route degrades? | Traffic automatically fails over to another operator route. |
| Am I charged for undelivered messages? | No. You pay only for delivered SMS. |
Resellers should read why SMS resellers fail TLV 1402 compliance and why resellers trust SMSGatewayHub.
SMPP connectivity use cases by industry
Each card links to a dedicated industry page with message samples and DLT tips.
E-commerce mass SMS
Flash sale and order alerts to millions of customers without HTTP request overhead. Bulk SMS for e-commerce
Healthcare OTP systems
Hospital systems sending patient portal OTPs and reminders at volume without API queue delays. Bulk SMS for hospitals
Logistics platforms
Shipment, delivery OTP and dispatch alerts streamed from TMS and courier platforms. Bulk SMS for logistics
Aggregators, telecom & ISPs
Resellers, wholesale aggregators and ISPs use SMPP for A2P routing with full PDU control. Bulk SMS reseller programme
SMPP v3.4 operations used on an SMSGatewayHub bind
The core protocol data units (PDUs) your SMPP client exchanges with our server.
| PDU | Direction | What it does |
|---|
| bind_transceiver | Client to server | Opens one session that can both send messages and receive delivery receipts (the recommended mode). |
| bind_transmitter / bind_receiver | Client to server | Alternative pair of sessions: one for sending only, one for receiving only. |
| submit_sm / submit_sm_resp | Client to server, then response | Submits one message with header, number, text and DLT TLVs; the response returns the message ID used to match the receipt. |
| deliver_sm / deliver_sm_resp | Server to client, then response | Delivers the delivery receipt (DLR) for a submitted message; your client must acknowledge it. |
| enquire_link / enquire_link_resp | Either side | Keep-alive that confirms the session is healthy so idle binds are not dropped. |
| unbind / unbind_resp | Either side | Closes the session cleanly before disconnecting. |
Send in Hindi and other scripts with UCS2 encoding; see Unicode and regional language SMS.
How to get SMPP connectivity
Create an account
Register free and tell our team your expected volume and use case.
Complete DLT
Register as a principal entity, headers and templates, and set up your PE-TM chain. We guide you through DLT registration.
Receive credentials
We share host, port, system_id and password, and whitelist your server IPs. How IP whitelisting works
Bind and test
Bind with any SMPP v3.4 client library, send test messages with your DLT TLVs and confirm receipts arrive as deliver_sm.
Go live and monitor
Scale to your agreed throughput and watch live delivery reports; fix rejections with the DLT error codes guide.
SMPP connection parameters
What you receive from us and what you set on your side. Host, port and credentials are issued privately after account activation.
| Parameter | Value / how it is set |
|---|
| Protocol version | SMPP v3.4 |
| Bind mode | bind_transceiver (recommended) |
| Host and port | Shared in your SMPP onboarding document after account activation |
| system_id and password | Username and password issued by SMSGatewayHub |
| Throughput | Configurable per SMPP session, agreed with our team |
| source_addr | Your DLT-registered header (sender ID) |
| registered_delivery | Set to request a delivery receipt for each submit_sm |
| data_coding | 0 for standard GSM text, 8 for UCS2 (Unicode) |
| DLT principal entity ID | Passed as a TLV on submit_sm |
| DLT template ID | Passed as a TLV on submit_sm |
| PE-TM chain hash | Passed as a TLV on submit_sm where the chain requires it |
| Keep-alive | enquire_link at a regular interval on every bind |
Need the full onboarding procedure? The SMPP API page carries our SMPP SOP and reseller user guide. Exact TLV tag numbers are confirmed in your onboarding document.
SMPP connectivity resource map
Everything related to SMPP on SMSGatewayHub, grouped by what you need to do next.
SMPP connectivity vs HTTP API: which do you need?
Choose SMPP connectivity when you send at sustained high volume, run your own SMSC client or resell SMS: a persistent bind avoids per-request overhead, receipts come back on the same session and throughput is set per session. It is most cost-effective for businesses sending around 5 lakh SMS or more a month. Resellers getting started can begin with our standard SMPP API.
Choose the HTTPS API for websites, apps and CRMs where simplicity matters more than raw throughput. Both run from the same SMSGatewayHub account with the same DLT setup. For code samples, see sending SMS in Python and maximising ROI on high-volume OTP delivery.
Frequently Asked Questions
What is SMPP connectivity and why do enterprises use it?
SMPP (Short Message Peer-to-Peer) is the industry-standard protocol for high-volume A2P SMS. Unlike an HTTP API, it keeps a persistent TCP session open, so messages stream continuously and delivery receipts come back on the same connection. Banks, telecom platforms and large enterprises use SMSGatewayHub SMPP connectivity for this throughput and lower latency.
What is the difference between SMPP connectivity and the SMPP API page?
The SMPP API page covers SMSGatewayHub's standard SMPP account for resellers, with the SOP and reseller user guide. This SMPP connectivity page covers enterprise binds: throughput agreed per session, DLT parameters on each submit_sm and failover. Both use the same SMPP v3.4 protocol and DLT setup.
Which SMPP version and operations does SMSGatewayHub support?
SMSGatewayHub supports SMPP v3.4, including bind_transceiver, submit_sm, deliver_sm and enquire_link, with configurable throughput limits per SMPP session. Any standard SMPP client library in Java, Python, PHP, .NET or C++ can connect.
How are DLT entity ID and template ID passed over SMPP?
In India the principal entity ID and DLT template ID are sent with every submit_sm as optional TLV parameters, and a PE-TM chain hash may also be required. The operator matches these against your DLT registration and rejects messages that do not match. SMSGatewayHub confirms the exact tags in your onboarding document.
How do I connect to the SMSGatewayHub SMPP server?
After account activation, SMSGatewayHub shares the SMPP host, port, username and password and whitelists your server IPs. You then bind in bind_transceiver mode with any SMPP v3.4 client. Our team provides free integration support for enterprise setups.
Is there a minimum volume for SMPP?
SMPP is available to enterprise accounts and there is no fixed minimum, but it is most cost-effective for businesses sending around 5 lakh SMS or more a month. Below that, the HTTP or HTTPS API is simpler. Use the SMS cost calculator to compare.
What does SMPP connectivity cost?
SMSGatewayHub uses Pay As You Go pricing: you buy credits as needed and pay only for delivered SMS; exact rates depend on volume and route, see https://www.smsgatewayhub.com/pricing or talk to sales on 1800 102 1822.
Get enterprise SMPP connectivity
Start with 1,000 free SMS credits, free DLT guidance and free SMPP integration support from our engineers.