Recently, I was faced with our aging legacy digital phone system coming off-lease. Years ago, when it was implemented, we looked at VOIP, but decided that it was too immature at the time. I planned to revisit it again when this system was to be replaced. That time has come and I looked at the major players: Cisco, Avaya, NEC, and Fonality/Trixbox.
After many weeks of evaluation and comparison, I realized they they all provide basically the same functionality. There was no big "killer feature" the differentiated one above the others, so I looked at "openess"and pricing. It seems that the big players like to charge extra for using SIP trunks, presence, and other options of the sort. Some vendors wanted 3 physical appliances or servers. Presence requires a dedicated server? I think that is to push you into spending more and adding more of their hardware into your shop. That's the feeling I got. One of the vendors wanted to charge per SIP trunk added to the system. I had enough of that sort of ridiculousness and looked deeply into the Trixbox/Fonality solution.
Trixbox Pro is basically a customized CentOS Linux 4.4 installation with the Trixbox Pro modules. I simply paid the licensing fees, downloaded the ISO image, burned it to CD, inserted it into my server, and booted from it. It looked like a normal CentOS install and asked for a bit of info such as root password, hostname, IP address, timezone, etc. Easy to follow. Afterwards, the server rebooted and I logged in, activated the server with Fonality, and connected to the management console. To my surprise, the management console is hosted by Fonality and trickles changes down to your server. I wasn't too thrilled with that, but it works. The Community Edition does not work like that. It is all hosted on your end. All clients connect to your local server and remote clients go thru Fonality to connect down to your server, again unlike the Community Edition. It took me about a day to add all 50 of my users and conference bridges. It seems like almost any SIP-compliant handset or softphone will work with it. We are pleased with it so far.
This is what made the decision easy to me:
Cisco Solution: $75,000-$86,000
Avaya Solution: $45,000-$65,000
NEC Solution: $46,000-$64,000
Trixbox Pro Solution: <$18,000
Simply, I got basically the same functionality with MORE flexibility for FAR less money with lifetime updates included. Professional support is only $2,000 per year as well. There really wasn't a decision to make after looking at it from a high-level overview.
I'm in a similar search, looking at some of the same companies. I'm really leaning towards trixbox Pro, because it's price point is obviously much better and I feel like its features are more robust and user friendly.
ReplyDeleteWhat other criteria did you use to make the leap from a digital system to the 'newer' VoIP technology. I guess my main concern is QoS issues.
I'd be very interested to hear more about your selection process and new implementation results.
Thanks for the comment Jeff. I run a Gig access network, with 10GigE for the core. I haven't had to use any QoS yet. It may come, but I am not having any issues thus far. I'm running Juniper EX PoE switches for access and Arista 7120T in the core. It's been pretty good so far, and the Pro support is responsive and worth the money, at least for the first year in my mind. That way you have formal support for any issues you may run into during the early deployment phase. I just simply could not see spending the difference for the other systems where I get basically the same functionality from TrixBox Pro.
ReplyDeleteUpdate: We've seen our last two phone bills drop by ~50% by switching to a SIP trunk provider, even though we doubled the number of lines we previously had.
ReplyDelete