![]() Microsoft is petty and petulant, and they don't specifically disable the transparent feature that can only help people in the free version. Unfortunately it is only Skype for Business that tags it's different classes of traffic. ![]() This, again, is also wrong - as you'll mistakenly classify both audio and video as the same priority. Others might also suggest using QoS policy ( gpedit.msc) to apply a DSCP policy to Skype.exe. Obviously trying to classify Skype traffic by the ports it communicates on is wrong, because then you would mistakenly classify both audio and video into the same priority class - thus defeating the entire purpose of QoS. ![]() If your firewall restricts access to these ports, check your firewall or security software settings or check with your system administrator. Others might suggest trying to classify Skype traffic by ports (to the point that they might even complain that Skype uses random ports that make it more difficult to find). For the best possible call quality experience, these ports are needed too: 1000-10000/TCP 50000-65000/TCP 16000-26000/TCP Make sure your firewall or security software is configured correctly with these ports. I guess you make sure everyone used the same port for Skype, that would help, but this isn't something I have tried. That's the problem - Skype will either use port 80, 443 or a random port (you can change it) for communication. Video: AF41 (Assuring Forwarding 41, DSCP 34) - class 4, low drop probability If you can set the incoming and outgoing port SKYPE uses, then you can QOS it.Audio: EF (Expedited Forwarding, DSCP 46) - low delay, low loss and low jitter. ![]() Skype for Business already automatically tags its two different kinds of traffic with a Differentiated Services Code Point (DSCP): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |