We have a VOIP phone system (Altigen), approximate 120 users in 2 locations.
Like your proposal, we have VOIP desk phones that sit between the network and the PC. Our system supports about 20 analog phones as well. I've not experienced any problems with this other than people unplugging the power from their phones for one reason or another. We've also had a few instances where a problem on the phone creates an issue with the data connection. Replacing the phone has fixed the issue. We have all HP Procurve 2600 and 2800 series switches. We have very good voice quality. I think what your vendor is telling you about voice traffic is true. At any given time, I don't think we ever have more than 10 - 12 concurrent phone sessions running; generally it's less so the level of network traffic generated by VOIP is fairly small compared to data. We're using the highest quality codec which produces the highest level of network traffic. If your network is really busy and has a ton of data traffic, you're likely to get echoing and choppiness if you don't have VOIP packet prioritization set properly on your switches. As far as typical 100 MB or better networks, I don't think it's ever really an issue for internal calls. VOIP over the internet is a whole different issue. Good luck with your project. ---------------------- Bob Hartung Wisco Industries, Inc. 736 Janesville St. Oregon, WI 53575 Tel: (608) 835-3106 x215 Fax: (608) 835-7399 e-mail: bhartung(at)wiscoind.com _____ From: Tom Miller [mailto:[email protected]] To: NT System Admin Issues [mailto:[email protected]] Sent: Mon, 02 May 2011 08:38:41 -0500 Subject: VOIP design questions Folks, We are planning to retire our current phone system and move to a Mitel VOIP system. Not having implemented VOIP before, I have some questions for those of you that have: - our vendor claims our current data network can easily handle VOIP traffic since it's a small amount of traffic (don't know exact amount yet, still awaiting vendor response). As such, they tell it is possible to use our current network to accommodate voice and data. I'm not sure if I"m comfortable with this. I was thinking of a more segregated approach: different network and voice and data never intersect. - our vendor claims we can use the existing data jack for the phones, and plug the desktop PCs/laptops into the phone as a sort of switch. I'm thinking this would add another level of complexity: phone is broke and by the way you can't get on the network now. - the reason the vendor suggests the above is that the current voice drops (cat5) terminate to phone patch panels (in most cases). Those cables would need to be cut and re-terminated to switches. So I have some concerns about our vendor claims. The dollar figure they propose does not include network changes, new switches, etc. Looking at the cost proposal, I am thinking there are quite a few hardware and man-hours costs missing. What do you folks do for VOIP? Thanks, Tom Confidentiality Notice: This e-mail message, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
