I am currently doing an evaluation of VOIP vs current PBX(or upgrading) for a client and I've run into a stumbling block. While I have found plenty of info on the plus side of VOIP as well as security risks that could be a negative does anyone have specific information on performance problems with VOIP? I really need a both sides of the issue evaluation but aside from vague references to voice quality i can find nothing specific-can anyone help??
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VOIP Problems 2
- Thread starter phoneguru
- Start date
-
1
- #2
Anymore there is really nothing to compare. IP telephony is pretty good these days.. I've rolled out systems from AVAYA and Cisco and they all work great. Keep in mind though, if you need simple things like to be able to use modems and such. IP telephony will not suit your needs.. Sound quality is good anymore to which it shouldn't be a factor.
Another thing you could do is like an IP enabled PBX.
BuckWeet
Another thing you could do is like an IP enabled PBX.
BuckWeet
- Thread starter
- #3
-
1
- #4
We are also currently looking into VoIP, and your right you cannot find anyone talking down the system. Personally I think it is due to the economic times, you have a bunch of hardware vendors who are hurting for sales and they will say anything to get you to change from your existing infrastructure.
But my political views aside here are some things we’ve found.
Cisco offers no hacker/phreaking type of guarantee.
Cisco is unable to provide TTY service for the hearing impaired.
I don’t care what they say VoIP is going to be a bandwidth hog, The compression is good, but I don’t see how you are really going to save T-1 costs. My guess is you will still end up with dedicated T’s for both voice and data.
Reliability – Most of the VoIP system is server based. How many times a year does your email, internet, database server go down? Just imagine it’s your phone system. I realize you can build redundant systems, but then you are loosing your pricing edge over TDM.
Having said all that, I think VoIP is definitely the future of telecom. I just don’t think if it were me, I would jump both feet first in to a TOTAL VoIP solution, I would ease my way into it.
Another good thing to do is to get different reps from Nortel, AVAYA, and Cisco into talk to you about VoIP and ask them why you should choose their system over the others, they will give you all the dirt on the other solutions.
RTMCKEE
(p.s. my assumption is that you are looking for an large system, I think VoIP is an excellent solution for small offices that dont need high avalability)
But my political views aside here are some things we’ve found.
Cisco offers no hacker/phreaking type of guarantee.
Cisco is unable to provide TTY service for the hearing impaired.
I don’t care what they say VoIP is going to be a bandwidth hog, The compression is good, but I don’t see how you are really going to save T-1 costs. My guess is you will still end up with dedicated T’s for both voice and data.
Reliability – Most of the VoIP system is server based. How many times a year does your email, internet, database server go down? Just imagine it’s your phone system. I realize you can build redundant systems, but then you are loosing your pricing edge over TDM.
Having said all that, I think VoIP is definitely the future of telecom. I just don’t think if it were me, I would jump both feet first in to a TOTAL VoIP solution, I would ease my way into it.
Another good thing to do is to get different reps from Nortel, AVAYA, and Cisco into talk to you about VoIP and ask them why you should choose their system over the others, they will give you all the dirt on the other solutions.
RTMCKEE
(p.s. my assumption is that you are looking for an large system, I think VoIP is an excellent solution for small offices that dont need high avalability)
Because modems are very sensitive to noise in the line, and various other reasons.. Well with VoIP, it samples the audio, then packetizes it. Where as in TDM world, its a circuit based switch, its not getting packetized and its not getting compressed.. Even though with codecs like g711, they still are getting comressed somewhat and you still have that audio sampling issue.
BuckWeet
BuckWeet
Don't go there with that reliability stuff because its based on servers, if its so bad, then why is AVAYA themselves going to the server based approach? Also, look at the S8700, they doubled if not more than tripled their BHCC than compared to the old G3R processors.. And they also cranked up the PN capacity, they cranked up total station count per system. etc.... The whole reason to go VoIP is so you can get some bandwidth back for Data reasons. Or like in my company we have a Qwest VPN cloud that we use for data throughout the country, and we also run Definity IP Trunking across this.. You couldn't run traditional telephony that way. As as for the bandwidth hog stuff, thats phoey too. G729 (which anymore you can't really notice a difference between that and G711 or a circuit connection) you can get down to about 12Kbps.. Thats saving you 52Kbps of bandwidth per call which you could use for other calls or your data transmissions.. I install both Cisco and AVAYA IP solutions, and while each has their benefits, it all comes down to what you need and how your infrastruture is going to be designed.. AVAYA has new products out now that is in total competition with Cisco's solution. They can now offer a full IP telephony solution. Sorry to bable, but all I can say is that the new technology does in fact work.. There are times that IP systems can't replace traditional pbxs, and there are places I wouldn't think of doing an IP system.
Once again it comes down to what you need.... Thats the bottom line.
BuckWeet
Once again it comes down to what you need.... Thats the bottom line.
BuckWeet
BuckWeet,
I knew I was going to step on some toes with my statement. Let me claify my "bandwidth hog" statment. I realize that the compression is VERY good these days. I was doing voice over wireless T'1s about 10 years ago and the compression was terrible.
At our remote sites we currently have one T for local and LD voice (pstn access) and one T for data. My mangagers are under the impression that they can go to just one T and be good to go. Which would be true if our remote sites were in the same area code, you wouldn't necessaraly need pstn access for 911. Our offices however cover the western half of the US. So at any given site we will need a T for IP voice and data, (note we went from a full T for data to some fraction to share it with the voice)and some 1FB's for PSTN access at each site, depending on the size of the site it might be cheaper to put in a full T for PSTN access as well (not saving anything accept the cost of calls to the main office). Also again I know the compression is good, but on ALL the demos I've gone to they always demo the product with NO compression.
As far as the server issue goes I will stand behind what I said Server based systems are less reliable that traditional PBX's. Period.
One of the big selling points of VOIP is cost savings, but when you look into building a Server based system with enough reliablity to equal trational pbx's you are getting into the same price range.
One last parting shot.... When was the last time your PBX caught a VIRUS?
RTMCKEE
I knew I was going to step on some toes with my statement. Let me claify my "bandwidth hog" statment. I realize that the compression is VERY good these days. I was doing voice over wireless T'1s about 10 years ago and the compression was terrible.
At our remote sites we currently have one T for local and LD voice (pstn access) and one T for data. My mangagers are under the impression that they can go to just one T and be good to go. Which would be true if our remote sites were in the same area code, you wouldn't necessaraly need pstn access for 911. Our offices however cover the western half of the US. So at any given site we will need a T for IP voice and data, (note we went from a full T for data to some fraction to share it with the voice)and some 1FB's for PSTN access at each site, depending on the size of the site it might be cheaper to put in a full T for PSTN access as well (not saving anything accept the cost of calls to the main office). Also again I know the compression is good, but on ALL the demos I've gone to they always demo the product with NO compression.
As far as the server issue goes I will stand behind what I said Server based systems are less reliable that traditional PBX's. Period.
One of the big selling points of VOIP is cost savings, but when you look into building a Server based system with enough reliablity to equal trational pbx's you are getting into the same price range.
One last parting shot.... When was the last time your PBX caught a VIRUS?
RTMCKEE
scottyjohn
Technical User
The new media servers from Avaya come on either win 2000 or Linux red Hat platforms. I take it that the Linux route would be the best solution for stability due to its unix roots? John
- Status
Similar threads