- How do I install franzose/laravel-smpp in a Laravel app?
- Install it with Composer using composer require franzose/laravel-smpp, then follow the package's service provider and configuration publishing steps. Verify the version constraint against your Laravel and PHP versions before installing. After publishing config, add your SMPP host, port, credentials, and bind settings, then test against a staging SMSC before sending production SMS.
- Does franzose/laravel-smpp support Laravel 11?
- Version 1.5 is a compatibility release that adds Laravel 11 support via PR #20. That makes it the version to evaluate for Laravel 11 projects, but you should confirm PHP constraints and CI coverage before upgrading. Treat it as a dependency compatibility update, not a new SMS feature release.
- What PHP version do I need for franzose/laravel-smpp v1.5?
- Laravel 11 typically aligns with PHP 8.2 or newer, so validate that your application and the package's Composer constraints resolve on PHP 8.2+. The release notes are sparse, so check composer.json and run a dependency resolution in a branch. If you are on older PHP versions, upgrade Laravel and PHP first or pin a package version that supports your stack.
- Is there a Laravel notification channel for SMPP in this package?
- The overview describes a lower-level SMPP sending package, and the assessment notes it may not expose a Laravel notification channel. Check the package source and README for a NotificationChannel class or documented notification usage. If none exists, wrap the SMPP client in your own notification channel or service class.
- Can I send SMS through Laravel queues with franzose/laravel-smpp?
- The package fits queue/worker-based sending patterns, but the sparse release notes do not explicitly confirm a built-in queue API. You can typically dispatch a job that calls the SMPP client from a long-running worker. Validate connection handling, retries, and duplicate-send safeguards before scaling worker concurrency.
- Does franzose/laravel-smpp support delivery receipts (DLRs)?
- The provided overview and changelog do not confirm delivery receipt support, so do not assume DLRs are handled out of the box. Review the package source and provider documentation for DLR correlation and storage options. If DLRs are required, test the full submit-and-receipt path against your SMSC before production use.
- How do I configure SMPP credentials and provider settings?
- Configuration is expected to follow standard Laravel package patterns: publish the config file and set SMPP host, port, system ID, password, bind type, and provider-specific options. Confirm the exact keys in the package config because provider settings vary. Keep credentials out of version control and validate bind/submit behavior in staging first.
- What are the risks of using franzose/laravel-smpp in production?
- Production risks include unverified Laravel 11 test coverage, provider-specific SMPP behavior, persistent connection handling, throttling, reconnect/retry, encoding, and lost or uncorrelated DLRs. Plan for observability, dead-letter queues, idempotency, and duplicate-send safeguards. Canary a low-volume SMS route and keep an exit path to a managed SMS provider.
- What alternatives to franzose/laravel-smpp should I consider?
- If you prefer HTTP APIs or managed messaging vendors, alternatives include Laravel notification channels backed by HTTP SMS providers or managed SMPP gateways. Choose franzose/laravel-smpp when you specifically need direct SMPP connectivity and can operate queue workers. Compare support SLAs, DLR handling, and operational burden before committing.
- Is franzose/laravel-smpp actively maintained and safe for long-term use?
- It is community-maintained open source with a small contributor base, and v1.5 mainly reduces Laravel 11 compatibility risk rather than changing ownership. Track upstream releases and Composer constraints, and expect community support rather than a vendor SLA. Retain an exit path to a managed SMS provider if maintenance stalls.