Cisco webex QOS shaping best practice

[mai.shaltout]

Hello All,

I hope you are doing fine.

My question is regarding the cisco webex traffic shaping, our customer has many performance issues in cisco webex so I would like to know on what is the best practice recommended by cisco to classify and shape cisco webex voice, video and signaling .. etc traffic in both directions.

Note: I have cisco router connected to ISP but as we all know outgoing traffic can be limited and shaped but incoming can not be controlled as it is sourced from cisco through ISP which is out of my control.

1- For traffic shaping I tried to filter Shaped QOS classes based on Ports and the issue was that the ports was not enough to differentiate between voice traffic and video traffic so drop action was affecting both traffic.

2- I read that we can do NABR protocol classification on router in QOS so i need to know what is the protocol i can use to match each kind of traffic and ensure each traffic type in cisco webex can be filtered.

Does anyone know what is the NABR protocol used on webex for each video, audio and other applications and is it enough or we have to list the cisco webex destination IPs and ports for each traffic type?

Our router model is ISR4431/K9 and has NABR package 43

IOS isr4400-universalk9.16.12.05.SPA

pmmu049#sh ip nbar protocol-pack active
Active Protocol Pack:
Name: Advanced Protocol Pack
Version: 43.0
Publisher: Cisco Systems Inc.
NBAR Engine Version: 37
State: Active

[Joseph W. Doherty]

Sorry, not current on current/recent NBAR protocol options, but did what to mention, for real-time voice and/or video traffic, shaping is often what you want to avoid.  I.e. you need to both insure adequate bandwidth and prioritize over all other traffic to insure RT packets are not delayed.

Some later Cisco QoS platforms support a two tier priority class, level 1 used for voice and level 2 used for video.

Regarding signally traffic, if it can be identified separately, it generally doesn't need to be prioritized like RT, but you do want to insure it also has adequate bandwidth so that its packets are not dropped.  (NB: signally often needs little bandwidth.)

NB: shaping, though, might be used to limit total traffic to some limit, but within that, above still applies.

[mai.shaltout]

Hello Josephe,

Thanks for your reply, i have below configuration designed to maintain voice traffic prioritized over the video and signaling, However my question is now about the class-map is NABR protocol below matches is practically enough to classify the packets for webex traffic voice , video and other webex tested OK or i have to add IPs with ports ?

class-map match-any CISCO_WEBEX_SIGNALING
match protocol webex-meeting
match protocol cisco-spark
class-map match-any CISCO_WEBEX_VIDEO
match protocol webex-video
match protocol cisco-spark-video
class-map match-any CISCO_WEBEX_AUDIO
match protocol webex-audio
match protocol cisco-spark-audio

policy-map PMAP_WEBEX_EGRESS
class CISCO_WEBEX_AUDIO
priority level 1
police 10000000 conform-action set-dscp-transmit ef exceed-action drop
class CISCO_WEBEX_VIDEO
bandwidth remaining percent 20
class CISCO_WEBEX_SIGNALING
bandwidth remaining percent 40
class class-default

!