Skype for Business has various workloads that require differentiated QoS treatment. If you plan to consume voice services through ExpressRoute, you should adhere to the requirements described below.
QoS requirements apply to the Microsoft peering only. The DSCP values in your network traffic received on Azure public peering and Azure private peering will be reset to 0.
The following table provides a list of DSCP markings used by Skype for Business. Refer to Managing QoS for Skype for Business for more information.
|Traffic Class||Treatment (DSCP Marking)||Skype for Business Workloads|
|Voice||EF (46)||Skype / Lync voice|
|AF21 (18)||App sharing|
|Default||AF11 (10)||File transfer|
|CS0 (0)||Anything else|
- You should classify the workloads and mark the right DSCP values. Follow the guidance provided here on how to set DSCP markings in your network.
- You should configure and support multiple QoS queues within your network. Voice must be a standalone class and receive the EF treatment specified in RFC 3246.
- You can decide the queuing mechanism, congestion detection policy, and bandwidth allocation per traffic class. But, the DSCP marking for Skype for Business workloads must be preserved. If you are using DSCP markings not listed above, e.g. AF31 (26), you must rewrite this DSCP value to 0 before sending the packet to Microsoft. Microsoft only sends packets marked with the DSCP value shown in the above table.