DOMAINTAINS / Open-source software for FreePBX

Telephone numbering.
Properly connected.

Connect an operator-authorised telephone service to the FreePBX configuration it needs. Keep numbering, entitlement and the phone system in a defined relationship.

Try number discovery ↗Explore the product ↗

The relationship / conceptual, not a live service

01 / NUMBER020 7946 0123Synthetic number. No allocation.

02 / OPERATORCustomer + subscriptionOwns commercial entitlement

03 / AUTHORISATIONA defined PBX serviceValidates identity and permission

04 / DOMAINTAINS + FREEPBXConfiguration + evidenceApplies and verifies owned objects

The operator authorises the service. DOMAINTAINS reconciles its owned PBX configuration. Carrier readiness remains separately verified.

The problem is the space between systems.

A number in one system.
A trunk in another.
Who joins up the facts?

An order can be accepted before a PBX is configured. A trunk can exist without authority to change it. A successful API response can arrive before anyone has checked the result.

DOMAINTAINS makes the PBX-side relationship explicit: who authorised the configuration, what the module owns and whether the actual result matches.

The service lifecycle / conceptual illustration

A number. A service.
A verified relationship.

Each transition has an authority. No single component owns the entire telephone service.

Illustrative number / no live operation020 7946 0123Offer observed

Operator / number provider

Availability is not allocation.

A customer finds a number through the operator availability interface. The offer is scoped evidence, not an allocation or a reservation.

Read the implementation guide ↗

Discover: Offer observed. A customer finds a number through the operator availability interface. The offer is scoped evidence, not an allocation or a reservation. Availability is not allocation.

Assign: Service relationship verified. The operator verifies the actual order, customer entitlement and number assignment. Allocation and activation must be confirmed by its real provider integration. An accepted order is not proof of carrier readiness.

Authorise: PBX entitlement validated. The PBX signs a fresh activation claim. The provider checks current entitlement and returns configuration authorised for that PBX service. Installing a module does not authorise a service.

Apply: Local state pending. Validated authorisation is retained as pending. DOMAINTAINS applies only permitted changes, with ownership and fingerprint checks protecting existing objects. An attempted write is not a verified result.

Verify: Locally provisioned. The resulting native configuration is inspected before provisioned status is recorded. Carrier routing, live calls and emergency confirmation need separate verification. Local success is not a call test.

Maintain: Refresh and reconcile. Activate with retained authorisation obtains a fresh provider response. Matching owned configuration can be reconciled; unexpected administrator changes fail closed. Drift is a conflict, not permission to overwrite.

Unlink: Local authorisation removed. Confirmed Deactivate removes retained activation authorisation. Identity, endpoint, ownership and existing PBX configuration remain. The operator handles upstream withdrawal separately. Local unlink is not cancellation or teardown.

Number discovery / genuine engine, synthetic inventory

Some numbers
just fit.

A familiar pattern. A memorable ending. Three independent searches that widen your choices, without counting the area code as a match.

Find your pattern

1 122 233 123

020 / LONDON7946 0123

One number. Three matching patterns.

The actual software

Your phone system.
Not a blank canvas.

The FreePBX module receives validated service configuration and applies it through FreePBX APIs. It verifies native objects, records ownership and refuses unexpected conflicts.

Explore ownership protection

May manage its own: Inbound and outbound SIP trunks; Exact-DID inbound routes; Applicable outbound routing; Authorised trunk channel limits
Does not silently take over: Unrelated PBX configuration; Administrator changes to owned objects; FreePBX Firewall rules; Carrier or billing authority

Your numbers. Your phone systems. Your choice.

Build on infrastructure you control.

For operators: connect existing customer, subscription, numbering and SIP systems through public contracts. Keep your commercial platform your own.

For operators

Choose an integrated service relationship.

For businesses: explore the intended FreePBX UK experience, including compatible hosting and operator integration, with current availability and terms to be confirmed.

Integrated-service option

Inspect the implementation

The detail is
part of the product.

Start with the practical guides. Follow the contracts into the source. Assess the current milestone against your own operational requirements.

Telephone numbering.Properly connected.

A number in one system.A trunk in another.Who joins up the facts?