Search all guides
Documentation / Core Concepts
Reconcile only what is authorised and owned
A refresh is a verified configuration operation, not an unrestricted rewrite of the PBX.
Refresh provider authority
Activate with retained activation authorisation makes a fresh signed request using the same identity. The provider response is validated before local application. Remote failure leaves the last known-good state untouched; local reconciliation failure leaves newly authorised state pending for diagnosis and retry.
Compare before changing
Current owned configuration must match its recorded fingerprint before a provider-authorised change proceeds. Unowned objects cannot be normalised, deleted or recreated. Existing native trunk identities and unrelated configuration are preserved.
Verify after changing
The module verifies the resulting configuration before reporting success. Pending ownership evidence supports recovery from interrupted operations only when the actual state can be matched and recorded safely. A third, unexpected state remains a conflict requiring review.
Provisioning is a sequence of checks
Create is not verify.
Retry is not reset.
Local reconciliation has a controlled success path and an equally important failure path.
- 01 / VALIDATE
Accept authority
Validate the provider response before local application.
Remote failure: retain prior state - 02 / RECORD
Persist pending
Retain newly authorised state before changing FreePBX.
Evidence survives interruption - 03 / COMPARE
Check ownership
Compare native objects with recorded fingerprints.
Unexpected state: stop - 04 / APPLY + INSPECT
Verify the result
Record provisioned only after complete local verification.
Local failure: retain pending
Recover from evidence. Inspect the actual state, repair the prerequisite and retry deliberately. Never erase signing identity, ownership or provider operation records to force success.