I don't have time to read the other replies (I'm drowning here!)...
The data world is a bit different from the VoIP world. Phone traffic
(let's call it things like "SIP" and "RTP") require absolutely top
priority through the wires.
1. Depite the same wires, there absolutely must be a separate
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 wrot
schorr.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 se
landschorr.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
Always separate voice and data. Your network guy isn't very astute if
he thinks the can comingle...
On 12/17/09, Evan Brastow 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 odd
In short, yes. This is because you're most likely not doing QOS on the LAN.
Which means the elf bowling e-mail to that production guy shares the same
priority as the call the CEO made to his wife. With the vlan you are
effectively segmenting them completely from each other. Even if they share th
