Documentation ↓
On this page
Guide · SMSFLARE 7.0.0
Version scope & known limitations
What this documentation verifies, plus practical implementation limits.
Documentation baseline#
These guides describe the SMSFlare source and demo reviewed on 28 October 2026. Screenshots are captured from demo.smsflare.net and show fictional sample records. Public website content, guide text, search and images are maintained in files; the help centre does not query a database.
Included capabilities#
- Dashboard as the operational start page, daily SMS/Voice metrics, optional refresh and account-scoped views.
- CDRs replaces the menu label Logs; existing report and guide URLs are preserved.
- Unified SMS/SMPP and explicit Voice delivery channels.
- MySQL-only configuration, reporting, message events, durable Voice jobs and DLR queues.
- Compact configurable tables and scrollable dialogs with pinned actions.
- Client message transformations, URL-removal windows, generated-URL Unicode and no-URL-only templates.
- Reference-aligned single/CSV test options and a saved-destination address book.
- SIP/UDP Voice, static IVR, Google TTS, flash calls and gateway statistics.
Current limitations#
| Area | Current boundary |
|---|---|
| Voice transport | SIP/UDP runtime; TCP/TLS selections are not implemented transports |
| SIP authentication | Digest challenge retry is not implemented |
| Recording | Route metadata exists, recording adapter disabled |
| TTS | Google adapter; additional vendors and runtime audio cache not implemented |
| Voice billing | Existing SMS tariff/part model; no separate duration-based unit |
| Cross-channel fallback | Application/client selection; no implied automatic SMS-group-to-Voice failover |
| URL/template counters | In memory; restart resets state, processes keep independent counters |
| Public demo | Sample gateways disabled; test sending requires the configured test client and route |
Maintaining accuracy#
Update the guide and screenshots when the implementation changes. Keep English and Polish versions synchronized. Regenerate the committed documentation data and run the documentation checks before publishing the website.
Screenshots show fictional data from the public demo. Your instance may have different records and permissions.