Every number, every lifecycle stage. Audited, governed, automated
Mobile, landline and toll-free. Inbound and outbound portability with clearing-house workflows. Quarantine, automatic release, categorisation, regulatory audit — the full national-scale surface.
Numbers are regulatory inventory.
Telephone numbers carry regulatory obligations IPs don’t. Quarantine windows, portability deadlines, audit retention requirements vary by jurisdiction. This platform models all of it as data, not as code that has to be rewritten for every regulator.
Typed lifecycle
Eight states. Valid transitions only. Every change typed, audited and reversible.
Portability orchestration
Inbound and outbound flows with clearing-house integration. Deadlines tracked structurally.
Automatic quarantine release
Configurable windows per category and region. Auto-release when window closes.
Regulator-ready audit
Exportable evidence packs in TRAI, FCC, OFCOM formats. No manual reformatting.
Eight states. Valid transitions only.
Every transition is a typed operation, audited and reversible. Approval gates sit between sensitive states — assignment, port-out, release — with optional dual-authorisation.
Port out. Without spreadsheets.
Outbound number portability is a sequence with strict ordering: request, eligibility check, clearing-house submission, scheduling, activation, completion. Each step is a typed message with a deadline, an audit trail, and a rollback path.
Inbound flows work the same way, modelled from the receiving operator’s perspective. Failed ports rollback structurally — not by operator memory.
See it liveRun your number portfolio against this engine.
Seven workflows. One inventory.
Available → Reserved → Assigned → Active → Suspended → Quarantine → Released, with a Released-back-to-Available auto-return path. Every transition is a typed operation: who, when, with what justification, gated by which approval, captured in the immutable audit trail.
Invalid transitions are blocked at the data layer. You cannot assign a quarantined number without going through the proper release path.
Inbound and outbound port flows. Eligibility checks. Clearing-house submission and tracking. Scheduled activation with deadline enforcement. Failed ports rollback structurally. Disputes captured on-platform with the full message log.
Integration patterns for major regional clearing houses are provided as configurable connectors, not custom code per operator.
Configurable quarantine windows per category, region and jurisdiction. Automatic release back to the available pool when the window closes — no operator intervention. Window extensions captured with reason.
Rules engine for number categorisation. Exchange-prefix associations modelled as data. Numbering plans are configuration, not code. New regulator-mandated categories can be added without a deploy.
Origin-based and destination-based routing rules. Time-of-day routing. Failover chains. Route precedence captured with audit lineage so disputed call routing decisions can be replayed.
Full history. Exportable evidence packs in TRAI India, FCC United States, and OFCOM United Kingdom formats. Per-jurisdiction retention windows. The evidence pack is what the regulator asks for — not what your team had to manually reformat overnight.
Exhaustion forecasting per category and region. Block-acquisition lead time tracked alongside utilisation, so commissioning of new blocks completes before the network runs out.
Tens of millions of numbers. Every state. Every history.
What operators say about running it.
Direct quotes from network architects and operations leads at our deployed carriers. Names and brand identities are protected by NDA.
Replacing four separate inventory systems with one unified resource graph removed three full-time positions worth of reconciliation work. The drift problems we used to chase weekly simply stopped occurring.
The TMF Open API surface meant we could integrate with our existing OSS catalogue without any custom adapter work. Cutover was a six-week project, not the eighteen-month migration we had budgeted.
Capacity exhaustion alerts caught a /20 block we were about to run out of with 47 days of lead time. That single incident paid for the entire deployment.
Everything you need to evaluate.
Number Inventory Management — Product datasheet
Capability matrix, data-model, performance characteristics, supported TMF APIs.
Deployment options & sizing
Reference hardware, tenant capacity, latency budget, HA topology.
Security architecture overview
Encryption, RBAC, audit, key management. SOC 2 controls mapping.
Migrating from legacy DDI / NIM
Shadow-mode reconciliation strategy. Zero-downtime cutover playbook.
TMF Open API integration patterns
Mapping Number Inventory Management to TMF 633, 638, 645, 656 — with example payloads.
Multi-tenant deployment for MVNOs
Hierarchical isolation. Tenant onboarding playbook. Operational handoff model.
Tell us about your stack. We’ll map the fit.
A 30–45 minute technical walkthrough of Number Inventory Management — mapped to your existing OSS/BSS environment. You’ll hear back from a solutions engineer within one business day.
- Architecture review against your current inventory stack
- Live demonstration of the workflows that matter to your team
- Sizing, deployment model, and migration playbook
- TMF API surface walkthrough with example payloads