Bring your own telecoms / 05
Bring the network you know.
Use your own numbering, service authority, provisioning and SIP infrastructure. DOMAINTAINS supplies a public PBX-side contract and an independent provider reference to build against.
Prepare the service
Verify customer, PBX and voice-service relationships in your authoritative systems.
Connect your adapters
Numbering, authenticated reachability, optional DNS and independent inbound and outbound edges remain replaceable.
Authorise the PBX
Issue the credential privately after prerequisites verify. The PBX activates against your compatible HTTPS endpoint.
Verify the result
Inspect actual infrastructure and local configuration. Prove live calls separately.
More than a single endpoint.
The standalone provider reference covers order preparation, customer linking, aggregated entitlements, expiring hashed credentials, replay protection and per-service orchestration. Its default infrastructure is simulated, not a commercial telephone network.
Read the BYOT architectureKeep your operational responsibility.
Real adapters must preserve authoritative account and service checks, key binding, locking, idempotency and ownership. Returning a SIP host does not configure an SBC or authorise traffic. Calling permissions must be explicit at both PBX and edge.
Adapter implementation guideMake recovery a first-class operation.
Preserve provider state and verified operation outcomes. Use audited recovery for partial effects. Revoking provider authority does not deliver a teardown message to an offline PBX, and local Deactivate does not cancel the service.
Recovery boundaries