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
Yes, I do.
laugh - I was temped to stop with the above, as it directly answers your question, but I assume you want to know how.
In principle, you recognize the VoIP traffic as being different from data traffic and provide it "special" egress treatment. Normally you would enable QoS, and for egress, enable PQ, direct VoIP bearer traffic to that queue. You might also direct VoIP signalling traffic to a queue that insures it's not unduly delayed or dropped. You might also set rate caps on ingress VoIP traffic.
Recognition of VoIP traffic can be done in different ways. Your phones might support L2 CoS or L3 ToS marking, your switch might "analyze" ingress traffic, your switch might trust a Cisco VoIP phone, your switch and VoIP phones might use a dedicated VLAN. Basically, there's lots of variables dealing with ingress.
Unfortunately, you've provided insufficient information for specific recommendations.
PS:
BTW, your 2960 might also support auto-QoS, which may, or may not, be all you need to enable.
