The product / 01
A defined place in your phone system.
DOMAINTAINS connects a compatible operator service to the configuration it is authorised to manage on FreePBX. Nothing more by assumption. Nothing less by accident.
Your PBX stays yours.
Your operator defines the service.
DOMAINTAINS maintains the connection.
Activate with authority.
A persistent PBX signing identity and a compatible HTTPS provisioning endpoint establish the activation request. The operator authorises the service; the module validates and applies only the returned configuration.
Explore service activationProtect what is already there.
Native object identities and fingerprints distinguish managed configuration from unrelated trunks and routes. Exactly matching objects can be reused without silently becoming owned.
Understand configuration ownershipVerify, then report success.
Reconciliation does not mean unrestricted repair. Unexpected drift stops the operation. Verified pending evidence can support recovery after interruption, while uncertain states remain visible for review.
See recovery and reconciliationKeep number relationships explicit.
Numbers come from provider-authorised service entitlements. Initial exact-DID routes use DOMAINTAINS Test. Number allocation, commercial service status and emergency confirmation remain separate responsibilities.
Follow the number relationshipConnect your own infrastructure.
Open extension contracts let an operator integrate ordering, numbering, provisioning and billing independently. The public examples demonstrate the flow with synthetic data; real adapters and live acceptance are still required.
Bring your own telecomsConfirm emergency registration separately.
The operator-side reference requires current individual-number authority and explicit accuracy confirmation. An accepted submission is not registered status, and the module does not automatically change Emergency Caller IDs.
Understand emergency responsibilitiesConfiguration protection / four cases
A matching name
is not permission.
What matters is verified ownership and the actual configuration, not whether an object looks familiar.
Manage after verification
Ownership is recorded only after creation has been verified. Later changes require the current object to match the recorded evidence and the new configuration to remain provider-authorised.