Who here uses VoIP either at home or at work?

[SlowToady]

Wondering who uses VoIP either at home or at work, how many lines/numbers you have, and how many simultaneous calls you make. Also, what internet connection you have to support it.

We're implementing a PBX at work and I'm trying to decide if we should go with an older (rather dated) hardware based PBX using POTS, if I should build a software PBX (Asterisk + Linux), or just switch completely to VoIP using Asterisk + Linux box. Internet connection is 1.5Mb/sec down and 384kbps up, which according to internet tests, wouldn't quite be adequate. The largest line we can get is 3Mb/sec down and 768kbps up.

The beauty of the VoIP software PBX is that we already have CAT-5 running to the wall jacks for the phone, so I could just wire up another patch panel, get a bigger switch, and be underway. The PBX we just bought is extremely complicated to maintain and setup, and using the software PBX with POTS would require an FXO port for every extension. In contrast the IP-PBX would require only another port on the switch.

I'm rambling, but, anyone using VoIP have opinions?

[beepbeep]

My company uses VOIP Lucent/Alcatell PBX. 150 lines, 9 sites, 2Mb lines to small sites, 4Mb to bigger ones. QoS on on all lines. We have leased lines between sites and 50% bandwidth is prioritized for VoIP.

PBX scales up to 5000 lines.

On site, we use DECT radio bases. So VoIP is only between our sites. Actual phones are ordinary cordless DECT's. Works like charm and we are able to place direct calls for zero money to each line in company, regardless of geographical site. All POT calls are routed trough central node, so each call goes trough VoIP and then out on 2+2Mbit digital POT trunk. Savings are significant as we don't need POT trunk on every site and use same leased line for both data and telefone.

Bandwith depends on CODEC. You can count with 40kbit per call, to be on the safe side.

This is a trough-and-trough VoIP PBX, so I don't know how you'll fare with software solution but I hope it'll give you a hint.

[SlowToady]

Thanks for the reply. I only have 11-22 extensions to worry about, and 2 incoming lines, so thankfully I have it a bit easier regarding setup I could get by with the VoIP on the 1.5Mb line, but we also do a bunch of internet stuff, so I think I'd upgrade just for peace of mind and to keep everyone happy. QoS on the network switches should take care of traffic prioritzation.

Everyone says VoIP gives substantial savings, but the DSL line alone is going to run $120/mo with 9 static IPs. Then the per month costs of the VoIP service. I've never paid a phone bill, so I don't know how much that is costing us. I think we're currently paying like $60/mo for the DSL, so the two phone lines would have to cost $60 combined to be even on costs.

I guess it'd be wise to keep a POTS line or two around and forward to VoIP in case the DSL goes down, or the VoIP provider goes down. We'd be using the VoIP for incoming and outgoing calls; we don't have any other locations so that isn't a concern.

It may possibly be more cost effective in the long run to pay $600-$800 to have our hardware PBX installed, but from talking to installers familiar with the unit, it's a complete PITA to do anything with. Even just adding an extension is a headache, and the company that made it doesn't support it anymore and won't go near it.

I dunno..VoIP seems like such an easy, nice solution.

Thanks for your reply.

[Rick Lee]

I have it, but know nothing about it or how it works. All I know is our entire company has 201 area codes, but we're located all over the US. When I leave voicemails and give my phone number, I always have to repeat the 201, since Wash. DC is 202. People probably try to call me back and dial 202 and never get me.

[beepbeep]

I believe VoIP is a nice solution but there are economies of scale to observe.
We are dependent on our WAN-lines, so VoIP traffic is there for free. Also, our installation is somewhat bigger.

In your case, I assume you want to connect your software PBX to VoIP provider and place calls trough them instead of POT? Having only 20 extensions, it sounds like overkill. But as I said before, VoIP bandwith is minimal, you can run 10 simultanious calls trough 512kbit line.
I don't know line pricing for US but if I was to do similar deployment here in EU I would just buy a small VoIP-capable PBX, connect it to DECT base and let everyone have a wireless phone. Then I would calculate if it's cheaper to lease 2 or 4-chanell ISDN or go for VoIP trough some provider and run outside calls accordingly.

A hint: Don't assume that QoS will work just beacuse your in-house Ethernet switch honors QoS. There are many things that can go wrong and you need to test it first.

[beepbeep]

Originally Posted by Rick Lee

I have it, but know nothing about it or how it works. All I know is our entire company has 201 area codes, but we're located all over the US. When I leave voicemails and give my phone number, I always have to repeat the 201, since Wash. DC is 202. People probably try to call me back and dial 202 and never get me.

Area codes can be re-routed in public PBX nowadays. At least here in Sweden. It doesn't always mean that you are using VoIP

[DARISC]

Have Vonage at home for over 2 years. 1 line, 1 number, works just fine.