#Lync web app setup audio device how to
#Lync web app setup audio device code
#Lync web app setup audio device windows

RFC2598 allocates a single DSCP value for all traffic in this classification as decimal 46 (hexadecimal 2E, binary 101110). Many networks will already be controlling EF traffic as well as limiting the total amount of bandwidth that EF traffic can consume on the network as if too much traffic is stamped with EF then assured delivery can become compromised. This class is ideal for real-time media as it provides a mechanism for reduced loss, delay, and jitter.

Expedited Forwarding (EF) is a single-value classification that is often granted the highest priority (below classification reserved for routing protocol traffic) and should be controlled through bandwidth management and call admission control policies on the network.

The DSCP decimal values are also identified for each AF classification as defined by RFC2597. The table below shows the multiple classes available to assign different traffic across the varying levels of prioritization available with AF.

Assured Forwarding (AF) is a group of 12 different levels of prioritization that assures delivery as long as this traffic does not exceed defined rates, as anything that exceeds this rate has an increased probability of being dropped.

Note how DSCP 40 is categorized as this will be discussed shortly. Multiple Precedence Levels are defined as per RFC791 and the following table shows the DSCP decimal values for each level.

Class Selector (CS) is a grouping of values that are backwards compatible with the pre-DiffServ method of prioritizing traffic called Type of Service (ToS).

Default is what unmarked traffic is classified as (using a null DSCP value) and is delivered on a best-effort bases just the same as all other non-prioritized traffic.

Set-CsUCPhoneConfiguration -Identity global -VoiceDiffServTag 0 DiffServ Classificationsīefore looking at the actual traffic it would be prudent to quickly review the different DiffServ classifications which are applicable to prioritizing media in Lync.

Run the Set-CsUCPhoneConfiguration cmdlet to specify the desired value for DSCP stamping or to disable the behavior by setting a value of 0.

Alternatively the same steps can also be performed from the Lync Server Management Shell by issuing the following cmdlet:.

This setting can be changed to 0 is disable DSCP tagging.

As shown the Voice quality of service setting is enabled and configured to a value of 40.

Using the Lync Server Control Panel browse to the Clients > Device Configuration section and view the properties of the default Global object.

#Lync web app setup audio device how to

The following steps show how to validate the default configuration in Lync and can be used to change the setting if desired. Once the QoS tagging was updated in Lync to the proper value then call quality returned to normal for all endpoints uniformly. The WAN routers were prioritizing traffic stamped with a DSCP value other than 40, so the 0 value traffic from the computers was being treated normally, but the 40 value traffic from the phones was being deprioritized, thus dropping a lot of packets of that traffic type.

#Lync web app setup audio device windows

In at least one field-engagement there were reported call quality issues between Lync Phone Edition devices in different sites across a WAN, yet anyone on the Windows Lync client was unaffected.

#Lync web app setup audio device code

Thus it is important to understand that Lync Phone Edition devices will stamp a Differentiated Services Code Point (DSCP) value of 40 on media traffic while the standard Lync client will leave this field null. In Lync Server, by default, Quality of Service (QoS) is not enabled for the Windows Lync soft client, yet it is enabled for Lync Phone Edition clients.