An A2P SMS trading infrastructure: it receives traffic over SMPP, routes it with a rule engine to SMPP or SS7 suppliers, follows every message through to the delivery receipt and keeps the accounts of every segment through to the invoice.
FAQ
The answers for those evaluating.
The questions specialists ask us first.
Auvia can be installed in the cloud or on-premise for large operators. On-premise deployment uses the customer’s systems.
Yes. White-label mode lets you show your own application name and logo on the operator panel and on the customer self-service portal.
Yes. Towards customers: SMPP 3.4, SMPP over TLS, HTTP(S) API and web portal. Towards suppliers: SMPP 3.4 and 5.0, plus SS7 over SIGTRAN (M3UA) through the built-in SMPP-to-SIGTRAN gateway.
With the Routing Analyser, which runs the same decision path as real traffic without sending anything, and with the coverage check for up to 500 destinations at a time.
Every part is tracked individually: retransmitted parts are neither sent nor billed twice, and each charge is recorded only once, even with retries and repeated receipts.
SMPP over TLS and an HTTPS panel, per-credential IP allow-lists, automatic IP blocking after repeated failed binds, about fifty role-based permissions, and API keys stored only as hashes and revocable.
No. They are illustrative sample data from the console, with identifying information masked, and do not represent guaranteed results or service levels.
Explore the feature catalogue, the console screens and the documented integrations: they are designed to give technical teams everything needed for a preliminary evaluation.
More questions?
The feature catalogue and the documented integrations answer in detail.