Connect your own SMSC over SMPP
Этот контент еще не доступен на вашем языке.
If your business already has a direct connection to a mobile operator or aggregator over SMPP, Pushwoosh can send SMS through that same connection instead of one of the listed SMS providers. Messages go out over your own bind, at the throughput your contract allows, and are sent from one-time campaigns, Customer Journeys, and the Messaging API exactly like any other SMS provider.
What SMPP is and why it matters
Anchor link toSMPP (Short Message Peer-to-Peer) is the protocol mobile operators and aggregators use to exchange SMS traffic between systems. A bind is a direct, authenticated connection to your operator’s or aggregator’s SMSC (SMS center) — the same kind of connection your telecom or messaging team already maintains if you send SMS outside Pushwoosh today.
Sending through your own bind instead of one of Pushwoosh’s built-in providers keeps you on your own relationship with that operator or aggregator: your own negotiated per-message rate, your own registered sender ID, and delivery status reported straight back from them, with no other party in between.
This fits businesses that already have a live SMPP connection and contract with an operator or aggregator, typically larger senders with dedicated numbers or negotiated pricing, who want Pushwoosh to send over that same connection instead of taking on a new provider relationship.
What to send us
Anchor link toPushwoosh’s team configures the connection using the settings below. Have them ready from your operator or aggregator before reaching out.
| Setting | What it is |
|---|---|
| SMSC host and port | The address of your operator’s or aggregator’s SMPP server |
| System ID and password | The bind credentials your operator or aggregator issued you |
| System type | An optional identifier some operators or aggregators require on bind |
| Sender ID | The sender id your messages go out under |
| TON and NPI (type of number, numbering plan indicator) | The addressing type for the sender and destination number, if your contract specifies non-default values |
| Throughput (messages per second and window size) | The send rate and number of unacknowledged messages in flight your contract allows |
| Message ID notation | Whether your operator or aggregator reports message ids as hexadecimal or decimal, if it differs between the submission response and the delivery receipt |
Sending messages and delivery status
Anchor link toOnce your bind is connected, send SMS the same way as with any other provider — from a one-time campaign, a Customer Journey, or the Messaging API. Delivery receipts come back automatically and update the message status, the same as with a routed provider.
A message longer than one SMS segment is split automatically. Unlike Pushwoosh’s routed providers, which charge a flat price per message, your operator or aggregator bills each segment of a long message separately under your own contract.