No need for expensive dedicated hardware or advanced knowledge to set up your own PBX. Starfish PBX is based on open source software and can run on any Linux powered computer.
Starfish PBX captures the power of a full featured phone system into a user interface that everyone can use.
Starfish PBX aims to be an open source alternative to Digium’s Switchvox. The goal is to have a software equivalent to which we can add additional functionality like :
In order to achieve all this, we need you help !
NOTE: Starfish PBX is in a early development stage right and and not suitable for production use but you’re encouraged to download and test it. We’re opened to your suggestions and questions on the forum and on our irc channel (#starfish-pbx on freenode).
It’s a long time since I have not updated starfish but I decided not to give up on it yet. I’ve started by changing from the proprietary license to GPL v2 in the hope that this will bring more developers into the action and why not maybe a company to fund the development.
Stay tuned for more actual changes to come, easy to install iso in coming soon …
As some might noticed already I started migrating all the MySQL specific stuff to more generic queries and started using PDO in order to have support for PostgreSQL and sqlite. I’m not moving away from MySQL as it will be supported also, but since Starfish PBX wants to have a version that will be bundled with hardware we needed to find an alternative to it. I also aim to improve the performance on embedded systems and sqlite will be o good alternative to a heavy database server.
This process may take some time and It’s very boring to code but it’s no use to delay it more. It’s a good chance to go over all the code I wrote so far and fix some of the wrong decisions I made in the past. I’m also adding a database abstraction layer so the interface / backend code to have all the db logic in external functions, this way the code will be easier to maintain.
Something to keep in mind for the next time I code a MySQL powered application: never use camel case naming and always stick to ANSI SQL.