Export (0) Print
Expand All

Deployment Process for Dial-In Conferencing

 

Topic Last Modified: 2012-04-09

The components required for dial-in conferencing are deployed when you deploy the Conferencing workload. Before you can configure dial-in conferencing, you need to deploy either Enterprise Voice or a Mediation Server and a public switched telephone network (PSTN) gateway.

All the steps in the following table must be performed before users can dial in from the PSTN to join an audio/video conference.

noteNote:
If you are migrating from Office Communications Server 2007 R2, you must apply at least Cumulative update for Office Communications Server 2007 R2: January 2012 to your Office Communications Server 2007 R2 environment before deploying dial-in conferencing. Cumulative update for Office Communications Server 2007 R2: January 2012 supports participants dialing Office Communications Server 2007 R2 access numbers to join Lync Server 2010 conferences.

Dial-in Conferencing Deployment Process

Phase Steps Permissions Deployment documentation

Create a topology that includes the Conferencing workload, including a Mediation Server and PSTN gateway, and deploy the Front End pool or Standard Edition server.

  1. Run the Planning Tool to configure your topology, and export the topology into Topology Builder. While configuring the topology, select the dial-in conferencing option.
  2. Publish the topology and deploy the Front End pool or Standard Edition server.
  3. If necessary, create a stand-alone Mediation Server and associate it with a PSTN gateway.
    noteNote:
    This step is required only if you do not deploy Enterprise Voice and do not collocate the Mediation Server with the Enterprise Edition Front End Server or Standard Edition server. If you deploy Enterprise Voice, you install and configure Mediation Servers and PSTN gateways as part of the Enterprise Voice deployment. If you collocate the Mediation Server, you install and configure the Mediation Server as part of the Front End pool or Standard Edition server deployment.

Domain Admins

RTCUniversalServerAdmins

Administrator

Configure dial plans

A dial plan is a set of phone number normalization rules that translate phone numbers dialed from a specific location to a single standard (E.164) format for purposes of phone authorization and call routing. The same phone number dialed from different locations can, based on the respective dial plans, resolve to different E.164 numbers, as appropriate to each location. If you deploy Enterprise Voice, you set up dial plans as part of that deployment, and you need to ensure that the dial plans also accommodate dial-in conferencing. If you do not deploy Enterprise Voice, you need to set up dial plans for dial-in conferencing.

Use the Microsoft Lync Server 2010 Control Panel or Lync Server Management Shell to set up dial plans as follows:

  1. Create one or more dial plans for routing dial-in access phone numbers.
  2. Assign a default dial plan to each pool. Set the Dial-in conferencing region to the geographic location to which the dial plan applies. The region associates the dial plan with dial-in access numbers.

RTCUniversalServerAdmins

CsVoiceAdministrator

CsServerAdministrator

CsAdministrator

Configure Dial Plans for Dial-in Conferencing

Ensure that dial plans are assigned regions

Run the Get-CsDialPlan and Set-CsDialPlan cmdlets to ensure that all dial plans have a region assigned.

RTCUniversalServerAdmins

CsVoiceAdministrator

CsServerAdministrator

CsAdministrator

Ensure Dial Plans Have Assigned Regions

(Optional) Verify or modify user personal identification number (PIN) requirements.

Use Lync Server 2010 Control Panel or Lync Server Management Shell to view or modify the Conferencing PIN Policy. You can specify minimum PIN length, maximum number of logon attempts, PIN expiration, and whether common patterns are allowable.

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

(Optional) Verify PIN Policy Settings

Configure conferencing policy to support dial-in conferencing.

Use Lync Server 2010 Control Panel or Lync Server Management Shell to configure Conferencing Policy settings. Specify whether:

  • PSTN conference dial-in is enabled.
  • Users can invite anonymous participants.
  • Unauthenticated users can join a conference by using dial-out phoning. With dial-out phoning, the conference server calls the user, and the user answers the phone to join the conference.

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

Configure Conferencing Policy for Dial-in

Configure dial-in access numbers

Use Lync Server 2010 Control Panel or Lync Server Management Shell to set up dial-in access numbers that users call to dial in to a conference, and specify the regions that associate the access number with the appropriate dial plans. The first three access numbers for the region specified by the organizer's dial plan are included in the conference invitation. All access numbers are available on the Dial-in Conferencing Settings webpage.

noteNote:
After you create dial-in access numbers, you can use the Set-CsDialInConferencingAccessNumber cmdlet to modify the display name of the Active Directory contact objects so that users can more easily identify the correct access number.

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

Configure Dial-in Conferencing Access Numbers

(Optional) Verify dial-in conferencing settings

Use the Get-CsDialinConferencingAccessNumber cmdlet to search for dial plans that have a dial-in conferencing region that is not used by any access number and for access numbers that have no region assigned.

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

CsViewOnlyAdministrator

CsHelpDesk

(Optional) Verify Dial-in Conferencing Settings

(Optional) Modify key mapping of DTMF commands

Use the Set-CsDialinConferencingDtmfConfiguration cmdlet to modify the keys used for dual-tone multifrequency (DTMF) commands, which participants can use to control conference settings (such as mute and unmute or lock and unlock).

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

(Optional) Modify Key Mapping for DTMF Commands

(Optional) Modify conference join and leave announcement behavior

Use the Set-CsDialinConferencingConfiguration to change how announcements work when participants join and leave conferences.

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

(Optional) Enable and Disable Conference Join and Leave Announcements

(Optional) Verify dial-in conferencing

Use the Test-CsDialInConferencing cmdlet to test that the access numbers for the specified pool work correctly.

RTCUniversalServerAdmins

CsServerAdministrator

CsAdministrator

(Optional) Verify Dial-in Conferencing

Deploy Online Meeting Add-in for Microsoft Lync 2010

Deploy the Online Meeting Add-in for Microsoft Lync 2010 so that users can schedule conferences that support dial-in conferencing. The Online Meeting Add-in for Microsoft Lync 2010 is installed automatically when you install Microsoft Lync 2010

Administrators

Deploy the Online Meeting Add-in for Microsoft Lync 2010

Configure user account settings

Use Lync Server 2010 Control Panel or Lync Server Management Shell to configure the telephony Line URI as a unique, normalized phone number (for example, tel:+14255550200).

RTCUniversalServerAdmins

CsAdministrator

CsUserAdministrator

Configure User Account Settings

(Optional) Welcome users to dial-in conferencing and set the initial PIN

Use the Set-CsPinSendCAWelcomeMail script to set users' initial PINs and send a welcome email that contains the initial PIN and a link to the Dial-in Conferencing Settings webpage.

RTCUniversalServerAdmins

(Optional) Welcome Users to Dial-in Conferencing

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft