A route decides which connect(s) carry a message. You assign routes to users, not connects, so one route change moves traffic for every client on it without touching their accounts.
Where to find it
Sidebar → SMPP Client → Routes → Add.
Route fields
| Field | What it does |
|---|---|
| Name | Internal name, e.g. IN_TRANS_VendorA_B_RR |
| Display Name (Alias) | What clients and resellers see. Use a neutral name like “Premium Transactional” so vendor names are never exposed |
| Description | Internal notes |
| Account Type | OTP, TRANSACTIONAL, PROMOTIONAL or INTERNATIONAL (see below) |
| Strategy | How traffic is spread across connects |
| Whitelisted Sender ID Check | Enabled: only whitelisted sender IDs can use this route |
| Apply Rules | Enabled: routing/normalization rules are evaluated for this route |
| Message Retry | Retry failed messages on other connects (see How to Configure Message Retry) |
| Reject Non PEID Messages | Yes: reject messages without a DLT Principal Entity ID (India) |
Account Type: which one to use
- OTP: low, steady, latency-sensitive traffic. Keep OTP on its own route so bulk campaigns never slow it down.
- TRANSACTIONAL: non-OTP alerts and notifications.
- PROMOTIONAL: bulk marketing; held to the promotional sending window.
- INTERNATIONAL: non-India traffic; Indian number filtration isn’t applied.
Strategy: which one to use
| Strategy | Behaviour | Use it when |
|---|---|---|
| Dedicated | One connect only | A client or product must stay on one vendor (contractual, compliance or testing reasons) |
| Round Robin | Messages are spread evenly across the selected primary connects | Several vendors of similar quality and cost; you want to use all their TPS |
| Percentage | Each connect gets the share you set | You want to control cost mix or trial a new vendor with, say, 10% of traffic |
| Priority | Uses the selected connects in priority order, with a Priority Threshold Delay (seconds) | A preferred (cheaper or better) vendor first, with others only when it’s slow or backed up |
Steps
- Enter Name, Display Name (Alias) and Description.
- Select the Account Type.
- Select the Strategy, then the Primary Connect(s). For Percentage, set each connect’s share; for Priority, set the threshold delay.
- Set Whitelisted Sender ID Check, Apply Rules and Reject Non PEID Messages as needed.
- Optionally enable Message Retry.
- Save, then assign the route to users from their user attributes.
Assigning routes to resellers
With Set Friendly Routes in a user’s sub-user attributes, you can give a reseller several routes. They see only the Display Name, and can assign those routes to their own sub-users. Always set a Display Name before sharing a route with a reseller.
Good practice
- One route per traffic type per destination. Mixing OTP and promotional traffic on one route makes latency unpredictable.
- Trial new vendors with Percentage. Start at 5–10%, compare delivery rates and latency, then increase.
- Name routes consistently:
<country>_<type>_<vendors>_<strategy>. It makes route lists, reports and rule matching much easier to read. - Clone instead of rebuilding. Use Clone for a new variant, then change only what differs.
Related articles
- How to Add a New SMPP Connect
- How to Configure Message Retry Across Up to 4 Connects
- What are Phone Routing Rules?
- How to add multiple MCC MNC routing for a user dynamically
Found this useful?Add as Preferred Source on Google