Separate VLAN absolutely, and in fact you can run the DHCP scope for that VLAN off of the same Windows DHCP server (dependant on the phone system and supported scope options) - you would just need to add the scope options into that scope to tell the phones what IP address the controller lives on - but if your phone guy can do that for you all the better. You might need to do some switch config as well so the switch is aware of the two VLANs given your phones and PC's use the same switch port.
From: Don Ely [mailto:don....@gmail.com] Sent: 18 December 2009 00:30 To: NT System Admin Issues Subject: Re: OT: VLAN question You're right, I shouldn't say they can't. I should say they shouldn't comingle. Best practice separates them because in theory it's easier to control and segment the traffic... On Thu, Dec 17, 2009 at 4:10 PM, Ben Schorr <b...@rolandschorr.com> wrote: Separate them logically or physically? I have to disagree that they CAN'T comingle - in a well-designed and implemented system they can. We support a site that runs voice and data over the same network for about 40 users (currently) and it works pretty well for the most part. Voice over IP is not really a very high bandwidth operation. Unless you're really underbuilt on your infrastructure you should be able to support it. Ben M. Schorr Chief Executive Officer ______________________________________________ Roland Schorr & Tower www.rolandschorr.com <http://www.rolandschorr.com/> b...@rolandschorr.com > -----Original Message----- > From: Don Ely [mailto:don....@gmail.com] > Sent: Thursday, December 17, 2009 2:04 PM > To: NT System Admin Issues > Subject: Re: OT: VLAN question > > Always separate voice and data. Your network guy isn't very astute if he > thinks the can comingle... > > On 12/17/09, Evan Brastow <ebras...@automatedemblem.com> wrote: > > Preface: I have no idea what I'm talking about. > > > > > > > > With that out of the way, I have a network consultant and a phone > > supplier that are a little bit at odds. > > > > > > > > We just purchased an Allworx IP phone system. All was going well until > > it was made active today and because apparent that voice quality was > > horrible. The IP part is only internal... External calls go over > > standard analog lines. But the problem is with internal calls as well > > as external. > > > > > > > > The Allworx phones share a 100Mbps network with the computers. We're a > > small company (smaller than ever) with about 25 computers and 19 > > phones, BUT, a lot of those phones and computers are out in production > > areas and receive VERY little use (i.e., someone will log in/out of a > > job once every few hours, and make a phone call once a day out there.) > > There are probably only about 8-10 active computers, and fewer active > phones. > > > > > > > > The way it's configured is that the phone sits on the same cable as > > the computer. It goes from the wall jack to the phone, and then from > > the phone to the computer. The phone are on the same subnet as, and > > get IP addresses from the same DHCP server as the computer network. > > > > > > > > When phone calls are made, there's echoing, latency, static, etc... > > The switch is an HP ProCurve 2810-48G. Cabling is all CAT5 at least. > > > > > > > > The phone supplier is telling me that the way to segment the traffic > > to make sure there are no voice quality issues is to create a VLAN on > > the switch. But my IT consultant is saying, "What's to segment? > > Everything's on the same cable and on the same subnet?" > > > > > > > > It appears now that the phone supplier is saying that he can create a > > VLAN, and then they would use the Allworx phone system server as a > > DHCP server for the phones, which would put them on their own subnet, > > thereby making all the traffic flow better and the calls clearer. He > > said he'd have to link the two VLANS together as there are computer > > apps that interface with the phone system. > > > > > > > > So, my question is (because I don't know much about this end of > > networking,) does this sound like creating a separate VLAN is really > > going to help improve bandwidth and increase call quality? > > > > > > > > Thanks so much J > > > > > > > > Evan > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > -- > Sent from my mobile device > > ~ 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/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
