I agree. Put it all on one vlan. No routing issues for people to point fingers at.
-----Original Message----- From: Phil Brutsche [mailto:[email protected]] Sent: Wednesday, March 17, 2010 2:25 PM To: NT System Admin Issues Subject: Re: VLans for VOIP Infrastructure I say put all the voice stuff in one VLAN, even the phones. Cisco VoIP is almost exclusively unicast; the only exceptions are DHCP chatter and multicast for phone paging. Derrenbacker, L. Jonathan wrote: > 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? -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
