Skip to content
Telecom · Platform

Convergent Messaging Gateway

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.

Interconnect & A2PRule-based routingFull DLR chain

Define the sending policy for each customer and route

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.

  • Which partners serve each destination
  • How cost and delivery quality influence routing
  • Which sender IDs and templates a customer may use
  • How portability information changes route selection
  • What rate each customer and connector can send
  • Which content rules reject a submission
  • How applications consume delivery reports
  • Who investigates queued or failed traffic

Route, govern and trace message traffic

The controls below act at different points between a submitted message and its final delivery report.

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.

Control traffic sent to a connector

Set rates and burst limits per connector, customer and route. Back-pressure and queues manage the difference between application demand and the receiving connection.

Apply sender and content rules

Govern sender IDs, templates and keyword or regex policies before traffic proceeds. Spam and fraud rules determine which submissions are accepted or rejected.

Keep the delivery-report chain

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.

Resolve number and partner policy

MNP and HLR lookups inform route and sender-policy selection. The rule engine applies the information relevant to the destination.

Inspect delivery and route economics

Track throughput, delivery ratio, cost and rejects alongside traces and service indicators. Operations and finance can examine the same messaging flow from different perspectives.

Connect the submission path to the delivery result

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.

Ingress & connectors

Applications and partner systems connect through SMPP ESME/SMSC, MMSC or HTTP. TLS, mTLS and scoped tokens control access to the submission interfaces.

Routing & policy

Accepted traffic reaches the route and policy layer. Destination information, partner rules and available sending capacity determine its next treatment.

Exposure & ops

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.

Investigate the exceptions behind delivery figures

A single delivery percentage does not explain ported destinations, sending limits or policy rejects. Follow each case to the control that owns it.

Submission accepted is not delivery confirmed

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.

Traffic volume is not connector capacity

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.

The cheapest route is not the only routing input

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.

Discuss messaging