About the ASTBILL Solution

From AstBillWiki

• AstBill: Design Principles
• AstBill: Functional Goals and Objectives
• AstBill: Architecture
• AstBill: Roadmap and Status

AstBill and Asterisk Capacity

We've been doing some benchmark experiments on a 3Ghz box with 1GB of ram and one traditional IDE disks. we can add to that 4000 registered SIP peers and IAX2 peers - total of about 100 registration refreshes per second. That pretty much fills up CPU. Audio quality is still perfectly fine.. Load average for the whole mix sits between 5 and 10. About 550Kb/s out and 400Kb/s out on the Ethernet for the registration traffic. Minimal media processing on the server.

I you are mixing IAX and SIP traffic you have to process media (voice) on the server and your capacity go down.

Be careful about doing media processing on the server. It kills your capacity. It is so hard to give clear advice as all setups are different. I do think that if you have 7,000 clients you be better off with two servers. This also provide some redundancy in case of HW failure. The downside is that it is much harder to manage two servers. A customer in Australia have 7500 clients and 11 asterisk servers. But they are also utilising access to local low cost calls in each state. That generates a different scenario.