Xonware · XonIPAM Founder-operated · Pune, India Deployed in 11 countries

Every telecom number, governed through its complete lifecycle.

XonIPAM manages telecom numbering resources through allocation, assignment, quarantine, release and portability workflows — with controlled history, approvals and APIs.


Lifecycle statesGoverned transitions, full history
AVAILABLE RESERVED ASSIGNED QUARANTINE RELEASED

Number ranges and individual numbers

Manage ranges and the numbers inside them as real, materialised, audited objects — mobile, landline and toll-free — at the scale of large operator inventories.

E.164 hierarchy

Numbers organise under an E.164-aligned hierarchy where applicable, with exchange-prefix associations and numbering-plan structure preserved rather than flattened into a spreadsheet.

Number categories

Programmable categorisation — premium, standard, regional, service-class — drives assignment rules, quarantine windows and reporting segmentation.

Customer and service binding

Assignment binds a number to a customer and service context, so the inventory answers who holds what, since when, and under which order — not just what is free.

Bulk assignment and release

Bulk operations for range delegation, mass assignment and coordinated release, with the same governance path as individual operations.

Cooling and quarantine periods

Configurable quarantine windows per category and region hold released numbers out of circulation, with automatic release back to available stock when the window lapses.

Portability workflows

Inbound and outbound portability workflows carry a number through eligibility, scheduling and activation states with full history. We do not claim national numbering authority integration or portability clearing-house connectivity.

Approval and audit

Sensitive transitions pass approval gates; every state change lands in append-only history — the audit surface regulators and enterprise customers expect.

Capacity and utilisation

Utilisation and exhaustion visibility per category and region, so numbering capacity planning runs on data rather than tribal knowledge.

APIs and reporting

REST APIs expose inventory, assignment and lifecycle operations for OSS/BSS integration, with exportable reporting for regulatory and internal review.

See it running on your own numbers.

Book a technical walkthrough