A telephone number connects several facts: who may use it, which service supplies it, where the carrier sends it and how the PBX handles the incoming call.
The service lifecycle / conceptual illustration
A number. A service. A verified relationship.
Each transition has an authority. No single component owns the entire telephone service.
Illustrative number / no live operation020 7946 0123Offer observed
Operator / number provider
Availability is not allocation.
A customer finds a number through the operator availability interface. The offer is scoped evidence, not an allocation or a reservation.
One customer has several voice-service entitlements
The BYOT reference can aggregate distinct authorised voice services for a linked PBX. It deduplicates numbers and avoids counting repeated service IDs twice. Emergency authority remains per-number; moving one assignment does not move every number in the bundle.
01
An authorised number list
The module receives provider-authorised numbers and creates exact-DID inbound routes within its ownership safeguards. The provider, not the browser or the module, is responsible for the allocation and entitlement behind that list. A displayed search offer is neither an assignment nor a reservation.
02
BYOT service linking
The reference links one DOMAINTAINS product to one PBX and can aggregate distinct voice-service entitlements. Number lists are deduplicated and repeated service identities do not add channel entitlement twice. Foreign, inactive and conflicting relationships are rejected.
03
Per-number emergency authority
Emergency authority is resolved for each individual number against current customer, service and PBX assignments. Moving one number does not move its siblings. Old selectors and signed forms must cease to authorise the reassigned number.