Knogin
[Geodaten]

PSAP Phone Number Allocation & DID Routing

The Phone Number Allocation module manages the lifecycle of Direct Inward Dialling (DID) phone numbers across the platform's telephony subsystems.

Modulmetadaten

The Phone Number Allocation module manages the lifecycle of Direct Inward Dialling (DID) phone numbers across the platform's telephony subsystems.

Zurück zur Liste

Quellreferenz

content/modules/psap-phone-allocation-did.md

Letzte Aktualisierung

2. Apr. 2026

Kategorie

Geodaten

Inhaltsprufsumme

7cda8274292b234e

Tags

geospatialai

Gerenderte Dokumentation

Diese Seite rendert das Markdown und Mermaid des Moduls direkt aus der offentlichen Dokumentationsquelle.

Overview#

The Phone Number Allocation module manages the lifecycle of Direct Inward Dialling (DID) phone numbers across the platform's telephony subsystems. It provides a centralised inventory of available phone numbers, handles allocation to tenants and subsystems, supports number remapping between subsystems, and maintains routing configuration that determines how inbound calls are handled. The module ensures that each tenant's phone numbers are isolated and that cross-tenant number access is prevented at the database level.

Key Features#

  • DID Inventory Management - Maintain a pool of available phone numbers with metadata including provider, region, country code, status (available, allocated, reserved), monthly cost, and reservation details. Query available numbers by region and country code for provisioning.

  • Tenant-Scoped Allocation - Allocate phone numbers to specific tenants and subsystems (PSAP, utilities, document telephony, mDOC) with customer labels, dashboard identifiers, and organisation scoping. Allocation records include auto-provisioning flags and timestamps for operational tracking.

  • Subsystem Routing - Each allocated number carries routing configuration that determines which subsystem handles inbound calls, which dashboard displays the call, and what customer label is used in greetings. The routing table supports multiple subsystems per tenant with independent number pools.

  • Number Remapping - Remap an allocated number from one subsystem to another within the same tenant without releasing and re-allocating. This enables operational flexibility when reorganising call routing or migrating between subsystems.

  • Number Release - Release allocated numbers back to the available pool when they are no longer needed, clearing routing configuration and tenant association while preserving the number in inventory.

  • Cross-Tenant Protection - Database-level constraints ensure that number allocation, remapping, and release operations can only affect numbers belonging to the requesting tenant. Cross-tenant number access is structurally prevented.

  • Subsystem-Aware Greetings - The routing configuration drives greeting selection for inbound calls: PSAP lines use country-specific emergency number greetings (911, 112, 119), while non-PSAP lines use the customer label from the DID routing record.

Use Cases#

  • PSAP Line Provisioning - Allocate emergency phone numbers to a PSAP tenant, configure routing to the PSAP subsystem, and associate numbers with specific dispatch dashboards for call display.
  • Multi-Subsystem Tenants - Organisations operating both PSAP and non-emergency telephony allocate separate number pools for each subsystem, with independent routing and greeting configuration.
  • Number Migration - Remap phone numbers between subsystems during operational reorganisation without disrupting the number's external-facing identity or requiring new number provisioning.
  • Regional Deployment - Query available numbers by region and country code to provision locally appropriate phone numbers for geographically distributed operations.

Integration#

The Phone Number Allocation module connects to the IVR routing system for inbound call handling, the voice AI session manager for provider selection and greeting injection, and the tenant administration interface for number management. Allocation and routing records are used by the session prewarming system to determine provider configuration before calls connect.

Last Reviewed: 2026-04-02