Choose the route for each message
Routing policies weigh cost, quality, destination country, number portability and partner SLAs. SMPP and MMSC interconnects carry the selected traffic.
An enterprise submits a message; your network must select a partner route and account for the delivery result. OVOO Convergent Messaging Gateway runs that SMS/MMS interconnect and A2P path, applying routing, traffic and sender policies across the partners you use.
A gateway connects several commercial and operational decisions: who may send, which route carries the traffic and what the application receives when delivery succeeds or fails.
The controls below act at different points between a submitted message and its final delivery report.
Routing policies weigh cost, quality, destination country, number portability and partner SLAs. SMPP and MMSC interconnects carry the selected traffic.
Set rates and burst limits per connector, customer and route. Back-pressure and queues manage the difference between application demand and the receiving connection.
Govern sender IDs, templates and keyword or regex policies before traffic proceeds. Spam and fraud rules determine which submissions are accepted or rejected.
Delivery reports link the submitted message to its downstream status. Retry handling and dead-letter queues give operations a path for traffic that could not complete normally.
MNP and HLR lookups inform route and sender-policy selection. The rule engine applies the information relevant to the destination.
Track throughput, delivery ratio, cost and rejects alongside traces and service indicators. Operations and finance can examine the same messaging flow from different perspectives.
Connectors accept traffic, routing and policy choose its treatment, and reporting interfaces return the outcome. The gateway runs on Kubernetes and exposes APIs to the systems consuming that result.
Applications and partner systems connect through SMPP ESME/SMSC, MMSC or HTTP. TLS, mTLS and scoped tokens control access to the submission interfaces.
Accepted traffic reaches the route and policy layer. Destination information, partner rules and available sending capacity determine its next treatment.
Delivery reports and webhooks return status to applications. Reporting APIs, dashboards and audit trails give operations the context for investigation and reconciliation, with billing and OCS/TAS/JSLEE integration hooks.
A single delivery percentage does not explain ported destinations, sending limits or policy rejects. Follow each case to the control that owns it.
Distinguish a gateway acceptance from the final downstream report. Follow the DLR chain, retries and dead-letter handling when support needs to explain what happened to an individual message.
A campaign can exceed the rate available on a receiving connection. Read queued traffic and back-pressure alongside customer and connector limits before increasing the sending allowance.
Compare route cost with delivery quality, destination and portability information. The policy must reflect the partner SLA and sender rules as well as the commercial rate.