Filament Issabel Click To Call Laravel Package

Technical Evaluation

Architecture fit: This package targets Laravel applications that need telephony integration — specifically "click-to-call" originating calls through Asterisk's Manager Interface (AMI). The 1.0.0 scope bundles three concerns into one package: (1) AMI origination logic, (2) a Filament integration surface ("visor con contexto filament-click-to-call"), and (3) a dialplan tag/artifact for deployment. That is a reasonable vertical slice for an ops-adjacent Laravel app, but it means the package straddles application code and telephony infrastructure configuration. The architectural fit is good only if the consuming team already runs Asterisk and accepts a hard dependency on AMI as the control plane.

Integration feasibility: Feasible for Filament-based admin panels, since the UI surface is delivered as a Filament context rather than a bespoke Blade/JS layer. The dialplan "publication tag" implies the package ships or references Asterisk dialplan config that must be installed on the PBX — this is the part most likely to create friction, because it moves deployment beyond composer require into PBX change management.

Technical risk:

• High: AMI is a credentialed, stateful TCP protocol. Credential handling, connection pooling, timeouts, and reconnect behavior are the primary reliability risks; release notes say nothing about these.
• High: Coupling to a specific Filament major version. "Contexto filament-click-to-call" suggests a Filament panel/plugin registration; Filament has had breaking changes across v3/v4, so version constraints matter a lot.
• Medium: The dialplan tag is effectively infrastructure-as-code with no versioning story described. Drift between package version and deployed dialplan is a silent-failure risk.
• Medium: A first stable release with no prior assessment and no changelog history means we have no signal on API stability or prior breaking changes.

Key questions:

1. Which Filament major version(s) are supported, and is the Filament dependency optional?
2. Which Asterisk versions are validated (AMI action sets differ; Originate semantics and event handling vary)?
3. How are AMI credentials supplied — config, env, secrets manager — and are they encrypted/masked in logs?
4. Does the package originate calls synchronously in the request cycle, or queue them? What happens on AMI timeout?
5. What is the "dialplan publication tag" concretely — a generated snippet, a published config file, a versioned tag consumed by CI?
6. Is outbound-only supported, or is there inbound/event handling (channel events, hangup, CDR)?
7. Test coverage and CI: is there an AMI mock/fake for testability?
8. License, maintainer count, and release cadence.

Integration Approach

Stack fit: Suitable for Laravel + Filament monoliths or admin backends where operators need a "call this contact" action, and where an Asterisk estate already exists. Poor fit for greenfield projects without a PBX, for API-only services, and for teams standardizing on a hosted CPaaS (Twilio/Telnyx) rather than self-managed Asterisk.

Migration path: There is no prior assessment and no earlier tracked version, so treat 1.0.0 as a net-new adoption, not an upgrade. Practical path:

1. Prototype in a non-production Laravel app against a lab/test Asterisk instance.
2. Validate Filament panel registration and the click-to-call UX end to end.
3. Manually apply/review the dialplan tag on the lab PBX, then codify it in the PBX config repo.
4. Promote to staging with production-like AMI credentials and network path.

Compatibility: Confirm Laravel and PHP version matrix against our current baseline, plus Filament major. The AMI dependency also implies network egress from the Laravel host to the Asterisk host on port 5038 — verify firewall and that AMI is not exposed publicly. TLS-wrapped AMI is worth checking.

Sequencing:

1. Pin versions and freeze the Filament/Laravel constraint set.
2. Stand up AMI egress and lab PBX; verify a single Originate.
3. Integrate the Filament context in one panel and one user role.
4. Introduce the dialplan tag into PBX config management with a documented rollback.
5. Run a limited pilot with a small operator group before general rollout.

Operational Impact

Maintenance: Two maintenance surfaces, not one — the Composer package and the PBX dialplan artifact. Both need ownership. Filament coupling means the package must track Filament majors; expect periodic upgrade work even without feature needs. A first stable release from an unknown maintainer set warrants watching release cadence and issue responsiveness for a quarter before relying on it.

Support: Telephony failures are user-visible and hard to attribute — is a failed click-to-call a package bug, an AMI credential issue, a network/firewall problem, or a dialplan mismatch? Without clear diagnostics this becomes a three-team triage (app, network, telephony). Ask for structured logging, distinguishable exception types, and a documented troubleshooting guide. Note also that release notes are in Spanish — fine internally if the team is Spanish-speaking, but it signals a small, possibly single-maintainer project with limited English-language community support.

Scaling: AMI is a single control connection to a single Asterisk instance; per-request connections will not scale well horizontally. Under load, concern is connection churn and contention rather than CPU. If click-to-call is a low-frequency operator action (tens per minute, not thousands), scaling risk is low. Also check Asterisk-side concurrency limits — the PBX, not Laravel, is the real capacity ceiling.

Failure modes:

• AMI unreachable / auth failure → click-to-call silently or noisily fails; needs graceful UX degradation.
• Dialplan drift → call originates but routes incorrectly or drops; high-severity, hard to detect.
• Filament upgrade → panel breaks, blocking operators from a feature embedded in their primary tool.
• Credential leakage via logs/config → security incident.
• Timeout without idempotency → duplicate calls placed to customers.

Ramp-up: Low-to-moderate for a Laravel developer (Composer install, Filament plugin registration, config publish). High for the telephony half — someone must understand AMI, dialplan context/extension semantics, and PBX deployment. Budget for a telephony-literate engineer or contractor during pilot; do not assume the Laravel team can own the Asterisk side unaided. Recommend a short internal runbook covering credential rotation, dialplan change procedure, and the failure-triage decision tree before production.