auviaGateway
SS7 delivery

SS7 SMS delivery through your SMPP-to-SS7 gateway

Operators can terminate traffic on SS7 without giving up routing, billing and traceability. Auvia keeps the SS7 parameters as profiles, sends them with each message to your SS7 gateway and records the result.

SS7 profilesOPC/DPCTranslation typesRetry patterns
Platform architecture
MT submitDelivery receiptMO inboundNumber lookup
Auvia Gateway architectureCustomers connect over SMPP, HTTP or the portal. Inside the gateway each message is validated, filtered, looked up, routed, rated, stored and acknowledged, queued and retried. Suppliers are reached over SMPP, HTTP or SS7 through a gateway. A configuration store, a live-state layer and a message archive form the data layer. CUSTOMERSSUPPLIERSDATA LAYER HLR / MNP providersDNS ENUM/NAPTR · HTTP AUVIA GATEWAYSMPP listener · API · workers Validatenumber · sender1Firewallsubmit + content2HLR / MNPreal operator3Routerules · LCR4 Ratereserve · once5Store · ACKthen submit_resp6Queuepriority · pacing7Retryreroute · retry8 ObserveMessage Debugger · PDU trace · Analytics · Alerts · Audit log Financeper-segment rating · balances · invoices · CDR export · REST API AssistAI console with masking · Routing Analyser · route tests SMPP customersSMPP 3.4 · TLSTX · RX · TRX bindsHTTP APIPOST /v1/smssigned webhooksCustomer portalcampaigns · chatswhite-label SMPP suppliersSMPP 3.4 / 5.0 · TLSper-trunk pacingHTTP suppliersJSON over HTTPSerror-code mappingSS7 networkvia SMPP-to-SS7gateway + profiles Configurationaccounts · pricesLive statequeues · countersMessage archiveCDR · analytics
Components of every installation, cloud or on-premise. Numbered steps follow one MT message.SS7 is delivered through a connected SMPP-to-SS7 gateway.
How it works

Auvia and your SS7 gateway, side by side

Auvia GatewayYour SMPP-to-SS7 gateway
Customer trafficAccepts SMPP and HTTP, validates, routes and prices—
SS7 parametersKeeps SS7 profiles and sends them as TLVs 0x1401–0x1438Applies them on the signalling network
Signalling—MAP over SIGTRAN or TDM
ResultsReads back the outcome, writes receipts and billingReturns the result of the delivery attempt
In the console

What you manage as an SS7 profile

SMSC addresses

The SMSC global titles used for submission.

OPC and DPC

Originating and destination point codes.

Translation types

Translation types for global title routing.

Retry pattern

How often and how long the gateway retries.

HLR override

Use a specific HLR for routing information.

Per-message

The profile travels with each submission to the SS7 gateway.

FAQ

SS7 questions

Does Auvia speak SS7 or SIGTRAN directly?
No. Auvia connects to an SMPP-to-SS7 gateway over SMPP. The gateway handles MAP and SIGTRAN; Auvia manages the SS7 profiles, sends them with each message and reads back the results.
Which SS7 parameters can I manage?
SMSC addresses, OPC and DPC, translation types, the retry pattern and an HLR override, kept as SS7 profiles in the console.
How are the SS7 parameters sent?
As vendor TLVs in the 0x1401–0x1438 range on the SMPP submission to the SS7 gateway.
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.
Talk to us

Let’s talk about your traffic.

Tell us your business type, the protocols towards customers and suppliers, cloud or on-premise, and the capabilities you care about. Our team comes back with a demo on the console or a technical evaluation on your scenario.

+971 58 513 4804sales@auviagateway.com