The above group policy settings modify the following three registry keys: When utilizing the OCS 2007 R2 infrastructure, you would use Group Policy to configure Media Port restrictions. When migrating to Lync Server 2010, you can use Lync 2010 Client or the Office Communicator 2007 R2 Client. Set-CsConferencingConfiguration -ClientMediaPortRangeEnabled 1 Legacy Clients In order to allow Lync to push the information on port restrictions to client’s, you must first enable Lync Server to do so by running the following command: You can read up on how Client Policies work on my previous article here. OCS 2007 R2 utilized Group Policies to set these options whereas in Lync, it uses Client Policies which in turn, provide Lync clients settings via in-band provisioning. This is very different than how it was configured in OCS 2007 R2. But what if you don’t want this entire port range open between your sites? You can utilize in-band provisioning to limit the amount of ports that are being used. If you want users to utilize peer to peer audio while internal to the network, you must ensure that this port range is open even if users are in different sites. Later in this article, when we take a look at Set-CSConferencingConfiguration, we take a look at the default ports. The ports that are actually utilized by default start at 5350. It’s just that it’s supported to utilize that entire range. If you do a Get-CSConferencingConfiguration you will actually see that they’re not using that entire range. At least that’s what the documentation says as you can see here. The ports utilized here are TCP/UDP 1024-65535. The first thing to understand is that in Lync Server 2010, when a user attempts to activate any type of audio and/or video, they first attempt a peer to peer session. Media Ports and Restricting Amount of Ports Being Used
PORTS FOR SKYPE FOR BUSINESS HOW TO
For specific requirements on what is required for QoS and how to enable QoS itself, please see the following article I wrote on QoS here. This article focuses on all dynamic port ranges regardless of whether or not it would be required for QoS.
PORTS FOR SKYPE FOR BUSINESS UPDATE
Update : As of, several (not all) parts of the article that refer to QoS concepts have been removed from this article. How do we configure Lync Server 2010 to restrict port usage for various modalities? How can we configure this for legacy clients? How can we configure this for native Lync Clients? How about when you do a peer to peer with both users being internal to the network? How about both users being external to the environment and connecting through the Edge? How about when you do a peer to peer with one user being internal and one user being external? Want to know? Read on…
For example, what servers and ports are utilized when doing Audio/Video through legacy clients or Lync 2010 based clients.
There aren’t really any places out there that describe how the media session works in different circumstances for Lync Server 2010. You will also see that the second half of this article is identical to Office Communications Server 2007 R2 as the method in which clients connect is identical. If you have read my Office Communications Server 2007 R2 article, you will see the first part of this article will show that the methods in which you restrict ports and the amount of flexibility in Lync Server 2010 has vastly changed. There are several ways in which we can utilize Audio/Video streams in Lync Server 2010. Read the Office Communications Server 2007 R2 version of this article here.
0 kommentar(er)
