Client Configuration

QoS tagging of the media is performed by the Lync client itself, so it must be provisioned in a way that it understands what ports to use for each type of traffic. By default, no tagging is done and all traffic uses the port range 5350–5389. The Lync client supports using different port ranges for the following types of traffic and recommends using a minimum of 20 ports per modality. This roughly translates to 20 concurrent calls per modality, which should be more than enough for any single endpoint.

First, to enable separate port ranges for each media type, run the following command:

Set-CsConferencingConfiguration -ClientMediaPortRangeEnabled $true

Next, define a unique port range for each type of traffic. As an example, the ports used on the client side can be the same as those on the server. The sample numbers used here are well beyond the minimum number of ports required and are used only to show how the default port ranges can be moved. The port ranges used should be limited to the recommended sizes for ease of management and troubleshooting.

Set-CsConferencingConfiguration -ClientAudioPort 500020 -ClientAudioPortRange 20 -ClientVideoPort 58000-58019 -ClientVideoPortRange 20 -ClientAppSharingPort 40803 -ClientAppSharingPortRange 20 -ClientFileTransferPort 40783 -ClientFileTransferPortRange 20