Customer connections
SMPP 3.4 server with TLS, plus an HTTP API. Binds are monitored, throughput limited per credential and per account.
Platform overview
A2P SMS gateway software, from submit_sm to invoice
Auvia Gateway is the software layer between your SMS customers and your suppliers. It accepts traffic over SMPP and HTTP, picks a route with rules you control, follows every message to its delivery receipt, and keeps the accounts of every segment through to the invoice.
SMPP 3.4 / 5.0SMPP over TLSHTTP(S) APIPer-segment billingCloud or on-premise
Architecture
Every component of an SMS business, in one diagram
Platform architecture
MT submitDelivery receiptMO inboundNumber lookup
Components of every installation, cloud or on-premise. Numbered steps follow one MT message.SS7 is delivered through a connected SMPP-to-SS7 gateway.
What it does
Everything an SMS business runs on, in one system
Buying separate tools for SMPP, routing, rating and reporting means reconciling them every month. Auvia keeps one record per message across all of them.
Rule-based routing
First-match rules on customer, country, network, sender and content type, with pools for least cost, weight, split or quality.
Supplier delivery
SMPP 3.4 and 5.0 client binds with TLS, HTTP suppliers, and SS7 through a connected SMPP-to-SS7 gateway.
Billing per segment
Price reserved at acceptance, charged once, margin known per part. Invoices and statements from real traffic.
Firewall and lookup
Two-stage SMS firewall and HLR/MNP lookup over DNS ENUM/NAPTR or HTTP providers.
Customer self-service
A white-label portal where customers send, read reports, check their balance and manage keys.
Traceability
Every message, explained
Open any message and see each pipeline step with its time, the route and supplier it took, what it earned and the raw SMPP PDUs on both sides. Support answers come from data, not guesses.
- Step-by-step pipeline: submit, validation, routing, pricing, balance, queue, upstream, DLR
- PDU ladder with decoded fields and hex, PCAP export
- Revenue, supplier cost, HLR dip and net margin per message
One message, end to end
RequestReceipt
The acknowledgement is sent only after the message is stored. Retransmitted parts are neither sent nor billed twice.
Operations
Monitoring your NOC can act on
Supplier and customer binds with a day of uptime history, queues, live traffic and alerts by email, Telegram, Slack and web push. A route quality guard switches off a route when its delivery rate drops.
- Bind uptime history for every supplier and customer
- Queues, in-flight messages and live submit rate
- Traffic and server health alerts with thresholds
Feature catalogue
Everything the platform ships, by area
Customers
How your customers connect, and what keeps them inside their limits.
- SMPP 3.4 server, plain and over TLS
- Transmitter, receiver and transceiver binds
- Session limits and IP allowlist per credential
- Automatic IP blocking after failed binds
- TPS limit per credential and per account
- Queue priority 1–10 per account (OTP before bulk)
- HTTP API with Idempotency-Key, up to 1,000 per request
- Signed webhooks for receipts and inbound messages
- Sender ID approvals and duplicate suppression
- Bounded delivery-receipt retries to customers
Suppliers
Every way out of the platform, monitored per trunk.
- SMPP 3.4 and 5.0 client binds
- TLS towards suppliers that offer it
- Throughput and session limits per trunk
- Outbound pacing: bursts wait instead of failing
- TON/NPI settings per trunk
- HTTP suppliers with error-code mapping
- SS7 via a connected SMPP-to-SS7 gateway
- Bind uptime history and last error
- Trunk changes applied to live sessions
- Supplier price lists imported from email
Message handling
What happens to each message between submit and receipt.
- Acknowledgement only after the message is stored
- Up to 20 parts per SMPP message, 10 over HTTP
- Parts validated before they are acknowledged
- Retransmitted parts neither sent nor billed twice
- GSM-7 / Unicode detection and segment count
- Optional transliteration to reduce parts
- Error-code registry for every supplier
- Retransmission of temporary errors
- Reroute on failure, at most 6 sends
- Two-way: virtual numbers and MO routing
Routing
Decisions you can read, test and change live.
- First-match rules with a visual editor
- Match on customer, country, MCC/MNC, prefix, sender, encoding, parts
- Pools: least cost, weight, percentage split, quality
- Routing scripts with preview and trace
- Routing Logic on SMPP: block, route, reduce parts, simulate receipt
- HLR/MNP-based routing and pricing
- Routing products applied in one step
- Routing Analyser: route, price, margin without sending
- Guards: minimum margin, quotas, time windows, loops
- Route quality guard switches off failing routes
Monitoring
What your NOC sees, from one message to the whole platform.
- Analytics: traffic, delivery, revenue, profit, MT and MO
- Live submit rate, queues and in-flight messages
- All Messages with filters and CSV export
- Message Debugger: pipeline steps with timings
- PDU ladder with decoded fields, PCAP export
- Customer and supplier bind monitoring
- Problematic binds and blocked IPs
- Alerts by email, Telegram, Slack and web push
- Audit log of every user action, 90 days
- AI console with data masking
Billing and finance
Rating, settlement and documents from the same records.
- Per-segment customer price and supplier cost
- Price reserved at acceptance, charged once
- By submitted or by delivered, per account
- Balance and credit limit checked before sending
- HLR dip cost deducted from margin
- Multi-currency with stored exchange rates
- Invoices, credit notes and PDF templates
- Account statements and payment reminders
- Supplier invoice inbox and netting
- CDR exports up to 500,000 rows, finance REST API
Security
Controls that matter when traffic is revenue.
- TLS for SMPP and HTTPS
- IP allowlists per credential and per API key
- API keys stored only as hashes
- Permission-based roles
- Two-stage SMS firewall: submit gate and content
- Blocked messages with the rule that stopped them
- Number lookup before paying a supplier
- Audit log with sign-ins
- AI console masks numbers, names and texts
- Webhook URLs restricted to public HTTPS hosts
Deployment
Where it runs and who owns it.
- Dedicated installation per customer
- On-premise as a compiled container image
- Your name and logo on panel and portal
- One SMPP listener owner, shared live state
- Scheduled jobs coordinated across nodes
- Separate stores for configuration, live state and archive
- Versioned database migrations per release
- Customer portal isolated by the server
- HTTP, SMPP and REST APIs in every installation
- Evaluation measured on your traffic
Capabilities
One platform, every capability included
Auvia Gateway is a single product. These are the parts of it, each explained on its own page.
SMPP connectivity
SMPP 3.4 and TLS for customers, 3.4/5.0 to suppliers.
Routing and LCR
Rules, pools, least cost and reroute on error.
Billing and invoicing
Per-segment rating, balances and invoices.
Firewall and HLR/MNP
Number lookup and two-stage traffic filtering.
Customer portal
Self-service for your customers, under your brand.
AI console
Ask the platform in plain language, with data masked.
SMS API
HTTP sending, signed webhooks and REST data APIs.
Concrete numbers
Limits written in the code, not in a brochure
Functional limits of the current release. Throughput is measured on your own traffic during an evaluation.
20 / 10parts per message, SMPP / HTTPLonger SMPP concatenations are rejected before the ACK
1,000messages per HTTP requestEach message validated on its own
6sends per message, across reroutesFirst attempt plus failover, then the message closes
24 hidempotency windowSame key, same answer, no second send
500krows per CDR exportAlso the cap for audit log exports
200krows per contact importCustomer portal contact lists
180 daysconversations in the portalTwo-way chat history window
90 daysaudit log retentionThen removed automatically
Integrations
Works with the networks and tools you already use
Suppliers, number lookup, route testing, AI models, alerts and your own systems.
Supplier connectivity
Every way out of the platform.
- SMPP 3.4 and 5.0
- SMPP over TLS
- HTTP suppliers
- SMPP-to-SS7 gateways
Number lookup
Operator and porting data before you pay a supplier.
- DNS ENUM/NAPTR HLR
- MNP lookup
- HTTP HLR providers
Route testing
Check delivery on a route from the panel.
- TelQ
- Testelium
AI models
For the AI console, with data masking.
- Anthropic Claude
- OpenAI
- Azure OpenAI
- Local models
Alerts
Traffic and server health, where your team looks.
- Telegram
- Slack
- Web push
Your systems
ERP, BI and customer applications.
- Finance REST API
- Signed webhooks
- CSV exports
- HTTP SMS API
Switch to Auvia
Moving from your current platform is simple
Bring your price lists, networks and customer connections across without rebuilding them by hand.
Customer price lists
Import customer prices from a spreadsheet, per country and network.
Supplier price lists
Load supplier rate sheets, or let import rules read them from the supplier emails.
Networks and prefixes
Import MCC/MNC networks and number prefixes, so routing and pricing match from day one.
SMPP accounts
Create SMPP accounts with the system IDs your customers already use, so most of them only change the host address.
FAQ
Questions buyers ask
Does it support both SMPP and SS7?
SMPP 3.4 and 5.0 natively, towards customers and suppliers. SS7 runs through a connected SMPP-to-SS7 gateway: Auvia manages the SS7 profiles and reads back the results, while the gateway handles the MAP/SIGTRAN side.
Is there an HTTP API as well as SMPP?
Yes. POST /v1/sms sends up to 1,000 messages per request with optional idempotency, and delivery receipts and inbound messages are pushed to your HTTPS endpoint as signed webhooks.
How are long messages accounted for?
Per segment. Each part is priced, and a message counts as delivered only when all its parts are. Retransmitted SMPP parts are neither sent nor billed twice. SMPP accepts up to 20 parts, the HTTP API up to 10.
Which deployment options are available?
A dedicated cloud installation, or on-premise for large operators on your own servers, domain and database. Each installation serves one customer and carries your name and logo.
What throughput can the platform handle?
Throughput depends on your infrastructure, connections and configuration, so we do not publish a guaranteed figure. During a technical evaluation we measure throughput and latency on your routes and hardware.
Keep exploring
