Weave Code
Gammu Laravel Package
laravel-notification-channels/gammu
A Laravel notification channel for sending SMS messages through Gammu, the open-source SMS gateway. Integrate Gammu into your Laravel app and deliver notifications as text messages using Laravel’s familiar notification API.
Gammu Notifications Driver
Frequently asked questions about Gammu
- What is laravel-notification-channels/gammu used for?
- It is a Laravel notification channel that sends SMS notifications through Gammu, the open-source SMS gateway. You integrate it via Laravel's notification API and deliver messages using a Gammu-compatible GSM modem on a Linux host. It is best suited to low-volume internal or air-gapped alerts rather than strategic customer messaging.
- Does laravel-notification-channels/gammu support Laravel 10 or Laravel 11?
- No, based on the package history it was built for Laravel 5.3-era applications and the last release was in December 2016. Modern Laravel and PHP versions are not assumed to work without a fork or port. You should verify Composer constraints and be prepared to update the channel contract.
- How do I install and configure this Gammu notification channel?
- You would normally require the package via Composer and configure a notification channel class plus Gammu connection details. However, because the package is unmaintained and tied to older Laravel versions, installation in a modern app will likely fail or need a fork. Validate a manual Gammu send first on the target Linux host before attempting the Laravel integration.
- What hardware and OS requirements does Gammu SMS sending need in Laravel?
- You need a Linux host with a Gammu-compatible GSM modem, an active SIM, and the Gammu CLI or service installed and working. The Laravel app must be able to access the device, which is difficult in containers, serverless, or multi-tenant cloud environments. Plan for device passthrough or an internal sidecar gateway if you cannot run on bare metal.
- Is laravel-notification-channels/gammu maintained or safe for production?
- It has no apparent upstream maintenance, with its last release in 2016 and no dependents listed. That means no security updates, outdated Composer constraints, and unclear queue, retry, and delivery-receipt behavior. Treat it as high risk and do not adopt it unmodified as a long-term production dependency.
- Can I use this package in a containerized or Kubernetes Laravel deployment?
- Probably not directly, because Gammu needs reliable access to a physical GSM modem and SIM. Kubernetes and serverless architectures generally lack stable device access, so the package is a poor fit. A better pattern is to expose Gammu as an internal SMS gateway service and call it from Laravel.
- How should I handle queueing, retries, and delivery receipts with Gammu in Laravel?
- The package itself does not clearly document robust queueing, retry, idempotency, or delivery-receipt behavior. You should wrap sends in Laravel queues, add retry and dead-letter handling, and log modem responses. Test duplicate and lost message scenarios, and confirm whether your Gammu setup can return delivery receipts.
- What are alternatives to using this package for SMS notifications in Laravel?
- For most applications, a managed SMS provider with an actively maintained Laravel notification channel is a better fit than on-prem Gammu hardware. If you must use Gammu, treat this package as a reference implementation and build a thin adapter behind your own SmsSender interface. You can also run Gammu as a separate internal gateway service and call it over HTTP or a queue.
- How do I migrate a Laravel 5.3 app away from laravel-notification-channels/gammu?
- First isolate SMS sends behind an internal SmsSender interface so the rest of the app does not depend on the package directly. Then either fork and port the channel to the current Laravel NotificationChannel contract or replace it with a managed provider adapter. Validate behavior with a test SIM and low-volume internal alerts before cutting over.
- What operational risks come with running Gammu SMS notifications on-prem?
- Expect modem offline failures, inactive or out-of-credit SIMs, signal loss, hung Gammu processes, device permissions issues, and host reboots. You also need to manage duplicate or lost messages, missing delivery receipts, and carrier compliance. Budget for health checks, alerting, fallback SMS providers, and internal ownership of hardware and runbooks.
Weaver
How can I help you explore Laravel packages today?