Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Communications

Solutions for Small Business VoIP? 232

MajorBlunder asks: "I'm part of the IT department of a small but prospering software company. We have recently filled the capacity of the POTS PBX phone system we currently have installed. We are currently looking into switching over to a VoIP phone system. We have a sizable IT staff in proportion to the rest of the company, so we'd like to be able to maintain the hardware/software in house as much as possible. I wanted to ask the Slashdot readership what experiences they have had with switching over to from POTS to VoIP. Any recomendations for full end to end solutions would be appreciated, and recomendations of things to avoid would be great."
This discussion has been archived. No new comments can be posted.

Solutions for Small Business VoIP?

Comments Filter:
  • Re: Asterisk (Score:2, Insightful)

    by Py to the Wiz ( 905662 ) on Tuesday November 29, 2005 @10:25PM (#14143709)
    Having seen smart people struggle to get Asterisk working (cool a system as it is!), I imagine there would be quite a brisk market for a pre-configured, low-power box running asterisk ready for the user to plug in some custom messages, and / or rely on existing generic ones. That is, something truly plug-and-play, providing your have at least one POTS line to which it can be connected.

    Such a system needn't be *cheap* exactly in order to be quite a bit less expensive than typical PBXes, which are usually overkill for small businesses, as well as for any but the most elaborate homes. (Should be doable for a few hundred dollars, I'd guess.)

    Or am I just missing that someone is selling such a beast already?
  • by ravenvijesh ( 934885 ) on Tuesday November 29, 2005 @10:42PM (#14143794)
    VoIP can be tricky - stay away from going exclusively VoIP, for example using Vonage, Broadvoice etc... for business in my experience it's just not there yet. The trickiest part will most likely be choosing the right phones and integrating with whichever PBX / Gateway you'll be implementing. Asterisk is a very solid option - but make sure the server that it's running on is reliable and that the IRQ issues aren't a concern with the hardware.

    Getting outbound VOIP Lines might not be mature enough for your company yet. There are always call quality issues unless you manage to get physically near your termination provider and you have a fat pipe from your offices.

    The fact that you're a part of a development house is going to help out a lot when customizing your solution. Asterisk really isn't that complicated - modifying it so that it fits your companies needs and provides true business benefit is probably the biggest thing. (Like integrating it with your existing CRM solution or back ending VoIP to your database).

    There is a PDF which helps on the overall analysis and how Asterisk can be pretty usefull for smaller businesses =
    A Voip Small to Medium Business Analysis [skyyconsulting.com]
  • by g-san ( 93038 ) on Tuesday November 29, 2005 @10:44PM (#14143808)
    Your network is a factor here as well. Do you know how much traffic you have on the network currently? Can your routers do prioritization on different traffic types, either IP Type of Service or tcp/udp port? You want to have that understood to make sure the quality is good, so VoIP doesn't affect your usual traffic and vice versa.

    You can also get switches/modules nowadays that have Power over Ethernet (PoE). So of the two RJ-45 connections (you have the physical cabling for this, right?) in a cube, one connects their PC and the other connects the VoIP appliance/phone back to the PoE port. The phone gets it's power from the ethernet cable. If those switches and the rest of your key servers and network are on UPS, the phones still work when the power goes out.

    Good luck.
  • IPT tips (Score:1, Insightful)

    by Anonymous Coward on Tuesday November 29, 2005 @10:46PM (#14143815)
    I have implemented many offices with Cisco Call Manager, sorry as this is the only VoIP PBX I have experience with.
    The best tip I can give is to make sure that you have a good infrastructure in place, that supports QOS (quality of service). Typically I only work with Cisco equipment, but I can say that this is an important step. This helps preserve needed bandwidth for call setup and for current active calls. Without it calls will drop, and you will experience choppy / robotic conversations. A Cisco 3560 access switch would be a good choice, as it allows you to use auto qos, and modify the qos statements to fit your needs.
    You also might want to look into equipment that can do SRST (survivable remote site telephony) if the IPT (IP telephony) equipment isn't in the same office as the phones. This will allow you to do basic phone service for the office (make and receive calls) with out the need of the CCM (Cisco call manager).
    In short, not sure if Cisco Call Manager is a good solution for the size of your company, but since you own /rent a PBX it cannot hurt. There are many consulting firms out there that can host the call manager in their own NOC, making it an attractive solution.
    Hope this helps ~MP
  • Re:Cisco (Score:3, Insightful)

    by ldspartan ( 14035 ) on Tuesday November 29, 2005 @10:56PM (#14143858) Homepage
    I won't argue since I have an obvious bias, but Asterisk and CCM aren't really comparable. Using CCM for 400 users wouldn't be cost effective, which is why CME exists. And yes, Callmanager is about a thousand times more complex than Asterisk, and it does a hell of a lot more as well. A lot of those features probably don't matter to a lot of folks, but Callmanager runs installs with tens (and hundreds) of thousands of phones. A bit different running, say, all the phones for a major bank or credit card processing house than running 400 phones in a small or medium sized business.

    Different strokes for different folks, but you'd be stupid to dismiss either option out of hand.
  • Re:My experience (Score:3, Insightful)

    by NoMoreNicksLeft ( 516230 ) <john.oyler@ c o m c a st.net> on Tuesday November 29, 2005 @11:30PM (#14144047) Journal
    I predict 37 clueless "Vonage" replies before this thread reaches 100 comments. 34 of those users will continue to defend their clueless "Vonage" answers even after it's pointed out that they don't want to ditch the landlines so much as they want to have more extensions than their phone hardware allows. Of those 34, 29 of them will have no clue what an extension is in this context, even though they have certainly dialed an extension at least once in their useless gibbering idiot lives.

    BTW, for those of you clever enough to know the guy is asking about asterisk... that part is probably obvious to him. He's more concerned with how to manage a network, bandwidth and hardware wise, to use this. With maybe a little "what's the best VOIP phone for your money" thrown in.
  • Re: Asterisk (Score:1, Insightful)

    by Anonymous Coward on Wednesday November 30, 2005 @12:22AM (#14144244)
    VoIP and Plug-n-Play DO NOT BELONG in the same sentence.. or even same paragraph.

    It's a intensely complicated thing with lots of options and lots of issues to deal with.. Anything that is easy to use or plug-n-play would actually make things more complicated and difficult to setup..

    As Asterix stands now it is perfectly good as top-of-the-line solution. It has hardware support and interlopy and is quite more well known in telephony circles rather then in computer ones.

    If Asterix is to complicated and difficult for you to setup then you have no business setting something like that up for a big company. If you want there are commercial systems based around asterix that you can purchase.
  • by Anonymous Coward on Wednesday November 30, 2005 @01:20AM (#14144629)
    And were are the ACD capabilities for Asterisk?

    http://www.voip-info.org/wiki-Asterisk+Wishlist [voip-info.org]

    Plus if one's running a call-center one needs to be able to keep track of overall phone system stats, as well as per-agent.
  • by Anonymous Coward on Wednesday November 30, 2005 @01:55AM (#14144781)
    We replaced our Avaya G3 with a Zultys MX250 just recently, keeping our T1 PRI lines for call quality reasons. We went with VOIP for the feature set and price, not for long-distance savings. I'd think the Zultys setup would work really well for a small software company.

    I found out about Zultys at commweb.com - they have articles on a lot of alternatives to the big guys (Cisco, Avaya) and Asterisk.

    Just a couple of tips from someone who's been there:

    - it's a lot harder than you'd think to get a fax machine working on a VOIP system, reliably, so consider electronic fax seriously (unless you honestly don't need fax)

    - it's worth your while to catalog all the features you're used to having in your circuit-switched PBX, and ask your candidate new provider how they're implemented, exactly - even the small stuff

    The Asterisk site is a great resource, even if you go with somebody else's SIP system. We used Cisco phones but I don't know that I'd do that again, as they've been dropping like flies (20% of the original set have been returned for replacement, and some of the replacements have, too).

    VOIP is, without a doubt, a lot more fun to work with than the old circuit-switched stuff.

He has not acquired a fortune; the fortune has acquired him. -- Bion

Working...