Forgot your password?
typodupeerror
Communications Technology

Cheap and Reliable IP Telephony? 62

Posted by Cliff
from the getting-a-handle-on-new-technology dept.
anomalie asks: "I am trying to sell IP telephony to my employer. The idea was shot down once already because of the cost (using a Cisco solution). I would like to find a cheap but reliable IP PBX because everyone liked the idea of IP telephony, just not the price associated with it. I need a system that could initially handle about 80 users at a single location, and eventually handle about 350 users at 7 locations. The two systems I have been looked at so far are Asterisk & Pingtel's SIPxchange IP PBX. I'm not looking here for a final solution, just some starting points for more research. Any feedback/tips/warnings from the Slashdot community?"
"I am looking to have at least the following capabilities:
-Auto attendant
-Handle a PRI (hopefully allow forwarding of old PBX DIDs)
-Handle long distance T1 (we would initially segment off some channels from our current PBX)
-Handle WAN Traffic so we could utilize our unused channels for long distance from other locations
-Forwarding of voicemails to email

Nice optional features:
-Web based GUI for voicemail administration
-GUI call manager

Eventually, we would have relay units at the other locations to handle the local calls and call routing and have 1 central PBX at corporate headquarters."
This discussion has been archived. No new comments can be posted.

Cheap and Reliable IP Telephony?

