Intelligent multi-layer SMS routing with complete control at every layer. Route Plans define strategy, Routes specify paths, Trunks manage connections, and Suppliers deliver messages. Includes auto failover, DLR tracking, and real-time monitoring.
4-Layer
Routing Architecture
Plan → Route → Trunk → Supplier
Auto
Failover Routing
Automatic failover on failure
DLR
Delivery Tracking
End-to-end DLR correlation
Multi
Connection Types
SMPP, HTTP, RCS, OTT, Voice
Complete message flow from client to mobile operator and back
Client
HTTP API, SMPP ESME, Dashboard
Route Plan
Routing strategy & grouping
Routes
Priority-ordered paths
Trunks
Connection configurations
Suppliers
SMS providers & aggregators
DLR Flow (Reverse): Mobile → Supplier → Trunks → Routes → Route Plan → Client (HTTP/ESME Push)
Complete control at every stage of SMS delivery
Ready-to-use SMS provider connectors for instant setup
And many more — add custom connectors for any SMPP or HTTP SMS provider
Enterprise routing capabilities
Routes are evaluated in priority order. The highest-priority route is tried first, with automatic fallback to lower-priority routes on failure.
Automatic failover at every layer — Trunk fails → try next Trunk. Route fails → try next Route. All Routes fail → queue or return undelivered.
End-to-end DLR tracking with unique message IDs that correlate delivery reports back to original messages through the entire routing chain.
Configure transactions-per-second (TPS) limits per route, trunk, and supplier. Prevent supplier throttling and manage traffic distribution.
Routes and trunks support SMPP v3.4, HTTP REST API, RCS, and custom protocols. Mix and match protocols within a single Route Plan.
Assign different Route Plans to different clients and sub-clients. Granular routing strategy per customer with independent supplier configurations.
Real-time SMPP bind status monitoring for all connected suppliers. View transmitter, receiver, and transceiver bind states from the dashboard.
Visual route map interface showing the complete routing topology. Configure per-country routing, prefix-based routing, and default routes.
Monitor SMS delivery rates, response times, failover events, and supplier performance per route, trunk, and supplier in real-time.
Common questions about multi-layer SMS routing
From the Net2APP dashboard, go to Route Plans → Add New Plan. Give your plan a name, then add Routes with priority ordering. For each Route, configure Trunks with supplier connections. Finally, assign the Route Plan to a client. The entire setup takes minutes and changes take effect immediately.
The SMS routing engine automatically detects supplier failure through connection monitoring and DLR timeouts. It then fails over to the next available Trunk in the Route. If all Trunks in a Route fail, it moves to the next Route in the Plan. This failover happens in real-time without manual intervention.
Yes. Net2APP supports prefix-based routing and country-specific route maps. You can configure different Routes for different country prefixes, allowing optimal supplier selection per destination. For example, route Bangladesh traffic through one supplier and India traffic through another.
Failover is nearly instant. The system monitors supplier connections via SMPP bind status and HTTP response times. When a supplier fails to respond within the configured timeout (typically 2-5 seconds), the next Trunk is tried immediately. Failover at the Route level is similarly fast.
Yes. Net2APP provides test SMS functionality and a route testing interface. You can send test messages through specific routes to verify delivery, check DLR responses, and validate supplier configurations before assigning routes to production clients.
Complete SMS routing engine with Route Plans, Routes, Trunks, and Suppliers. 80+ pre-built connectors, auto failover, DLR tracking. No setup fees.
Deploy Your Instance Free →