First activation

Installation makes the module available. Authorised activation gives it a defined service configuration.

Prepare the service

Obtain a token privately from a compatible operator. Confirm the correct PBX identity, endpoint and explicit routing policy. Do not place the token in shell arguments, URLs, tickets or logs. The CLI prompts without displaying it; the administrator interface uses a password field and CSRF protection.

Verified command example

fwconsole domaintains activate
fwconsole domaintains status --json

Sign, validate, apply, verify

The module creates or reuses its persistent signing identity and sends an Ed25519-signed claim over HTTPS. The response must match the local service and pass validation. Authorised configuration is retained as pending before local reconciliation. Only complete local verification allows provisioned status.

Check the result

Assigned incoming numbers initially use DOMAINTAINS Test, which answers with confirmation tones and hangs up. A locally provisioned result does not prove upstream routing, working outbound calls or emergency registration. Those need separate controlled operator checks.

Interpret the result by stage

Interpret the result by stage
Observation	What it establishes	Next action
Unprovisioned	No retained provisioned activation state	Check identity, endpoint, routing policy and operator authority before activating.
Remote activation failure	The new provider response was not accepted	Check the complete HTTPS endpoint, token/service relationship and provider status. Prior known-good local state is retained.
Pending after a local failure	New authorisation exists, but local reconciliation did not complete	Inspect last_error and last_error_stage. Review native objects and ownership evidence before retrying.
Provisioned	The module verified the intended local configuration	Confirm FreePBX reload requirements and separately verify carrier routing, controlled calls and emergency obligations.