What port does skype use qos software#
Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
The sites are not controlled by Microsoft. Note: Microsoft is providing this information as a convenience to you. In addition, we will share a link with you: For this issue, please check if the correct port has been used for other application when presenter to conference or conference to participant. As soon as you want to implement GPO based QoS it's recommended to use separate port rangesįrom troubleshooting this issue, please tell us more details about SFB server infrastructure in your organization.Īs I am concerned, the client should use the correct port for source and destination. You will not have any troubles, as long as you use the default AppSharing port range on the server (49152-65535) because this range overlaps with audio and video. This have to be considered when defining firewall rules between client and server and also for QoS GPOs.įor me, it seems the Technet article to not cover the correct port ranges or the conferencing server do not offer the correct ports (from video port range instead of AppSharing port range). We changed the client and server port ranges to confirm this behavior.Īs soon as the client sends/receives VbSS over a conference, we have a mixture of the AppSharing Ports and Video Ports. Destination Port is correct from Client AppSharing Port Range UDP. Destination port seems to be wrong, it uses the Server Video Port Range UDP.Ĭonference to Participant: Source port seems to be wrong, it uses the Server Video Port Range UDP. Presenter to Conference: Source port is correct from Client AppSharing-Range UDP. The new feature VbSS (Video based Screen Sharing) seems not to use the correct port ranges in all cases:Ĭlient to Client (Peer2Peer): Source and destination ports are in the Client AppSharing-Range UDP=>OK Video: 57501-57540 (custom range) TCP and UDPĪppSharing: 40803-40842 (custom range) TCP, new also UDPįile Transfer: 40843-40882 (custom range) TCPįor Audio/Video/Desktop Sharing (RDP), it uses the correct source and destination ports in UDP and TCP (if UDP not possible). Video: 57501-65535 (default range) TCP and UDPĪppSharing: 40803-49151 (custom range) TCP, new also UDPĬlient: (Set-CsConferencingConfiguration)Īudio: 49152-49191 (custom range) TCP and UDP We defined the following port ranges to better handle QoS and defined the corresponding FW rules:Īudio: 49152-57500 (default range) TCP and UDP We use SfB 2016 Client full patched (September 2016) and SfB Server 2015 (CU3 June 2016). It seems VbSS uses not the correct ports in all cases.
I checked which ports VbSS really uses, because the most of our customers have firewall(s) between the clients in different subnets and/or to the SfB servers and we got some issues with VbSS.
0 kommentar(er)
