[asterisk-users] network design philosophy and practice

[Jeff LaCoursiere]

On Wed, 29 Oct 2008 11:50:31 -0500, Tilghman Lesher wrote
> On Wednesday 29 October 2008 10:22:43 David Gibbons wrote:
> > A phone takes very, very little bandwidth away from the desktop and a decent
> > one will support tagging its frames for the alternate voice VLAN.
> >
> > --snip--
> > In almost all cases it is much better to have two seperate networks.
> > This may be impractical in some smaller installs, but in any office
> > setting we always do this. The only reason I can think of not to is to
> > eliminate the cost of the second cable.
> > --snip--
> 
> The concern is almost never one of taking bandwidth away from the 
> desktop, but one of the desktop taking bandwidth (especially by 
> introducing latency) away from the phone.  Though, as you pointed 
> out, a good QOS and VLAN policy will make that usually unnecessary.  
> Folks do have to contend with customers who won't spring for 
> anything but el cheapo network switches, and that's where a 
> completely separate physical network makes sense.
> 

I was under the (very possibly mistaken) impression that by running the desktop through the phone 
the phone will keep the PC from doing such terrible things.  At least that seems to be the case in the 
installations I have done with Polycom phones to date.

My largest is a 150 phone installation at a major resort.  No VLANs, no QOS, and pretty much 
everything runs back to mid-range Linksys managed switches.  I only have quality issues when they 
try to use the Internet connection for long distance, which in the Virgin Islands is spotty at best ;)

I think much too big a deal is being made here and over-engineering is at work.  But then my 
installations are not into heavy LAN use.  I suppose as always it depends on the situation.

--
Jeff LaCoursiere
JB Telenet, LLC
6501 Redhook Plaza, box 395
St Thomas, USVI 00802