Is MYLO a PBX, an AI Telephony Agent or a Complete Appliance?

Asterisk is the PBX engine that executes trunks, endpoints, dialplan, media and live calls. MYLO is the guided management and AI-assisted control layer around that engine, delivered with prepared local hardware and browser access. The appliance combines these layers but does not erase their boundaries. The value comes from the layers working together while each retains a clear responsibility. This makes changes explainable, reviewable and recoverable rather than dependent on an opaque model response.

Asterisk role

Asterisk is the PBX engine that executes trunks, endpoints, dialplan, media and live calls. MYLO is the guided management and AI-assisted control layer around that engine, delivered with prepared local hardware and browser access. The appliance combines these layers but does not erase their boundaries. Operators should confirm this boundary through current evidence and avoid assumptions inherited from old documentation.

MYLO role

MYLO presents relevant evidence in business language while preserving permission and approval controls.

Hardware role

The proposed operation names its scope, protected inputs, dependencies and expected result before execution.

Browser experience

Deterministic checks make the behaviour repeatable, auditable and safe to stop when evidence disagrees.

Complete package

Completion requires verification against the running system, not merely a successful save message.

From Request to Controlled Operation

1. An authorised person states the desired business outcome.
2. AI assistance interprets language, retrieves relevant approved knowledge and asks for missing information.
3. Deterministic code observes current authoritative state and validates values, permission and scope.
4. MYLO presents a structured proposal showing intended differences and protected values.
5. A responsible administrator approves when the effect is consequential.
6. Deterministic services create required backups, apply the bounded operation and reload safely.
7. MYLO verifies configuration and live evidence, records the result and offers a defined recovery path.

Limits and Operating Checklist

• Does each fact come from its authoritative source?
• Is the requested outcome and exact scope clear?
• Are permission, provider and product boundaries explicit?
• Does the proposal show meaningful before-and-after differences?
• Has the responsible person approved consequential effects?
• Is there a scoped snapshot and manifest before mutation?
• Did deterministic validation and execution complete?
• Was the real customer outcome verified?
• Can failure be explained and restored without inventing state?

Three Views of the Same Product

The PBX view explains call execution: Asterisk owns trunks, extensions, dialplan, IVRs, routes and live channels. The AI-agent view explains interaction: MYLO interprets ordinary business language, identifies missing facts and prepares a controlled proposal. The appliance view explains delivery: prepared hardware, Linux, application services and a supported local operating boundary arrive together.

None of those labels should erase the others. Calling MYLO only a PBX hides guided configuration; calling it only AI suggests the model places calls directly; calling it only hardware hides the operating layer. For the broader distinction, compare the telephony-appliance definition with MYLO versus MyLineHub open source.

Use the Correct Authority During a Fault

If a route is wrong, inspect Asterisk. If an address or route is wrong, inspect Linux. If an approval or campaign record is wrong, inspect MYLO application state. AI can explain the evidence but cannot replace it. This division is what makes the product understandable and recoverable.