FireFlo SMS/SMPP Gateway

FireFlo uses standard semantic versioning. What matters to you is what a version number promises and what to check before you take one.

What the number means

Change	Means
Major — `1.0.0` → `2.0.0`	A breaking change. Expect to read the notes and to change something.
Minor — `0.7.0` → `0.8.0`	New capability. Existing behaviour is intended to survive, but defaults can move — see below.
Patch — `0.7.3` → `0.7.4`	A fix. The safest kind to take, and usually the reason to take it promptly.

Your release notes accompany each build. They are the authoritative list of what changed; this page is about what to look for in them.

Releases

The current pair is .

Gateway	Control panel	Date	What the release was about
0.11.0	0.11.0.0	2026-09-20	Delivery receipts stop being lost under load, and three webhook defaults move. A receipt’s state is now written once, when the provider accepts the message, instead of at ingress and again on the response — the earlier pair raced at rate and abandoned correlations, so a delivered message could be reported `EXPIRED`. Three changes you may notice before you notice the fix: an endpoint answering `3xx` no longer counts as delivered and is retried like any other failure; webhook targets on private and loopback addresses are refused by default, so a deployment posting receipts to an endpoint on its own network must now allow them explicitly; and the retry ladder is exponential with jitter, so the window a failing endpoint gets stretches from minutes to hours. Also: margin is reported unknown rather than subtracted when a price and a cost are in different currencies, and a vendor removed from a weighted group and later added back returns on an equal footing instead of working off its old position
0.10.0	0.10.0.0	2026-09-11	A reseller can move credit to and from the accounts it holds over the API it already sends with. Three endpoints under `/secure/transfers`, authenticated by the same credentials — no second sign-in, and a transfer is queued and applied on the gateway’s next poll rather than moving money inside the request. Carries a migration: the gateway’s own reservation bookkeeping moves out of the money ledger, which becomes append-only, so take a backup before upgrading — it is forward-only. Two defaults move: a vendor’s retry budget goes from 1 to 3, and routing-group failover begins to fire at all. The SMPP ingress rate limit now binds per account rather than per session
0.9.23	0.9.23.0	2026-09-07	Makes 0.9.22’s blocking usable — take this one if you took 0.9.22 for it. It could not be enabled on an install that already existed, `--dry-run` wrote to the host, and a reboot did not release a ban, which matters because a ban covers every port. New `fireflo-install fail2ban` verb, and a boot-time unit that releases FireFlo’s jails and leaves the host’s own alone
0.9.22	0.9.22.0	2026-09-07	Refused logins are recorded, visible and blockable. Every refused SMPP bind, API password and panel sign-in goes to a file of its own, a new Security page shows them beside who is currently blocked, and `fireflo-install --with-fail2ban` ships the jails — off by default. A security fix rides with it: the REST API read the left-most `X-Forwarded-For` entry, which under the common nginx recipe is whatever the client sent, so a credential’s allowed-ips list could be satisfied with a forged header. See Blocking abusive clients
0.9.21	0.9.21.0	2026-09-07	Stop sending and Hold now act on a listener’s own traffic — on earlier builds both controls paused only the receipts going back to bound customers, and submitted messages kept going out. A suspended listener now accepts and parks; a held one refuses at the door before charging. Stopping a vendor also stops its retries, and vendors gain a Restart. See Controlling a worker
0.9.20	0.9.20.0	2026-09-07	Sustained-throughput work on the receipt store — the ten-minute 3,000 msg/s run now holds flat with a store a third the size — plus refused SMPP binds counted by reason and a lighter postpaid credit poll. A default moved: `smsg.dlr.correlation.days` is now `2` (was `3`); an estate that set the key explicitly is untouched
0.7.4	0.7.4.1	2026-08-20	Three defects on the prepaid credit path
0.7.3	0.7.3.3	2026-08-19	Postpaid accounts, statements and period close
0.7.2	0.7.2.1	2026-08-19	Template placeholders widened to accept names and phrases
0.7.1	0.7.1.1	2026-08-19	Template matching — an approved template was refusing every message
0.7.0	0.7.0.1	2026-08-19	Concatenated messages end to end, and the segment billing defect

This table lists selected releases, not every one. The releases between 0.7.4 and 0.9.23 each shipped with their own notes; ask support@fireflo.au for any of them. 0.7.0 is where this table starts, not where FireFlo starts. Earlier releases exist and are in service; their notes are available from support@fireflo.au. Published history begins here because 0.7.0 opened the line of billing work the product is currently on.

Two things the table will not tell you on its own. The control panel column shows the newest revision for that gateway release. The fourth number is a panel-only revision and moves on its own — 0.7.3 had three of them. Any panel version whose first three numbers match the gateway is a valid pair; the panel checks this at runtime and says so when it does not. Five gateway releases inside two days is not a mistake. 0.7.0 opened a piece of billing work, and each release after it closed something the previous one exposed — a segment billing defect, then the template matching it depended on, then the placeholder grammar, then the postpaid work, then three defects on the credit path. Releases cluster when a seam is being worked; that is what it looks like.

Before you upgrade

The pattern worth internalising: the changes that hurt are the quiet ones. A breaking API change announces itself; a changed default does not.

Read the release notes for changed defaults

A default that moves changes behaviour on every deployment that never set the value — which is most of them. These are the entries to read closely, more than the new features.

Check whether anything moved between ports

Enabling the management port moved /q/metrics from 8080 to 9000. A Prometheus job still pointed at the old one gets 404s rather than failing loudly, so a dashboard reads as a quiet system rather than a broken monitor.

Check whether a database migration is included

Migrations are forward-only. There is no down-migration, so the rollback path is a restore rather than a reverse migration — take the backup before, not after.

Check whether receipt behaviour changed

Receipt semantics have changed twice in ways that were invisible until a customer noticed. level used to always read 2, so ACCEPTD was reported as an outcome; and the User-Agent on webhook calls changed from the JDK default to FireFlo/<version>, which matters to any receiver with an allow-list.

Decide whether a customer notice is needed

If figures a customer can see will change, they need telling before it happens — with the number, the direction and the date. See Customer notices.

Version pairing

The gateway publishes its running version on /ops/health, and the control panel shows both its own and the gateway’s.

A mismatched pair is flagged deliberately. The panel degrades rather than breaking when it talks to an older gateway — a column simply drops out of its queries — but a feature that appears absent because of a version gap looks exactly like a feature that is broken.Check the pair before investigating anything that “should be there and isn’t”.

Reporting problems

Everything goes to support@fireflo.au. What changes is how you frame it:

	Include
A reproducible bug	The version pair, what you did, what happened, and one message serial that shows it
A question or setup help	What you are trying to achieve, not only the error — the answer is often a different approach
Anything security-sensitive	Say so in the subject. Do not attach unredacted logs or configuration to a first mail; we will tell you where to send them

Redact before sharing. Credentials, system IDs, IP addresses, phone numbers and message content all appear in configuration and logs. fireflo redacts what it can; a hand-copied log line is your own responsibility.

Customer notices

When a release changes what a customer sees.

Migrating a deployment

Coming from Jasmin or Kannel.

Start here

The control panel

Install and run

Connections

Routing

Customers and approvals

Billing

Operations

Troubleshooting

Migrating

Project

Versioning and upgrading

What the number means

Releases

Before you upgrade

Version pairing

Reporting problems

Customer notices

Migrating a deployment

​What the number means

​Releases

​Before you upgrade

​Version pairing

​Reporting problems

​Related

Customer notices

Migrating a deployment

What the number means

Releases

Before you upgrade

Version pairing

Reporting problems

Related