Useless answer #1 - it pretty much depends on what/who is doing your VoIP. Other than that, you have your voice traffic with Quality of Service on one VLAN, and your data traffic on a separate VLAN.
Splitting your voice traffic on still more VLANs? Again, you would need to work with whomever/whatever is doing the VoIP. -- Richard D. McClary Systems Administrator, Information Technology Group ASPCA® 1717 S. Philo Rd, Ste 36 Urbana, IL 61802 [email protected] P: 217-337-9761 C: 217-417-1182 F: 217-337-9761 www.aspca.org The information contained in this e-mail, and any attachments hereto, is from The American Society for the Prevention of Cruelty to Animals® (ASPCA ®) and is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying or use of the contents of this e-mail, and any attachments hereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by reply email and permanently delete the original and any copy of this e-mail and any printout thereof. "Derrenbacker, L. Jonathan" <[email protected]> wrote on 03/17/2010 01:12:57 PM: > I?m doing my first VOIP rollout and I?m getting mixed answers on how > to vlan the voice infrastructure. > I?m curious how everyone else here does it. > We have under 250 users, we?re going to have 2 call managers, a > unity box, and a IPcelerate box. Some people are saying each server > should be in its own dedicated vlan(no access lists, just for broadcasts). > Other people are saying putting them all in their own vlan is perfectly fine. > Any advice or input? > > Thanks, > Jon > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
