So, as a bit of background, I work for a company which, among other things, is a reseller of VOIP phone systems. Currently in our (small) office (with less than 10 employees), we are using the same Aastra VOIP phones we sell to clients. The problem is that while these work pretty OK for calling thousands of numbers to leave 30 second messages, when they are being used as an everyday office phone system to take incoming calls on the same server as all of our other (heavy) internet traffic...they leave something to be desired.
This morning my boss threw up his hands and decided we're finding a new phone solution for the office. He wanted me to find out if it's possible to use the Aastra phones we've got with traditional phone service (it doesn't appear to be), and in any case find who can offer us the best (by which he means, I am assuming the best value, all other things probably being equal) plan to replace everything with traditional phone service that won't be at the mercy of server traffic and internet instability.
He gave me this task for my "research skills." My research skills are pretty decent for finding information on potential clients and markets, but my knowledge of this stuff is essentially nil. I just spent about two minutes looking at the business services side of AT&T's website, and...well, I think it was about two minutes, I think I briefly lapsed into a catatonic state.
Please help me figure out how to start with this bullshit. To make things worse, he hasn't specifically told me the parameters for our needs (I emailed him and he has yet to respond), but based on the size of the office and what we do with the system we have I am figuring on a maximum of ten actual physical phones and extensions, and perhaps 3 lines. Plus we do occasionally still receive a fax.
Posts
Sorry, perhaps I wasn't clear. We are done using VOIP for the office phone system. Period. Boss wants to go to traditional phone service.
I guess I should also mention we are located in the midwestern US, lest some helpful but misguided person tell me about the attractive packages Deutsche Telekom has to offer or something.
Replace "VOIP" with "traditional phone service" in Darkewolfe's post and follow the rest of his advice.
Well, my boss was apparently wrong, as our tech guy tells me the phones actually already are on a separate connection and apparently they just suck because they suck. :?
The worst is WCI uses VOIP and when they go down you cant even call em to get an ETA on restoration of service.
The "highest value" solution is to buy a traditional phone system (PBX, VM, and handsets) off of Ebay (lots of people moving to VoIP) and do the install yourself or get an independent phone vendor/contractor to do the install and programming. Independents may not want (or have the experience) to deal with the brand you buy and also may not want to lose the markup they'd get from vending you hardware.
You'd then still need dialtone service (and a bucket of minutes) from a voice provider. If you're not sure who to look at as a phone vendor you could just call up business voice service providers (or your ISP) and they'll surely have some mechanism to provide the install capability or give you a referral.
Not sure how cost-conscious your boss is, but before you do all this you may want to look at the VoIP usage from the past couple of months, call up business voice providers, get a rate card from them, and determine what your voice bill is going to look like (add 20% to line rental cost for taxes/fees). That way you can pitch your boss: it's going to cost $N for the pbx/handsets/install, $X monthly recurring line charges, and around $Y monthly recurring for our long distance minutes usage.
That all said, you shouldn't be having this problem. Spotty VoIP due to traffic means you've gear that is not QoS-aware and it isn't prioritizing traffic properly, or maybe QoS tagging at the handset isn't occurring properly, or maybe your handsets are shit or have a crappy codec applied. Either way as a VoIP handset vendor I'd think you'd have the technical resources on hand to fix this. Unless your ISP cannot deliver you service that's good for VoIP (which requires good metric different from bandwidth and latency, like jitter), then you'll need traditional voice lines.
So basically the position we are in is doing research for the purpose of demonstrating that the whole thing is unfeasible and a waste to the bosses who don't understand this and just want their phones to work right 100% of the time, which is of course not going to happen.
What do you mean by "infrastructure?"
Do you mean wiring? Network switches and routers? Internet connection?
I literally came into this thread to say that the majority of the time, problems with VOIP phone systems have nothing to do with the phones or the servers or the software, but rather with the underlying network.
The good news is that these problems are fixable, and usually for less money than a new phone system would cost.
the "no true scotch man" fallacy.
You can share switches with the actual network just fine, as long as your switches configured properly.
Using either QoS, or VLANs, or both is typically all that's needed.
That's a pretty typical configuration IMO because it lets you use phones with two Ethernet ports. One port plugs into the network, then the computer plugs into the phone. The switches can tell which traffic comes from which device and will prioritize it accordingly.
the "no true scotch man" fallacy.
I still hate VoIP.