Forum Discussion
Client log doesn't detect QoS
You'll se a difference because the Policybased QoS policy adds the CoS information to the IP header, which happens at layer 3 (network layer), your Snooper looks at layer 7 (application layer) and has no idea, what so ever, to whats happening at the other layers.
If you were using SFB server, the Set-CsMediaConfiguration should set this (as Michael LaMontagne correctly points out), however that is not available for SFBO, and is neither applicable for Windows devices, who gets the setting from a GPO.
/Kenneth ML
Have you viewed this similar thread for Skype for Business Online: https://techcommunity.microsoft.com/t5/Skype-for-Business-IT-Pro/QoS-for-SfB-when-using-Cloud-PBX-and-PSTN-Calling/m-p/104087#M2821 ?
Yes, same issue - the snooper log doesn't show qosenabled status properly if you are using Skype for Business Online - only works with Server.
Hi Trent.
As I stated earlier in this thread, the CoS tag is not in the application layer, but in the network layer, so the application (and hence the Snooper log) has no idea this is happening on the Windows OS.
Without an ExpressRoute your received packets from Office 365 is not tagged this must then be done by your edge firewall or core switch based on a source address, source port and destination port combination.