Comments Filter:
  • by ObviousGuy (578567) <ObviousGuy@hotmail.com> on Tuesday April 13, 2004 @08:24PM (#8855288) Homepage Journal
    It seems like replacing your current phone system is going to cost more in the short term than just sticking with what works. Will the IP telephone system cost less in the long run? What is the time frame to break-even? Will your company still be around by that time?
    • Well, I hope we will be around for a while (the company has been around for over 40 years).

      We currently have 6 locations running 5 different phone systems, and a few of the older phone systems are really showing their age and have reached their maximum capabilities. And I am afraid that it may become more difficult to find someone to support some of our remote locations the older these systems get. We have a new CEO & I have a new PHB who is really energetic about making IT a very utilized resource

      • I am currently running a project for a small (less than 800 subscriber) telephone company that is looking at replacing their switch. Because of this I have been doing a lot of research on available solutions. Now, not knowing what Cisco gave you as a quote for the system (Cisco may be significantlly cheaper than a softswitch), I would suggest looking at some of the Softswitch vendors that work in the ILEC industry, MetaSwitch, Taqua, CopperCom, Santera, Etc. A few of the vendors that offer services in th
      • Sound not too dissimilar from my situation. I am in the final presentation process of going with Csico AVVID. What I am doing, and working with a very good reseller, is doing it as a self funded project. if you are not familiar with what the means, it is quite simple. Find all the ways you can save money (hard costs, soft costs will not cut it) and use the savings generated to pay the monthly lease on the equip.

        Please email me at jason AT vilter DOT com
        I can discuss with you the +/- with Cisco and others.
  • by sinergy (88242) on Tuesday April 13, 2004 @08:33PM (#8855359) Homepage
    The only corporations that would actually stand for a gain from the benefits of IP phones are the ones that would not balk at the price of the hardware.
    The largest sum of money spent on phone systems is usually interoffice calls. Why would you set up IP phones in a single location as your goal, then add more offices as a secondary "good to have?"
    This is not sound economics -- just because speaking over your cat5 network is cool does not make it a smart thing to do.
    • Don't forget that the word of the day is globalization. More and more companies are needing to make international calls.

      The largest economy of money VoIP can provide is in international calls. Some countries can have ridiculous fees, like $5/min.

      VoIP leaves the company free to have some parts - like customer assistance - in another part of the world. That can mean lower costs.
      • This is true, however he speaks nothing of globalization in his question.

        And, is anybody actually doing this? I would not consider running an entire offshore call center over VoIP. The cost of a dedicated network circuit would surely offset the cost of telco communications.
        • Companies like

          Amazon [slashdot.org],

          CollabNet [slashdot.org](a company that would not exist if they didn't have access to engineers from India),

          Dell [com.com] (wich didn't get a good level of support for their users), and many others.

          So, yes, there are companies doing this.
        • And, is anybody actually doing this? I would not consider running an entire offshore call center over VoIP. The cost of a dedicated network circuit would surely offset the cost of telco communications.

          Now this is precisely the sort of application where VoIP does make sense. If you're filling even a moderately-sized pipe with calls a good portion of the time, then the data haul cost is a whole lot cheaper than metered phone rates - even after you throw in infrastructure and maintenance. You don't need a

      • Some countries can have ridiculous fees, like $5/min.

        You're getting screwed.

        I do a lot of international calling to some strange places. The most expensive place I know of is Kiribati (while it lasts) for about $3/min. Afghanistan and Wallis & Futuna follow at $2. After that, it falls off quickly. Most places that people actually call are dirt cheap these days. The only calls that will cost $5 and up are to certain types of satellite phones, and VoIP's not going to help you there.

        Using an ordina

        • I do a lot of international calling to some strange places.

          Ok, you can pay that when calling TO that places, but what about when THEY call you?
          • There are some schemes where you, in distant country, place a call to a machine in the US, which immediately hangs up then calls you back giving you a US dial tone. Calls in the US then cost your standard 5c/min, calls to other countries perhaps twice that (once into US and same again out). I have had calls from Hungary routed to me in the UK like this.
        • Optiop (Score:3, Informative)


          Internet-initiated calls: It may be interesting to compare this to Internet-initiated calls using Bigzoo.com's BigTalk [bigzoo.com], which cast 3.6 cents per minute to call the U.S. from New Zealand.

          Free VOIP: An option if both sides of a call have internet connections is Skype [skype.com]. At present it's free, and provides better quality than normal telephone. Skype is a great way to try VOIP without paying anything. Skype provides AES encryption of your calls, too. Skype can use port 80 for connections, so it can get past a
        • Have you seen the costs of a phone call to some of the islands in the pacific? Or islands offshore of India. I know for a fact that a call to some of the islands in the pacific have charges of $7.50 a minute. Granted, internet connections are hard as hell to get into places like that, but, it would be cheaper to have VOIP. Yes, I understand that places like this are special cases, but it goes to show even in small volume, VOIP can save money.
          • Have you seen the costs of a phone call to some of the islands in the pacific? Or islands offshore of India. I know for a fact that a call to some of the islands in the pacific have charges of $7.50 a minute.

            Like where?

            I'm looking at the rate sheet for my LD service:

            $0.15 American Samoa
            $0.61 Antarctica (okay, below the Indian Ocean)
            $1.25 Christmas Island
            $0.50 Comoros
            $0.81 Cook Islands
            $1.24 Diego Garcia
            $0.49 Fiji
            $0.37 French Polynesia
            $0.28 Guam
            $2.99 Kiribati
            $0.73 Maldives
            $0.20 Marianas
            $0.


        • Slashdot software failure? Seems to have posted nonsense before. Here is the correct version, edited from a previous comment to another story:

          Internet-initiated regular telephone calls: Internet-initiated calls using Bigzoo.com's BigTalk [bigzoo.com], which cast 3.6 cents per minute to call the U.S. from New Zealand, for example.

          Free VOIP: An option if both sides of a call have internet connections is Skype [skype.com]. At present it's free, and provides better quality than normal telephone. Skype is a great way to try VOI
    • Please don't go to a Linux or windows based software solutions. Go to always hardware/appliance based or else you loose your job, since both OS sucks always, no matter how great/political they are!
    • But it is soo cool! Actually, saving money on inter-office calls was what I was trying to sell. But, we have a lot of other expansion going on right now, so my timing probably wasn't the best. And I think it will take a while for all of the old school management here to start believing that technology isn't scary and doesn't have to be a drain on finances. Oh...I should probably post anonymously in case one of them learns how to work that newfangled Internet!
  • Vonage (Score:2, Informative)

    by ClydeBear (654996)
    We've been using Vonage for over a year now and it's great. We pay something like $25 per month for each line (we have 3) and it includes free long distance. It's cut our phone bill (while our call volume has increased!) from $1500 to $600. They send you very simple little cisco VOIP boxes, all you do is plug the ethernet into the network and the phone into the PBX/Phone and you're set.
    • Re:Vonage (Score:1, Troll)

      by dj245 (732906)
      We've been using Vonage for over a year now and it's great. vonage vonage vonage vonage blah blah blah

      are the moderators on crack or just don't know what the vonage can and can not do for you?

      Parent post wants a PBX. Not a phone company. Vonage is a phone company, not a maker of PBX devices. Nor do they sell PBX devices that are up to the job.

      Obviously this poster knows nothing about what the parent poster wants and/or doesn't care. Mod him down. As to the subject at hand, I personally don't know a

  • by johnnliu (454880) on Tuesday April 13, 2004 @08:40PM (#8855416) Homepage
    I work in a company with IP phone system. While it's good for long distance calls to branches in other cities (pay local call rates), the overall system has let us down many times.

    I'm not sure whether it's that this particular service provider is no good, or whether the service itself is still unproven.

    Anyway, just remember when the phone doesn't work, your internet also doesn't work.

    No phone calls & no emails - might as well go to the bar.
    Phones and emails are almost at the core of most businesses now, they are expected to be always working (like electricity in the building), and when they don't work, the managers get really upset.

    Anyway, I don't know who (this person is probably no longer with us) got the company to use IP phones, but they have mentioned many times how much they hate the system.

    Good luck. May be services in your area are much better.
    • by jtheory (626492) on Tuesday April 13, 2004 @11:56PM (#8856852) Homepage Journal
      The company I was in previously used the expensive, Cisco system (and it was cool to see our phones in the movies - Ocean's Eleven and others)... and we still had issues with it. Even once all the wrinkles were worked out and we no longer had echoes or constant rebooting of the phone server, it was still only as resilient as our network.

      Like parent poster said, it sucks when your network goes down and you reach for the phone only to see that it's also rebooting, and you are stranded.

      Granted this was a year and a half ago, but you're still taking the risk of much greater technical complexity, plus sharing a network that can be brought down by a lot of other factors (whereas POTS is independant).

      Before you get on the boat, you'd better be able to point to a significant savings to justify it AND you have to either factor in downtime, or pay for a bank of backup standard phone lines. Here's a good tip for evaluating providers -- ask them for contact info for a few current customers that you can talk to. They should be able to find one who can share the experiences so far. You do NOT want to be the guinea pig on the cutting edge.
      • Adgeed! Having a single cable plant for telecomm and datacomm is a risk, but there are many benefits if you do it properly.

        Before I go to far, a proper setup means redundancy on all critical components. Dual/rendundant core switches, dual links to all distribution switches, redundant voice gateways, backup power suplies and UPS power for all switches. Most important is an independent path to the pots world. Don't use your internet connection for access to the phone company, get dedicated circuits to the p

    • It sounds like your system is just setup totally wrong.
      IP phones have nothing to do with the internet unless you purposly set them up that way, and you shouldn't.

      The way our setup works, we have local lines going into the PBX (The PBX is IP based, the lines are BRI based.) You dial 9 and a local number and the calls go out the local lines. This won't be affected by the internet at all.
      If you dial 9 and a a long distance number, the PBX will see if we have any friendly PBXs in that areacode and then attem
      • Like I said, I'm just a user, I have no idea how the system works. I'm not interested to know how electricity works in my office, nor how a normal phone call goes through to the callee.

        But funny, they all work doesn't it? :-)

        I do know everytime the networks' no good, the network admin gets on the mobile (cell) to the providers, and it's usually problem on their side.

        It seems the only "necessary" service that always goes up and down is either the internet, or the ip phone system. I never hear about norm
  • Sounds bad to me. (Score:4, Interesting)

    by JMZero (449047) on Tuesday April 13, 2004 @08:43PM (#8855435) Homepage
    Unless you're having problems with your current phones, I'd keep them. It's almost certain you'll have some downtime during the switchover, and a few things to iron out during the startup.

    I've talked to a few people who've just moved to IP based phones. While they've ended up with a system that works, they had some problems setting up. And end users didn't like the new phones much - they didn't have as many speed dial buttons and certain features were awkward (well, probably just different).

    If people are complaining all the time about the phones, then this cost is OK. But if people are happy with their phones, this is going to look like a big waste of time and money.

    Wait a couple years, and you've got a good chance stuff will get cheaper, better, and your old phones will look worse.
    • "I need a system that could initially handle about 80 users at a single location, and eventually handle about 350 users at 7 locations."

      It sounds like his current system isn't the problem, but rather the expected growth from 1 to 7 locations. Having a plan that can cheaply expand to those requirements sounds like a good idea.
  • Cost vs Savings? (Score:5, Insightful)

    by JLester (9518) on Tuesday April 13, 2004 @09:16PM (#8855714)
    When you looked at the Cisco solution, did you just look at the bottom dollar or did you run the numbers on line savings, labor savings, etc? We're going from an all-Centrex phone system with about 420 lines spread across 21 sites to a Cisco VoIP system in the next few months. The initial cost is pretty high, but we're looking at a 2-2.5 year payoff. After the payoff, we're estimating a $7-$8,000 savings per month! Our network techs can do all the maintenance (no more $200+ service calls), all phones have advanced calling features and voicemail, we're leveraging the XML-based displays to add company directories and clock-in/out capability, etc.

    Don't just look at the actual cost, run the numbers on everything else too. If it doesn't work out now, stick with current setup until either the numbers work out better or until the added features justify the cost.

    Also, I personally wouldn't want to stake my company's phone system on a smaller vendor. We looked primarily at Cisco, 3Com, Nortel, and Avaya. All three have good reputations in the industry.

    Jason
    • "We looked primarily at Cisco, 3Com, Nortel, and Avaya. All three have..."

      Do you work in finance? :)
      • Oops, I originally forgot about Nortel and then remembered and went back to add it before I submitted. None of the Nortel resellers bid on our project anyway though, not sure why.

        Jason
        • I had the same experience w/ Nortel . They seem to make great voip equipment but did not seem eager to make a sale. Avaya on the otherhand was great. got me all the info i needed and put in touch w/ the right people. Afterwards they followed through to see if i needed more help.
  • Astrisk (Score:4, Informative)

    by Lenolium (110977) <rawbNO@SPAMkill-9.net> on Tuesday April 13, 2004 @09:27PM (#8855792) Homepage
    Ironically, we just switched off of using astrisk on Friday, to a non-IP phone solution.

    Astrisk really has a great set of features, a lot of which I am really going to miss. On the downside is that we were constantly having problems with it. Not major problems mind you, a couple lost calls here or there and sometimes the voicemail prompts would stutter. I'm not sure if the dropped calls were actually the fault of astrisk, or the PRI circuit we had coming in, because the astrisk console always was feeding warning messages about a particular PRI.

    This could all be because we were running off of CVS versions of astrisk, with local patches but aparently, it is the way to go, because stable releases of astrisk are very few, and very far between.

    So take this as a word of warning, astrisk is rad, but it'll take some work to get it to settle down.
    • Re:Astrisk (Score:5, Informative)

      by tzanger (1575) on Tuesday April 13, 2004 @11:13PM (#8856593) Homepage

      I second that.

      I am using Asterisk right now to offload our high-volume long distance calls over to Nufone [nufone.net]. $0.0295/min anywhere in the continental US and Canada. Great service but not offically open for business yet. Talk to Jerjer in #asterisk on OPN.

      Anyway -- Asterisk for the most part works great -- I currently have our Norstar system with four trunk lines going into an Adit600 channel bank to Asterisk. We also have 8 regular PSTN lines which go directly into the KSU. Speed dials are set to pick up a VOIP trunk line. When we move to the new building we will have a PRI going directly into the asterisk box, and a channelized T1 connection between the Norstar system and the Asterisk box. We're only going to have one "real" phone line in the building, with everything else going over VOIP to a colocation place downtown.

      Biggest problems with Asterisk (for us) seem to be with VOIP phones, not VOIP calls. Since we're using our regular Norstar system we avoid most of these issues but we are slowly moving to VOIP phones to replace the KSU since we want (much) tighter integration of the phones and computers. You pretty much require end-to-end QoS though for guaranteed reliability and clarity of calls. We do pretty go with having QoS working on both ends of the data T1 such that it's not possible to fill the pipe and cause havoc.

      Asterisk is really becoming VERY stable over the past few weeks -- I think there are under 8 bugs open in the bugtracker which are preventing 1.0 stable. (yes I realize how funny that sounds)

  • Well, we just ripped out our (not so old) PBX in favor of the Shoreline [goshoreline.com] VoIP solution and we love it. No more calling in the vendor to move a phone, calling in the vendor to change workgroups, no more calling in the vendor to ... you get it. Now, we take care of everything with a web based admin tool, handle our own hunt groups, moves and adds, etc. Plus, the shoreline system offers soft phones which let you use a usb-headset and their call manager software so you can have an extension on your computer
    • We run a shoreline switch where I work. It is pure junk. Nothing but trouble. Constant dropped calls. Horrible sounding music on hold, so much so that just about customer that calls in a hears it complains. We have swapped out the shoregear24 box already, had three separate consultants out to look at it, had Shoreline Engineers connected directly to our system all to no avail. This is all at one location with customers calling in to the DIDs. We are not even talking about office to office calls. At
  • by salesgeek (263995) on Tuesday April 13, 2004 @10:35PM (#8856302) Homepage
    Moving to IP based phones can have some great benefits to your company. If you do it right you will end up:

    - With almost unlimited flexibility for managing call routing
    - Easy integration with databases for tricks like skills based call routing
    - Low cost for intra-office communications
    - Near perfect support for work from home employees
    - Flexibility to set up spot call centers and so on
    - Really cool voice mail

    Unfortunately, most companies don't use a fraction of the capability of IP phones - a lot of time they end up being used just like the crappy 80's AT&T Merlin they are replacing. Oh yeah - make sure you have a really good SLA on your T's... downtime is SUPER EXPENSIVE when sales and customer service are down.
  • Enough of the FUD! (Score:5, Informative)

    by jaredcat (223478) on Tuesday April 13, 2004 @10:48PM (#8856394)
    Wow there are so many armchair quarterbacks in here it is unbelievable!

    I work at a mid-sized telco that heavily relies on IP telephony. To put it simply, this is where things are moving to on the carrier side and the PBX side. The technology is mature. Everyone is using it. 'Nuff Said.

    It looks like the poster is looking for a basic IP PBX that does the stuff that pretty much EVERY modern office PBX does. AutoAttendents, lite web client, simple IVR's, voicemails, and being able to interconnect with a T1 are all very standard features.

    Having researched the PBX and call center solution for my own company (about 300 users with 100 call center agents), these are my 2 recommendations:

    Artisoft Televantage
    --------------------
    -VERY Inexpensive for small offices like 5-20 people. Pretty average priced when you get up there in the users. Low base cost, high per-seat license cost.
    -Supports pretty much EVERY feature under the sun, along with some neat stuff like 'follow me' routing lists, announced hold times, and a free SDK for ODBC integration if you want to build your own IVR's and plugins.
    -Televantage runs on standard Intel Dialogic boards, so you can use T1's, DS3's, POTS lines, whatever you want. It also supports something like 1000 SIP users per server if you want to use standard SIP IP phones.
    -Biggest disadvantage to TeleVantage is that it runs on a lite version of MS SQL server. On average, we reboot our TeleVantage system about once a month just for stability's sake.

    3com NBX SuperStack
    --------------------
    -The 3com is pretty lite on features though it does cover everything that the poster asked for. Certainly not a solution for a call center, but defenitely a great box for an office environment.
    -The 3com box runs Cisco Call Manager which is a plus since the poster specifically said he likes the Cisco stuff.
    -The 3com box is very inexpensive for small-to-mid sized offices of like 30-50 people. The license cost and the base cost are both reasonable.
    -The 3com box runs the same OS as artificial hearts, so it is VERY VERY VERY stable.
    -Disadvantage is that you have to use proprietary 3com phones since insted of going with a standard protocol, 3com uses some Layer2 ultra-efficient monster of a codec that they developed internally.
    -Another disadvantage is that if you want to add features that are not available in the 3com SuperStack, you basically have to put them on a seperate box next to the machine. For instance, if you desperately wanted ACD or announced hold times, you'd end up putting a 2nd box just as expensive as a PBX right next to your PBX to handle those calls on pass-through.
    • After some reading, I have the impression that the Artisoft system is fairly easy to expand on?

      Thanks for info!

      • Yeah the Artisoft Televantage system is basically built on Microsoft COM API, Microsft MSDE Database, and Intel Dialogic Hardware. Its got more API's and SDK's than you can shake a stick at and you can pretty much customize and add whatever you like.

        Really the only significant drawbacks to the system are 1) lack of robust call center recording, quality monitoring, and reporting features (they are all there, but not as refined as I would like), and 2) stability issues due to being basically a microsoft/in
  • VoIP in Reality (Score:4, Informative)

    by Whatchamacallit (21721) on Tuesday April 13, 2004 @11:08PM (#8856549) Homepage
    Here goes...

    We deployed several offices with VoIP in a large enterprise environment. Some offices have more bandwidth then others. The one's with the least bandwidth have more issues with VoIP.

    Most problems have to do with initial setup and configuration of the phones. i.e. programming of voice mail, features, etc. The next problem is setting up the routing and networking. Then out of the blue problems with dropped calls, voice mail issues and no incoming calls.

    The hardware is only part of the problem. You have a lot of choices to make.

    1. Quality phones and PBX gear that's stable and reliable.
    2. Bandwidth, enough to handle the load of normal data and VoIP.
    3. Quality tech's to set it up the right way. Network engineers to ensure the quality of the data circuits.
    4. Quality provider with stable systems. This includes the Internet pipeline / leased line. You need to keep this circuit up and running during business hours. If the network is unstable and computers are disconnected frequently, then you can expect the phones to go with it.

    There are advantages to having your data and phones on different systems. The big advantages to VoIP come when you already have circuits in place and you are connecting multiple offices from across the country (or world). This way you can save money on inter-office calls and long distance calls (depending on the provider). Workers can setup VoIP at home and connect it to their Cable modem along with a VPN connection. This makes a lot of sense both technically and financially.

    The initial cost of VoIP hardware is justified when you need to service it.
  • I've done this. (Score:5, Informative)

    by adolf (21054) <flodadolf@gmail.com> on Wednesday April 14, 2004 @01:02AM (#8857263) Journal
    The company I work for recently (~6 months ago) sold a system almost exactly as you describe, to great effect. My job was to make it all work together between them closing one PM, and reopening the next AM. So far, they're quite happy with it.

    As configured, it has an LD T1, local DID PRI, auto attendant, VM retrieval by email, slick client-side GUI, about 120 analog (POTS) extensions, a handful of active h.323 IP extensions, and an operator console. Consumes only 4 rack spaces, instead of the couple dozen square feet of wall space occupied by their old switch. 17 PCI slots, hotswap Adaptec RAID, hotswap redundant power supplies, redundant quick-connect fans, audible alarms, gig-o-RAM, backplane, captive screws, yadda, yadda.

    80 extensions in one spot, be they IP, analog, or 80 of each, is not a big deal.

    Runs Win2k, has a network-operable Win32 GUI for administratia. It'll do all the fancy automatic least-cost call routing you can ask for between branches (via IP, or whatever other means you have). It will also do the remote PBX thing at least as well as anything else available today. Tenant-oriented resource allocation and detailed call reporting (and recording, if that's your gig) will keep the beancounters happy.

    It's called Altigen [altigen.com]. It mops the floor with Cisco's paltry offerings, across the board. And it's way, way cheaper.

    Questions?

  • by b00m3rang (682108) on Wednesday April 14, 2004 @02:34AM (#8857657)
    I'm surprised nobody's mentioned them yet, they have a great line of products.
  • Did you look at Nortel [nortelnetworks.com]? These guys have been in the phone business for over 100 years and they know how to do it right. They don't offer "low cost" solutions and definitely don't offer free solutions but, you can't go wrong with their products.

    One of the products that might fit your needs very well is their Business Communications Manager [nortelnetworks.com]. It is an all in one box for small businesses and branch offices. The Business Communications Manager(BCM) provides PBX funtionality for IP phones as well as standard ana
  • Im trying to come up with a cost effective way to unite two PBX using VOIP. My idea is that since most companys here (hint: third world) are not ready cough up the money to go to full-fledged VOIP, they might be willing to pay for a hybrid-solution: a kind of "point-to-point" line using VOIP, which let's them dial an extension on the other PBX.

    Am i just talking funny ? or is this idea doable ? i dont know a lot about PBX, but im learning (working tech support for a call center actually), i would like to kn
  • by lathama (639499)
    http://www.snom.com/

    I like their systems and they are $200 on the bottom end and go up to $400 on the phones. I mention this because I here the Cisco phones are steep!!! Also have built in switch and POE.
  • cisco and a few other companies offer voip systems with 802.11b enchantments that allows for 802.11b wireless phones
  • I really didn't see what you were trying to gain by switching to IP telephony. Most of the features you mentioned can be accomplished using traditional PBX's. The big issue to implement some of these features would be security. Just about any standard voice mail system will give you auto attendant capabilities. You can add equipment to your existing PBX's to convert voice traffic to IP and send it across your network. I highly recommend this approach because you can still fall back to traditional voice

  • IP Telephony is a reality. If you have a reliable network than you should investigate it. If you don't have a reliable network, then you've got some other business issues.

    The following link is a year old, but provides a good overview of the market:
    http://www.nortelnetworks.com/products/0 1 /eedge/bc m/collateral/nn103560-032103.pdf

    All of the major vendors have low-cost small-mid sized solutions that are very price competitive. Those that do a better job in the small-mid size market are:

    Avaya - IP offic
  • We are Altigen resellers. It's an inexpensive, reliable phone system that supports VoIP, analog and digital interfaces in a mixed environment. It has all the features you'd expect and a few you wouldn't. Check out the company page (www.altigen.com) and if you're interested, email our sales@ivrusa.com for a quote and demonstration of the product. Make sure to mention slashdot in your email.

"Our vision is to speed up time, eventually eliminating it." -- Alex Schure

Working...