- Lync Server Cookbook
- Fabrizio Volpe Alessio Giombini Lasse Nordvik Wed? António Vargas
- 471字
- 2021-08-06 19:28:35
Enhancing conferencing security
Conferencing, in Lync Server 2013, has the same default security configuration that we had in Lync Server 2010. Justin Morris, in a post dedicated to Lync Server 2010 conferencing (http://www.justin-morris.net/understanding-conference-security-in-lync-server-2010/), pointed out some of them, including the fact that every Lync user has a meeting URL and a conference ID that never changes by default, and that users invited to a meeting using a PSTN line have the ability to bypass the lobby. If we always use the same conference ID, people outside our company whom we have invited in the past could use it with malicious motivations, or different (unrelated) conferences with different people could merge if our time schedule is not perfect. We will list some steps to improve conferencing security, including a couple of cmdlets from the previously mentioned post.
How to do it...
- We can start assessing the security configuration of conferencing for our Lync deployment using
Get-CsMeetingConfiguration
. - To disable the lobby bypass for PSTN users, use the following cmdlet:
Set-CsMeetingConfiguration -PstnCallersBypassLobby $false
- To force users to schedule private meetings (with unique IDs), use the following cmdlet:
Set-CsMeetingConfiguration -AssignedConferenceTypeByDefault $false -EnableAssignedConferenceType $true
- Then, we have to work on the conferencing policies. The default global policy allows almost any of the available conferencing features. I suggest that you clone it using
New-CsClonedPolicy
from Pat Richard (http://www.ehloworld.com/2300). This script is useful to create a new user-conferencing policy called, for example,DefaultConferencing
, which will have the same parameters we had in the global policy. The cmdlet we will use is the following one:.\New-CsClonedPolicy.ps1 -SourcePolicyName global -TargetPolicyName "DefaultConferencing" -PolicyType ConferencingPolicy
- Restrict the global conferencing policy to match the minimal level of service we will grant to every Lync-enabled user.
- To enhance conferencing security, we can also restrict the number of TCP ports involved in the client communication. Launch the
Get-CsConferencingConfiguration
cmdlet to look at the applied configuration. IfClientMediaPortRangeEnabled
isFalse
, then the clients will use a port between ports1024
and65535
when involved in a communication session. We can use the following cmdlet to force port range (default will be starting from TCP port5350
for all the kind of network traffic):Get-CsConferencingConfiguration | Set-CsConferencingConfiguration -ClientMediaPortRangeEnabled $True
How it works...
As we said, the cmdlet shown in step 6 will use the same TCP port for all the network traffic involved in the clients' communication. We can refer to Chapter 11, Controlling Your Network – A Quick Drill into QoS and CAC to also implement Quality of Service (QoS) and Call Admission Control (CAC).
See also
I suggest that you also read a second post from Justin Morris, which is related to the unique conference IDs, Why You Should and Shouldn't Configure Unique Conference IDs in Lync (http://www.justin-morris.net/why-you-should-and-shouldnt-configure-unique-conference-ids-in-lync/#sthash.W9h9mCzn.dpuf). This post examines the pros and cons of the solution outlined in the previous document in depth.
- AngularJS Testing Cookbook
- Ceph Cookbook
- Debian 7:System Administration Best Practices
- Learn WebAssembly
- Unity Shader入門精要
- Advanced Express Web Application Development
- Python:Deeper Insights into Machine Learning
- Orchestrating Docker
- Windows Phone 8 Game Development
- 深入實踐DDD:以DSL驅動復雜軟件開發
- Unity 2017 Game AI Programming(Third Edition)
- 深入分析GCC
- jQuery從入門到精通(微課精編版)
- Java并發實現原理:JDK源碼剖析
- MongoDB Cookbook