From HiPBX Wiki

This is a non-comprehensive list of changes to be done to FreePBX, in no particular order

• Replace MySQL with SQLite, if feasable
  • Have decided against that. Keeping it with MySQL actually INCREASES the reliability, by being able to have a MySQL cluster service, too.
• Replace internal ASTDB with MySQL SQLite (or MySQL/Drizzle if SQLite isn't going to happen)
  • ASTDB actually causes a significant bottleneck in big Asterisk systems. Moving it to SQL calls gives a massive improvement.
  • And when I say 'massive improvement', I mean 10,000 transactions takes 7 seconds with ASTDB, and .25 seconds with MySQL.
• Re-organise files so that DRBD can easily replicate them
• GUI for DRBD and HiAv This is going to need some significant, but not major, core code changes. Probably the biggest part of the project.
• SIP Provisioning Module
  • This is actually almost done, based on existing stuff. But I want to make it BETTER, eg, scan the phones MAC barcode into a web form, and it knows what sort of phone it is by the MAC address, and can do smart stuff from that, like configure up a DHCP server that allocates IP addresses and does config generation
• Astribank Management UI
  • Astribanks are awesome, but they're a prick to configure for those that aren't familiar with them. I want to fix that. And, they are the only Austel Certified hi-av channel bank, which does limit the range of choices 8)
• Zaptel Provisioning Module Ties into the Astribank management
• New module for 'Immediate Answer' (prereq is 'Provisioning', so Asterisk knows what sort of phone it's ringing) This is the Paging Module on Steroids, basically. The current Paging module does everything we need. I was thinking about an 'Emergency Page' system, but, it can already do that!
• We-write the installer (possibly based on the PIAF installer, but with a bit more smarts)
• Replace PHP::Pear with PDO
  • PHP::Pear is depreciated and a pain, and PDO is the new PHP standard, and should be pretty stable for the next 5 or so years.