05-10-2017 05:52 PM - edited 03-17-2019 10:18 AM
I have a simple QoS config, that matches RTP and SIP traffic and marks the packets with DSCP values. The weird thing is - it takes exactly 4 minutes after the call is initiated before the packets start getting marked! What on earth could be causing this? Ive never seen this behaviour before.
Heres my QoS config:
class-map match-any CM-classify-rtp
match protocol rtp
match ip precedence critical
class-map match-any CM-classify-signalling
match protocol sip
match ip precedence flash
policy-map PM-classify-in
class CM-classify-rtp
set ip dscp ef
class CM-classify-signalling
set ip dscp af31
interface gigabitethernet 0/0.2
encapsulation dot1q 2
ip address 10.131.2.4
ip nbar protocol-discovery ipv4
service-policy input PM-classify-in
05-10-2017 09:38 PM
Hi,
On Gig0/0 interface apply the command ' load-interval 60' and see if it makes a difference.
05-11-2017 07:41 PM
Hello, I applied the load-interval 60 command and there is no change to the behaviour. Thanks for the suggestion!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide