Submission is not confirmed registration

Emergency registration belongs to operator and carrier infrastructure, not to the FreePBX module.

Read the actual status

The reference normalises unregistered, received, awaiting_validation, submitted, awaiting_acceptance, registered and rejected. Only explicit authoritative provider confirmation can map to registered. An HTTP 200 or 202, upload receipt or successful form submission is not sufficient.

Protect each number

Customer authentication is independent of activation. Every request resolves current customer, service, PBX and number authority. A lease rechecks ownership before and after carrier calls, with authoritative assignment locking or a provider-enforced conditional guarantee across all mutation stages. Adapters without that guarantee must remain disabled.

Confirm and minimise data

Submission requires explicit accuracy confirmation and a fresh signed one-use intent. Addresses and registration mirrors are not persisted by the reference; retrieval and status come from the provider. Unknown or partial mutations require a current-state check, not blind replay. The integration does not change FreePBX Emergency Caller IDs or prove that emergency calls will route correctly.

Enable only after integration

Supply customer authentication, authoritative assignment, provider mapping, private settings and real scoped rate policies. The composition rejects the non-locking LocalBilling fixture as emergency authority. Test carrier confirmation, reassignment, revision conflicts and partial submissions on an authorised staging account.