banner-ad

Lync QOS: DSCP Tagging and Testing for Various Vendor Endpoints

 

Setting up DSCP on the Lync Server and Lync client is done via group policy

Elan Shudnow has an excellent article on this so I won’t redo his work. Take a look here:
http://www.shudnow.net/2013/03/03/enabling-qos-for-lync-server-2013-and-various-clients-part/

LPE Edition

It will get its DSCP tagging values directly from Lync Server via the Device Configuration | Voice Quality of Service value:

clip_image001

snom UC Edition

NOTE: Still checking if snom UC Edition gets DSCP value from Lync Device policy. If you know, welcome your comment.

By default snom UC Edition devices are set to DSCP 40 (which matches Lync Server defaults). To change the DSCP value (or look what it is) log into snom web UI: (NOTE: the below snom device has been changed to DSCP 46 using snom TOS value of 184)

clip_image001[5]

Here is a chart to cross reference snom TOS value and standard DSCP dec values:

http://wiki.snom.com/FAQ/What_does_the_TOS_value_160_mean

image

Audiocodes 4xxHD Series

Voice Over IP | Signaling Protocols | QOS Parameter

image

Testing that the DSCP Tag is indeed in place:

Install Wireshark on the PC (to see traffic from Server) and/or Server.

Now expand the “Differentiated Services Field” under “Internet Protocol Version 4” and check the value pointed out in the picture below.

clip_image001[7]

http://www.tucny.com/Home/dscp-tos

No comments:

Post a Comment