Skip to content
Telecom - Signaling & Messaging

OVOO USSD-GW

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.

Production-provenSession state in JSLEECloud-native CNF

In production. At scale. Today.

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 JSLEE and Kubernetes, is what we deliver to new operators.

  • Multi-brand routing and per-service-code logic active simultaneously
  • Active-active multi-site model, session affinity at the SS7 layer
  • GitOps deployment with Helm and ArgoCD, plus tested rollback procedures
  • Operator-grade volumes with linear scaling

USSD models on one platform

Subscriber-initiated and network-initiated dialogues differ in how they begin. Multi-brand routing determines which service backend handles either flow.

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.

USSD PUSH (network-initiated)

Backend services trigger USSD dialogues toward subscribers. Notifications, opt-in flows and multi-step prompts keep state continuity through the full session lifetime.

Route each dialogue to its brand

A single deployment serves multiple brands and MVNOs. MSISDN-to-brand mapping is resolved in memory and routing rules apply per service code.

Built for the scenarios operators actually run

USSD links a short service interaction on the handset to the backend that carries out the request. These examples show where that channel fits into an operator offer.

Mobile banking USSD

Secure USSD channel between subscribers and banking partners. Multi-step dialogue flows, brand-aware routing and structured logs for audit.

Balance and data inquiry

Self-care service codes for prepaid balance, data allowance and top-up status with a low-latency request-response path.

Subscriber notifications

Network-initiated USSD push for service alerts, promotional opt-ins and time-sensitive prompts with optional interactive replies.

Service activation flows

Multi-step USSD wizards for adding services, changing tariff plans or confirming entitlements without an external session store.

Roaming notifications

Welcome messages and rate disclosures triggered on inbound roaming events without changing the operator HLR or MSC.

MVNO USSD platform

Shared USSD gateway for multiple MVNOs from one deployment, with per-brand service codes and independent backend endpoints.

Operate the signalling path and session lifecycle

STP routing, SBB activity contexts and GitOps configuration each own a different part of running the gateway.

Hundreds of sessions per second per pod, linear scaling

Pod count provides horizontal capacity for new USSD traffic. Size the deployment against the expected session rate and service mix, then validate it under sustained peak load.

Active-active, multi-site

Two sites run simultaneously, with session affinity preserved at the SS7 layer through STP routing rather than application stickiness.

In-house SS7 / MAP stack

SCTP, M3UA, SCCP, TCAP and MAP RA are built and owned by OVOO, keeping full control over transport and failover behavior.

Cloud-native CNF

Native Kubernetes deployment via Helm and ArgoCD GitOps. Runs on IaaS, CaaS or bare metal with no vendor lock-in.

Selective tracing via API

Enable per-MSISDN debug tracing in production without restarts. TTL-bounded traces are streamed into the operator observability stack.

Session handling without an external database

Session state lives in the SBB activity context and brand mapping loads from ConfigMap, moving operations into GitOps merge requests.

Match the gateway to your network interfaces

OVOO USSD-GW technical specifications
InterfacesMAP / SS7 (TCAP / SCCP over SIGTRAN: M3UA / SCTP), HTTP / XML subscriber services, optional SMPP, REST management API
ThroughputHundreds of sessions per second per pod with linear horizontal scaling
RedundancyActive-active multi-site, STP-layer session affinity, JSLEE activity-context sessions, zero in-flight loss for single-MT
DeploymentKubernetes / CaaS, IaaS, bare metal, Helm + ArgoCD GitOps, any telco cloud
ObservabilityPrometheus metrics, structured JSON logs, ELK / Kibana, selective tracing API, APM-compatible export
Standards3GPP MAP / TCAP, SIGTRAN M3UA (RFC 4666), SCTP (RFC 4960), JSR-240 JAIN SLEE (JSLEE)

Evaluating USSD-GW for your network?

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.

Discuss USSD