Optimal settings in SD-WAN for Microsoft Teams

rhamersley
Getting noticed

Optimal settings in SD-WAN for Microsoft Teams

Would like to send a message out to the community on your configuration for the MX Security Appliance for the optimal configuration to set a high priority for Microsoft Teams.

 

Anyone have any configuration suggestions?

4 Replies 4
DarrenOC
Kind of a big deal
Kind of a big deal

Are we talking Teams telephony?  If so and you’re using Direct Routing there’s pretty nothing much you can do to optimise from the MX outbound to the internet.  Once those packets touch the internet you’ve lost control of those packets.

 

Operator Connect could be an option for you:

 

https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan

 

 

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
DarrenOC
Kind of a big deal
Kind of a big deal

@rhamersley , apologies, just re-read the title of your post and realised you’re using SD-WAN.  This previous post resolved by @PhilipDAth  may help:

 

https://community.meraki.com/t5/Security-SD-WAN/SD-WAN-MX-16-16-Little-Help-Needed-Best-Practices-Ti...

Darren OConnor | doconnor@resalire.co.uk
https://www.linkedin.com/in/darrenoconnor/

I'm not an employee of Cisco/Meraki. My posts are based on Meraki best practice and what has worked for me in the field.
ww
Kind of a big deal
Kind of a big deal

I never understood those default rules. They tag the traffic but do nothing else.. or do they..

GIdenJoe
Kind of a big deal
Kind of a big deal

Any MX using NBAR can recognize MS Teams traffic.
What I personally always do is the following:

GIdenJoe_0-1706516809667.png

I always match all voice applications and give these a DSCP EF marking (so I have to assume the high setting will be ignored and the MX will put them in the realtime queue).  Notice the MS Teams Audio tag in the config.

Then the second rule matches the rest of voice and video which will be the video and call signaling protocols and those then get the AF41 and high queue.  Since matching is always done top down this configuration should work.

 

It is important that the voice part hits the realtime queue of your MX so it goes outbound first.  Once your packet hits the internet it is fair game for any kind of treatment.  So you only have control of outbound packets on your own MX towards the ISP.

Get notified when there are additional replies to this discussion.