Desmond*
*br...@briandesmond.com*
* *
*c – 312.731.3132*
* *
*From:* Evan Brastow
[mailto:ebras...@automatedemblem.comebras...@automatedemblem.com]
*Sent:* Thursday, December 17, 2009 7:02 PM
*To:* NT System Admin Issues
*Subject:* RE: VLAN question
Wow guys… seriously.. what a great
Little late to the party, but figure I'll throw in my $.02 worth. As
was mentioned by several, the key thing here you need to be concerned
with is QOS. Putting the data and voice on separate VLANs is a best
practice in my experience, but that alone isn't going to prevent
breakups/dropouts/etc.
...@pittcountync.gov]
Sent: Friday, December 18, 2009 7:34 AM
To: NT System Admin Issues
Subject: RE: VLAN question
Little late to the party, but figure I'll throw in my $.02 worth. As
was mentioned by several, the key thing here you need to be concerned
with is QOS. Putting the data and voice on separate VLANs
I suspect that what would help more than VLAN would be QOS. Configure
your ProCurve to prioritize voice traffic from the phones. VLAN can help
with that, but it's not essential for that.
You might also try connecting one of the phones separately from the
computer - by that I mean give the
Short answer - yes!
What your phone vendor is referring to is simply VLAN segmentation and
it is an *essential* part of a well performing IP Telephony system. The
phones likely have the capability to run an 802.1q trunk to your HP
switch. What this essentially does, is allow the phone to
Great post J
From: Rohyans, Aaron [mailto:arohy...@dpsciences.com]
Sent: 18 December 2009 00:37
To: NT System Admin Issues
Subject: RE: VLAN question
Short answer - yes!
What your phone vendor is referring to is simply VLAN segmentation and it is
an *essential* part of a well
and QoS. Heck, last time I
knew anything about real networking, VLANS was a typo J
Evan
From: Clayton Doige [mailto:clayton.do...@gmail.com]
Sent: Thursday, December 17, 2009 7:47 PM
To: NT System Admin Issues
Subject: RE: VLAN question
Great post J
From: Rohyans, Aaron [mailto:arohy
