MS Teams Traffic Shapping on MR 56

[AxL1971]

Anyone used a custom traffic shaping policy for MS Teams traffic or does the default VOIP policy suffice

Access Points are MR56

[Mloraditch]

I don't work in a lot of low bandwidth environments, so generally the default policies seem to suffice these days for me.  However I'm sure some others here will have thoughts. Here is an older thread on the subject: https://community.meraki.com/t5/Security-SD-WAN/QoS-for-Teams/m-p/102045#M25647

It's technically relating to MXs but many of the same ideas would apply

[Inderdeep]

This may help you 

https://documentation.meraki.com/MR/Firewall_and_Traffic_Shaping/Traffic_and_Bandwidth_Shaping

[Inderdeep]

Check this one about the Strategy

https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Simple_Traffic_Shapin...

[cmr]

Have you enabled QoS tagging for Teams in the 365 admin console?

[cmr]

Configure QoS settings in the Teams admin center - Microsoft Teams | Microsoft Learn

[PhilipDAth]

This.  You need to enable QoS in Teams first.  Afer you do that, there isn't much to do if you have Meraki's default traffic shaping enabled.

[GIdenJoe]

For the downstream direction it suffices to use the MS Teams Voice NBAR category to set the DSCP value to EF and of course put a custom limit or ignore limit option.  If your VLAN is tagged you can also set the PCP tag to 6.

However for upstream traffic treatment you will need to make sure your clients tag their traffic with DSCP EF and L2 tag to 6 to give it the correct upstream scheduling.

If you use the port matching you can add this using the Add-NetQoSPolicy commandlet in windows.  The default UDP source ports are 50000-50019 for voice traffic and you can use that for matching.