jgard - Thanks for posting your question on the forum!
With the configuration you provided, QoS is currently setup to match traffic marked with a DSCP value of 46. This is the DSCP value most voice packets from IP phones are marked with. This traffic would then be given priority of 1 Mbps should the link become congested.
I would be more than happy to help you configure the ACL in your QoS map, however, I am a little unclear if you would like to mark the traffic in your ACL with a certain DSCP or precedence value or if you would just like to prioritize this traffic?
Please do not hesitate to let us know if you have any questions.
Depending on what version ShoreTel you are using may change your QOS needs.
You can set RTP DSCP for shore Gears and phones only on pre 13.x code. What that means, only set to
set or Shore gear RTP is prioritized no signaling and no Call server RTP.
13.x and later you can set the call server RTP and signaling
If you run “sho qos map int ppp 1” do you see matches?
I sometimes do this to set dscp on input interface:
qos map remark 10
match ip list 105
set precedence 46
interface eth 0/1.1
vlan-id 1 native
ip address 10.7.51.1 255.255.255.0
qos-policy in remark
My QoS is matching the packets, and have tracked some internal issues that was causing the jitter for our voice traffic. Thanks for the response, I will keep this in mind.