So, how do we market the FireBrick SIP features.
My plan is that the base models FB2500 and FB2700 will have a good set of SIP PABX features, but ultimately limits on number of calls and registrations (in the hundreds). This is the code I am working on now.
The fully loaded models will have extra APIs and external RADIUS based authentications, routing decision and accounting. This is coming soon, starting with RADIUS accounting data.
The 6000 model will do the same as the fully loaded, but with lots and lots of calls and registrations aimed at a telco. This is what we will eventually replace the existing A&A VoIP services with.
I will publish specs for the external authentication, routing and accounting information, and also provide free linux based C code for voicemail and call recording systems to work with the system.
Does that make sense?
FireBrick SIP feature plan
Subscribe to: Post Comments (Atom)
Companies bad at banking
I was discussing with a colleague the other day how so many companies are so bad with banking. In some ways we have been lucky, but to be fa...
Broadband services are a wonderful innovation of our time, using multiple frequency bands (hence the name) to carry signals over wires (us...
For many years I used a small stand-alone air-conditioning unit in my study (the box room in the house) and I even had a hole in the wall fo...
It seems there is something of a standard test string for anti virus ( wikipedia has more on this). The idea is that systems that look fo...
Post a Comment
Comments are moderated purely to filter out obvious spam, but it means they may not show immediately.