A2billing: How Do We Compare?

By Author: Carl Lewis
Total Articles: 4
Comment this article

We are often asked how DTH VoIP Billing Software compares to a2billing. This question usually comes from customers who are using a2billing but are looking for a more comprehensive alternative, or customers who are starting a new business and are evaluating the different telecom billing systems available.
In this article, we will attempt to highlight the primary differences between a2billing and DTH VoIP.

Architecture

At the architectural level, a2billing is what we would refer to as a bundled system. i.e. the switch and the billing software are on the same server and share resources. This configuration is low-cost but it introduces performance, scalability and security concerns.
Running both your switch and your billing operations on the same server will also introduce performance issues as both systems are competing for the same resources.

As a bundled system, it is limited to the scalability that can be achieved using a single server only.

Having to open billing-related ports (HTTP, HTTPS, etc) on your switch will encourage malicious individuals to ...
... attempt to compromise your server.

The DTH VoIP billing system is what we would refer to as stand-alone. i.e. it is independent of the switch (or switches) and makes use of APIs to integrate with whatever switch or PBX is being used. It runs on its own server(s) and has dedicated resources. Although this scenario has higher start-up cost, it offers greater performance, security, scalability and integration opportunities.

Codebase

A2billing is an open-source project lead by a single individual with code contributed from various programmers.
Our system is a commercial application designed and built by a team of development and support staff. As such, we provide scheduled releases and dedicated support via email, phone, and remote desktop.

Interoperability

Interoperability is another key difference between our systems. A2billing was built specifically for use on Asterisk and currently does not operate with any other switches/PBX systems.

Our system, on the other hand, uses standardized APIs to interface with whatever switch/PBX is required for the deployment in question. This approach affords you the flexibility to use whichever switch (or switches) best suits your needs at given time in your business life cycle; giving you more control over your future growth.

Summary

A2billing may be suitable for sites who intend to use Asterisk and only expect limited growth.

Our solution can work for you at the start of your business and stay with you as you grow to support thousands of concurrent calls per server.
Our system is geared towards deployments that may need to interface with multiple switches and require a higher level of scalability, integration, interoperability and customization.