Mobius Routing Management Web Interface 2.1.0
1. Introduction & Conceptual Overview
1.1 What is Routing Management?
Mobius Routing Management is a modular and stateless telecom configuration system that provides centralized control over routing data for voice, messaging, and signaling traffic. It enables operators, integrators, and backend systems to create, manage, and resolve virtual networks, number ranges, and ported numbers through both a web interface and a REST API.
At its core, Routing Management is designed to act as a configurable decision engine for mapping incoming MSISDN (phone number) queries to logical routing destinations — whether those routes depend on prefixes, number portability databases, or custom virtual network configurations.
1.2 Core Use Cases
Routing Management supports a wide range of operational and integration scenarios:
|
Use Case |
Description |
|
Prefix-based routing |
Matches input numbers against defined ranges (e.g., +38067 → Network A) for routing decisions. |
|
Number portability (MNP) override |
Overrides default routing for specific numbers (e.g., +380671234567 → Network B) when ported. |
|
Network segmentation |
Creates logical partitions (Virtual Networks) for separating traffic per operator, service, region, or use case. |
|
API-driven configuration |
Allows external systems (e.g., SIP routers, Diameter nodes, service orchestrators) to manage routing data programmatically. |
|
Cluster-wide control |
Centralizes routing logic across distributed systems, ensuring unified behavior and reducing inconsistent local configurations. |
1.3 Key Benefits
Multiple application instances can operate concurrently with no inter-dependencies, enabled by shared database storage and local caching.
The platform is not bound to any specific signaling protocol. It can support SIP, Diameter, SS7, or internal REST-based resolution as long as the lookup key is a number or prefix.
Routing Management focuses on structured, audited, user-driven configuration that can be versioned, replicated, and controlled, unlike hardcoded routing tables or dynamic scripts.
Changes to routing entries are instantly effective without requiring service restarts or re-deployments.
Semaphores, async-safe patterns, and audit logging ensure consistency even under concurrent load or failure conditions.
1.4 Role in the Telecom Stack
Mobius Routing Management is not a signaling engine by itself, but it plays a critical decision-making role in the telecom stack. It acts as an external routing module for elements like SIP, Diameter, SS7 or HLRlookup.
- SIP & ENUM Translation: SIP proxies can call Routing Management to resolve a number to a carrier network or domain.
- Diameter Routing (DRA): Diameter routers can use it to enrich or override destination hosts for requests (e.g., based on User-Name AVP).
- SS7 MAP SRI / PRN: As an internal NPDB system to resolve ported numbers from local configuration instead of querying HLRs or NPDBs live.
- SMS Routing: Can be used by an SMSC or message broker to determine the correct delivery network.
- HLR Lookup fallback: Acts as a cache layer to avoid repeated live lookups for recently resolved numbers.
Start innovating with Mobius
What's next? Let's talk!