Forum Discussion
Client log doesn't detect QoS
When QoS is enabled via GPO, the log when viewed with Snooper shows qosEnabled as false, but a wireshark trace shows the DSCP on the packet as 46.
Wireshark:
Snooper:
7 Replies
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 ?
- TrentIron Contributor
Yes, same issue - the snooper log doesn't show qosenabled status properly if you are using Skype for Business Online - only works with Server.
Just to confirm you have enabled QoS in the onpremises server media configuration?
Set-CsMediaConfiguration –EnableQoS $true –EnableInCallQoS $True
- David PhillipsIron Contributor
Michael LaMontagne wrote:Just to confirm you have enabled QoS in the onpremises server media configuration?
Set-CsMediaConfiguration –EnableQoS $true –EnableInCallQoS $True
I think this is a misspelling and is really supposed to read -EnableInCallQoE and -InCallQoEIntervalSeconds. It wouldn't have anything to do with QoS.
http://ucken.blogspot.com/2015/07/in-call-qoe-in-skype4b.html
- TrentIron Contributor
Skype for Business Online - no on-prem.