Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Just to clarify, when you write of running two cables to each cubicle, one for data and one for VoIP, the two sets of traffic never share a link (or device)? For example, both those links wouldn't terminate on the same device?
If any part of the network infrastructure shares physical resources with both the data and VoIP traffic, there's a chance the data traffic might be adverse to VoIP. If there's any physical resource sharing, QoS might be configured to guarantee resources to VoIP traffic over data traffic.
As LANs often have ample bandwidth, and it's often easy to provide more bandwidth, if necessary, you might not need to utilize QoS to have acceptable VoIP.
PS:
BTW, older hosts used to have TCP stacks that would cap their bandwidth utilization on high speed LANs. Newer TCP host stacks can often drive even 10g host links at full utilization. QoS might be needed where it didn't used to be needed.
