What’s wrong with a PBX? With a PBX
I am in control,
I’M the one that administers it,
MY organizations voice mail gets stored on an on-prem server that
I maintain. Not some stupid 'cloud' BS.
Plus VoIP seems like nothing but a rip off. We pay only pay $481/month for a 23 channel PRI and everything else. That the same cost as a whole 12 lines with RingCentral.
My previous boss and I looked at about a dozen different VoIP providers, everything from RingCentral to rinky dink local providers all of them would result in a $2500 - $3000/month voice bill. Sure no or minimal upfront costs, and a ton of features we'd never use, and we'd be so hip and modern because we would be in the 'cloud'. But at 40-50K for a PBX and new end user handsets and with bill of $480/month, after roughly 2.5 years of VoIP we'd be in the hole. I find it very difficult to believe that any enterprise grade solution would come out cheaper than what we pay Charter. My company is a subsidiary of a larger organization with operations in 35 different counties, affordable international calling is a big deal to us. All of the call center type reporting metrics and unified communications that were pushed on us don't mean jack.
A lot of the outfits we talked to had all in pricing which makes no sense for us. There's no point in paying anything more than a dollor or two per month for the phones we have in our lobbies, conference rooms, training rooms and manufacturing plant that are seldom used.
We have 10 long range ruggedized ANALOG cordless phones that have a one mile range that tie into the PBX and have internal twinning enabled. These are issued to shop supervisors and foremen who are not desk jockeys and need to be available in areas of the building where cell phone reception doesn’t exist. None of the companies we talked to, with their fancy hi tech solutions and marketing buzzword speak could give us what I would consider a decent equivalent.
If I wanted to get our voice bill cheaper I could, we probably could get away with a 13 channel PRI.
View attachment 150201