Author: Jim Machi – VP of Marketing, Sangoma
Yesterday, I wrote a blog called “Is it Possible to Outgrow an Open Source PBX?”. The blog was misconstrued with regards to how I stated the premise of situations that may call for someone to move to a commercially supported PBX. It was insensitive to our open source community and the great work they do. If I offended anyone, I am sorry. Yesterday’s blog post does not represent any change in Sangoma’s commitment to our open source projects or the ecosystems around them. Open source projects continue to play a vital role within our business, and we are thankful for all those who choose to be a part of the broader open source telephony ecosystem.
Let me try to state the premise I was trying to convey in yesterday’s blog post in a different fashion.
It’s easy to get started with building a PBX with Asterisk or FreePBX. That’s why they have been so successful – they’re great platforms and they’re easy to use. One downside, however, is that building your own PBX puts the burden of updates (to the underlying operating system as well as telephony platform) on you if you are managing the system yourself, or on someone else if you outsource that work. Unlike most phone systems of the 20th century, a modern PBX is just another type of computer server and needs to be updated and maintained just like any other server.
So what are your options when it comes to maintenance? If you’re not comfortable doing the maintenance yourself, you could go to an integrator who specializes in support of open source telephony platforms. (Luckily, you’re not locked into just one vendor for help!) Another option is to use a turn-key solution or hosted solution that minimizes the amount of maintenance you need to do. That’s all I was trying to say – there are options to reducing your maintenance burden.