Connect an SMPP platform to TelecomsXchange

TelecomsXchange speaks plain SMPP, so any SMS gateway or SMSC that can bind as an ESME can buy SMS routes, and any that can accept a bind can sell them. This page puts every value in one place for both directions; the platform guides show the exact configuration for Kannel, Jasmin and Restcomm SMSC.

Before you start#

• To buy: an account with Protocol Type SMPP, an SMS route bought from SMS Market, and funds on the account.
• To sell: an SMS route under Routes → My Routes with your SMSC's IP and port and the credentials TelecomsXchange binds with.
• Your platform's public IP address, for example 203.0.113.10, and access to its firewall.

How do I send SMS through TelecomsXchange?#

Configure one SMPP client connection on your platform:

Then make sure every message carries:

• destination_addr: the route's tech prefix, #, and the number in E.164 without + or 00: 80039#447700900123. A routing group's prefix works the same way: 444123#447700900123. A plain 447700900123 goes to the account's Default Routing Group, or its default SMS route if no group is set.
• source_addr: a sender ID registered on your account. Others are blocked or replaced by your default sender ID, according to the account setting shown under Sender Settings on Logs → SDR (SMS).
• registered_delivery set to 1 if your platform wants delivery receipts.

Each segment is billed at the route's price: up to 160 GSM or 70 UCS-2 characters is one segment, longer texts are billed per part at 153 or 67 characters. The submit_sm_resp carries the TelecomsXchange TLVs 0x1520 billing_price and 0x1521 billed_msgs_cnt. Split long texts into UDH parts on your side; some routes accept only single messages.

How do I receive delivery receipts?#

TelecomsXchange requests a receipt from the seller for every message. When the seller reports delivery, the receipt reaches your bind as a deliver_sm with id:<message_id> and stat:DELIVRD, where message_id is the one returned in your submit_sm_resp. Your platform matches it to the message it sent.

Receipts are relayed only while your bind is open. Keep the transceiver bind up permanently; if it was down, read the status from Logs → SDR (SMS) instead.

How do I receive SMS from TelecomsXchange as a seller?#

When you sell an SMS route, TelecomsXchange is the client and your SMSC is the server:

Your platform must:

1. Accept a bind_transceiver from 174.136.44.213 on the port you entered on the route, with that system ID and password.
2. Answer each submit_sm with submit_sm_resp within the route's SubmitSM Timeout: status 0 and your message_id to accept, any other status to refuse.
3. Send a deliver_sm receipt with id:<your message_id> and stat:DELIVRD when the handset confirms delivery.

Run Test Bind from the route's ⋮ menu in My Routes to check the connection. Interconnect Info shows the exact credentials for each route.

What about SMS to phone numbers?#

• You sell numbers: your SMSC binds to smpp01.telecomsxchange.com, TCP 2776, with login did and password did (or your custom credentials under DIDs → My DIDs → Authentication) and submits each inbound SMS to the number, without a tech prefix. See Sell phone numbers.
• You buy numbers: TelecomsXchange binds out to the SMPP Endpoint you set on the number, written smpp:login:password:number@host:port, so your platform must accept that bind. See Buy virtual phone numbers.

How do I test it?#

1. Check the bind: the Accounts page shows Bind Status ONLINE; click it for the SMPP BIND history.
2. Send one message to a test handset with an approved sender ID and the route's prefix: 80039#447700900123.
3. Confirm your platform logged a submit_sm_resp with status 0 and, a few seconds later, a deliver_sm with stat:DELIVRD.
4. Go to Logs → SDR (SMS), set Status to All Messages and click Search SMS. The message shows its Route, Amount, SMS Count and Status.

Platform guides#

What if something goes wrong?#