I will add that not all switches that handle QOS will handle a lot of traffic AND QOS well! I had some older Cisco 2950's that as long as the traffic loads were not high would work well but when you had all your servers AND 3 to 4 heavy phone users on the same switch bury themselves in the sand. The Cisco 3560's worked much better.
Jon On Mon, May 2, 2011 at 9:42 AM, John Hornbuckle < [email protected]> wrote: > I don’t have an answer for you, but will be watching for replies. We > don’t do VoIP here, but have been looking at it. I have the same concerns as > you—I really would rather have the VoIP network be physically separated from > my data network as much as possible (e.g., have it on its own separate > wiring and switches). For one thing, not all of our edge switches support > QoS. But I also just want to keep data and voice totally separate if I can. > > But it could be that VoIP experts think this idea is nuts. > > > > > > > > John Hornbuckle > > MIS Department > > Taylor County School District > > www.taylor.k12.fl.us > > > > > > > > *From:* Tom Miller [mailto:[email protected]] > *Sent:* Monday, May 02, 2011 9:39 AM > *To:* NT System Admin Issues > *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 > ~ 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
