USSD PULL (subscriber-initiated)
Subscriber dials a service code *123# and the gateway drives the dialogue. Single-MT and multi-step flows, full MAP TCAP handling, response routing by service code and brand.
Carrier-grade USSD Gateway for mobile operators. Bridges SS7/MAP signalling with modern HTTP backends. Production-proven at Tier-1 scale, redesigned for Kubernetes from the ground up.
OVOO USSD-GW is live at a major Tier-1 European MNO, handling millions of USSD dialogues per day across multiple service codes and subscriber brands. The same codebase, refactored onto OVOO SLEE and Kubernetes, is what we deliver to new operators.
Three dialogue patterns, one codebase. Run one, two, or all three side by side.
Subscriber dials a service code *123# and the gateway drives the dialogue. Single-MT and multi-step flows, full MAP TCAP handling, response routing by service code and brand.
Backend services trigger USSD dialogues toward subscribers. Notifications, opt-in flows and multi-step prompts keep state continuity through the full session lifetime.
A single deployment serves multiple brands and MVNOs. MSISDN-to-brand mapping is resolved in memory and routing rules apply per service code.
Every use case below shares the same platform, the same observability stack and the same integration point.
Secure USSD channel between subscribers and banking partners. Multi-step dialogue flows, brand-aware routing and structured logs for audit.
Self-care service codes for prepaid balance, data allowance and top-up status with a low-latency request-response path.
Network-initiated USSD push for service alerts, promotional opt-ins and time-sensitive prompts with optional interactive replies.
Multi-step USSD wizards for adding services, changing tariff plans or confirming entitlements without an external session store.
Welcome messages and rate disclosures triggered on inbound roaming events without changing the operator HLR or MSC.
Shared USSD gateway for multiple MVNOs from one deployment, with per-brand service codes and independent backend endpoints.
Designed for operator-grade reliability from the start, not bolted on after the fact.
Throughput scales with pod count, with no architectural ceiling. Sized for Tier-1 traffic from day one and validated under sustained peak load.
Two sites run simultaneously, with session affinity preserved at the SS7 layer through STP routing rather than application stickiness.
SCTP, M3UA, SCCP, TCAP and MAP RA are built and owned by OVOO, keeping full control over transport and failover behavior.
Native Kubernetes deployment via Helm and ArgoCD GitOps. Runs on IaaS, CaaS or bare metal with no vendor lock-in.
Enable per-MSISDN debug tracing in production without restarts. TTL-bounded traces are streamed into the operator observability stack.
Session state lives in the SBB activity context and brand mapping loads from ConfigMap, moving operations into GitOps merge requests.
| Interfaces | MAP / SS7 (TCAP / SCCP over SIGTRAN: M3UA / SCTP), HTTP / XML subscriber services, optional SMPP, REST management API |
|---|---|
| Throughput | Hundreds of sessions per second per pod with linear horizontal scaling |
| Redundancy | Active-active multi-site, STP-layer session affinity, stateless per pod, zero in-flight loss for single-MT |
| Deployment | Kubernetes / CaaS, IaaS, bare metal, Helm + ArgoCD GitOps, any telco cloud |
| Observability | Prometheus metrics, structured JSON logs, ELK / Kibana, selective tracing API, APM-compatible export |
| Standards | 3GPP MAP / TCAP, SIGTRAN M3UA (RFC 4666), SCTP (RFC 4960), JSR-240 SLEE |
We'll deliver a technical architecture session or a scoped integration estimate within 5 business days. No commitment, just clarity on what integration looks like for your SS7 environment, HLR setup and service backends.