Compile policy into a local real-time representation
PostgreSQL remains authoritative for administration, while a C++ loader/compiler transforms the configured rules into an optimized in-memory form. Per-call checks never require a PostgreSQL query.
Networking and High-Performance Systems
A real-time mobile-network filtering gateway with custom C++ in-memory matching, SIGTRAN/CAMEL integration, more than 10 million call checks per second against 10 million policy entries, and multi-operator production deployment.
SentinelVoice connects to a mobile-network call-control environment through SIGTRAN and CAMEL integration. For each relevant call attempt, it extracts the calling and called numbers, evaluates them against customer-maintained policy records, and returns one of three enforcement actions: allow the call, drop it, or forward it to an IVR.
The gateway does not determine whether a call is fraudulent. Customer teams and surrounding systems create the blacklist, policy, and pattern records. OPTIME engineered the deterministic, high-performance real-time enforcement layer that applies those supplied decisions inside the signaling path.
Policy records can contain exact values and pattern-based rules. At the required rates, scanning a flat list or evaluating a conventional collection of regular expressions for every call would have been computationally unsuitable, so the real-time design required a different local representation and matching approach.
Across a two-year specialized telecom program, OPTIME engineered the signaling integration, the higher protocol/application functionality needed by the gateway, the C++ rule-loading and matching engine, the administration plane, production integration, and performance validation.
OPTIME used the Dialogic SIGTRAN stack as the lower transport/signaling foundation and implemented the application-specific functionality required above MTP3 for the CAMEL-integrated gateway. The public architecture intentionally stops short of proprietary protocol flows and customer MSC configuration.
Relevant mobile-network call attempts enter the filtering workflow through the customer’s CAMEL-integrated MSC environment.
The Dialogic SIGTRAN stack provides the lower signaling foundation used by the gateway.
OPTIME-built functionality above MTP3 extracts the calling and called numbers required for policy enforcement.
The C++ engine evaluates exact and pattern-aware policy entries using a proprietary optimized local representation.
The gateway returns allow, drop, or forward-to-IVR without performing independent fraud analysis.
Operators manage filtering and policy records through the administration console.
Backend services validate and coordinate policy administration outside the per-call processing path.
PostgreSQL remains the canonical administrative and policy store rather than a database queried for every call.
The C++ loader transforms configured records into the optimized in-memory representation used by the real-time plane.
PostgreSQL remains authoritative for administration, while a C++ loader/compiler transforms the configured rules into an optimized in-memory form. Per-call checks never require a PostgreSQL query.
The rule set includes exact values and patterns. A conventional sequential or regex-style scan across the complete set would not meet the required rate, so OPTIME designed a proprietary pattern-aware matching architecture.
Customer and surrounding systems decide which policy records represent fraud-prevention actions. SentinelVoice applies those supplied records deterministically and does not infer fraud.
The achieved throughput did not depend on specialized acceleration hardware, allowing the production gateway to run in virtualized Linux server environments.
The original requirement was approximately one million call checks per second against roughly one hundred thousand policy records. OPTIME’s optimized in-memory matching architecture ultimately exceeded ten million checks per second against a ten-million-entry rule set.
The design keeps administration and canonical policy storage out of the signaling hot path. Rule compilation happens when policy changes are loaded; call processing uses only the prepared local representation and immediate enforcement logic.
The delivered gateway continues operating in production across multiple mobile operators. It enforces customer-supplied filtering policy through CAMEL/SIGTRAN integration and runs in ordinary virtualized server environments rather than requiring specialized accelerator hardware.
OPTIME delivered a production filtering gateway that exceeded ten million call checks per second against ten million policy entries while preserving a strict boundary between customer fraud-policy decisions and deterministic real-time enforcement.
The customer’s starting performance and policy-set requirement.
Validated matching throughput and rule-set size for the optimized architecture.
CONTACT US
Austin, Texas
Distributed engineering teams across North America, Europe, the Caucasus, and Latin America.
[email protected]