A2Billing still runs in 2026. Support is what operators are missing

Operators run A2Billing on live traffic. ICT Innovations, in a June 2026 roundup of open-source VoIP billing, wrote that the project “still works and remains in production at many providers,” then pointed new Asterisk work at MagnusBilling. The code did not disappear. The people who used to catch you when a rate import broke, or when a hired fixer stopped answering, moved on.

Kolmisoft published the first version of this page in January 2022, after operators asked what to do once Star2Billing declined A2Billing help. Star2Billing’s current public product is DialerAI, a predictive dialer and voice-broadcasting stack. The old A2Billing support page lists paid help. News on that page stops around 2017, and the copyright line reads 2004-2012. Independent 2026 guides treat A2Billing as the legacy Asterisk calling-card option.

If the box is quiet, you know the cost of a migration. The next trigger is an outage, an Asterisk upgrade, or a reseller who wants invoices that are not a weekend of PHP.

What changed since 2022

In 2022 the query was “A2Billing is no longer supported.” In 2026 it is “A2Billing alternative,” and the first answers are open-source roundups. ICT Innovations ranks CGRateS and ASTPP as the strong fully-open options, puts A2Billing in an “aging” column, and names MagnusBilling as the maintained Asterisk biller. MagnusBilling’s site now ships an installer for Asterisk 20, PJSIP, and Debian 13.

ASTPP publishes its own A2Billing comparison and a 2026 “top 10 billing” list to move you onto FreeSWITCH. Treat those pages as a map of the market. They are vendor content.

The 2022 Kolmisoft article listed failure modes operators described to us: invoices built by hand, buy and sell rates in one tariff, missing destination reports, failover LCR that did not fail over, and a PHP stack that struggled around 100 concurrent calls. That was operator mail, not a lab test. If your install is past that load and the box is fine, you are the exception the 2022 piece named.

Three exits, if you decide to leave

Match the exit to the engine you want to keep. Picking a biller and then ripping out the PBX is a second project.

CGRateS is a fourth path if you have developers and you want a charging engine rather than an admin panel. ICT Innovations says that out loud. Most A2Billing operators who wrote to us in 2022 wanted a GUI, invoices, and someone to call. CGRateS is a different job.

Keep the PBX. Move the billing

A2Billing was the AGI bolted onto FreePBX: custom destinations a2billing-did and a2billing-out, inbound routes pointing at those contexts, cron jobs for invoices. PowerPBX documents that pattern. After support dried up, the usual move was to replace the whole box.

MOR is Kolmisoft’s Class 5 softswitch with billing, routing, rating, and reporting in the same product. On the wiki, the PBX registers (or IPs) to MOR as a trunk, and MOR bills each phone by CallerID using virtual devices. We published the same pattern as public how-tos for 3CX outgoing calls and VitalPBX inbound DIDs plus outbound billing. FreePBX sits in the same SIP family. The wiki page Cannot make calls from FreePBX is the register-string version of that trunk.

In 2022 a reader named Mahoney asked, on the original A2Billing post, whether they could keep FreePBX and attach Kolmisoft for “customer gui billing.” Vilius’s answer was yes, via PBX connection to MOR. That answer holds.

Our top PBX platforms list names FreePBX as a common operator choice and notes that MOR’s own PBX Functions addon is optional: many providers keep a third-party PBX and use MOR for the money.

The case for staying

All three have to be true. You have someone who can read Asterisk and PHP. The concurrent-call load is modest. You have accepted that the next serious bug is yours to own, or MagnusBilling is the upgrade path you planned.

Open source is not free once you count the nights. ICT Innovations says the same in its FAQ: you still pay for the server, your time, and any development you hire. MagnusBilling is the cleaner Asterisk stay-put move in 2026. ASTPP is the cleaner move if you were going to leave Asterisk anyway.

Confirm who picks up the phone this year. A 2012 support page with a sales@ address is not that confirmation.

Honest limits

This page has no count of A2Billing shops that moved to MOR, and no reprint of ASTPP’s operator-count marketing. MagnusBilling and ASTPP run real ITSPs. ICT Innovations documents both as current options. If A2Billing is the thing that bills your customers today, and you need a supported Class 5 that can sit behind the PBX you trained staff on, MOR is the product we sell, and the interconnection is documented.

M4 exists for higher-volume Class 4 work. If you need transit and interconnect, start the conversation on M4, not MOR. Reseller layers, recordings, and PBX features are MOR-side in Kolmisoft’s own product split.

FAQ

Does A2Billing still work in 2026?

Yes. ICT Innovations lists it as a production option for legacy Asterisk calling-card work. Active development has slowed. New Asterisk billing projects in that roundup go to MagnusBilling.

Can I keep FreePBX if I leave A2Billing?

Yes. Treat FreePBX as the PBX and put rating, balances, and invoices on a biller that speaks SIP. MOR’s wiki covers FreePBX registration and generic PBX trunks with ANI.

Is this an ASTPP attack piece?

No. ASTPP is the loudest 2026 open-source alternative, built on FreeSWITCH. Use it if that engine is the plan. This article is an A2Billing exit note, not a clone of an ASTPP comparison page.

If you want to see the PBX-plus-billing setup

Walk the wiki page PBX connection to MOR, then pick the public guide that matches the PBX you run: 3CX or VitalPBX. If you want a Kolmisoft engineer on the call while you register the first trunk, ask for a walkthrough.