Cheap and Reliable IP Telephony? 62
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."
What problem are you trying to solve? (Score:5, Insightful)
Re:What problem are you trying to solve? (Score:1)
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
Re:What problem are you trying to solve? (Score:3, Informative)
Re:What problem are you trying to solve? (Score:1)
Please email me at jason AT vilter DOT com
I can discuss with you the +/- with Cisco and others.
You should probably think things over. (Score:5, Insightful)
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.
Re:You should probably think things over. (Score:3, Insightful)
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.
Re:You should probably think things over. (Score:1)
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.
Re:You should probably think things over. (Score:2)
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.
Re:You should probably think things over. (Score:1, Informative)
Re:You should probably think things over. (Score:3, Interesting)
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
Re:You should probably think things over. (Score:3, Informative)
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
Re:You should probably think things over. (Score:2)
Ok, you can pay that when calling TO that places, but what about when THEY call you?
Re:You should probably think things over. (Score:1)
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
Re:You should probably think things over. (Score:1)
Re:You should probably think things over. (Score:2, Informative)
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.
Options. (Score:2)
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
Re:You should probably think things over. (Score:3, Interesting)
Re:You should probably think things over. (Score:1, Interesting)
Re:You should probably think things over. (Score:2)
Re:You should probably think things over. (Score:1)
Vonage (Score:2, Informative)
Re:Vonage (Score:1, Troll)
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
Re:Vonage (Score:2)
I'm just an IP phone user. (Score:5, Interesting)
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.
Similar experience with Cisco (Score:5, Insightful)
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.
Re:Similar experience with Cisco (Score:2)
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
Re:I'm just an IP phone user. (Score:2)
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
Re:I'm just an IP phone user. (Score:1)
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)
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.
Re:Sounds bad to me. (Score:2)
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)
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
Re:Cost vs Savings? (Score:1)
Do you work in finance?
Re:Cost vs Savings? (Score:2)
Jason
Re:Cost vs Savings? (Score:1)
Astrisk (Score:4, Informative)
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)
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)
Satisfied Shoreline customer (Score:2, Interesting)
Re:DISsatisfied Shoreline customer (Score:1)
Re:DISsatisfied Shoreline customer (Score:2)
By the way, I've dealt with Shoreline products. That Merlin doesnt sound THAT bad, now does it...
IP for the sake of IP (Score:5, Interesting)
- 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)
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.
Re:Enough of the FUD! (Score:1)
Thanks for info!
Re:Enough of the FUD! (Score:2)
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)
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)
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?
Avaya - IP Office (Score:3)
Re:Avaya - IP Office (Score:1)
Did you look at... (Score:2)
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
Business Idea (Score:1)
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
Snom (Score:1)
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 802.11b voip (Score:1)
Cheep and Reliable IP Telephony. (Score:1)
ignore FUD and investigate the many options (Score:1)
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
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
How about this for a solution (Score:1)