Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Dial-in Conferencing Configuration Prerequisites and Permissions

 

Topic Last Modified: 2012-06-20

Dial-in conferencing is an optional component of the Lync Server 2013 Conferencing workload. The components you need to install before you can configure dial-in conferencing are deployed when you use the Topology Builder to design your topology and then set up your Front End pool or Standard Edition server. This topic describes what you need to have accomplished before you can configure dial-in conferencing.

This section assumes that you have read the planning sections related to the Conferencing workload and dial-in conferencing in particular.

Dial-in conferencing requires the following Lync Server 2013 components:

  • Unified Communications Application Service (UCAS) (called the Application service)
  • Conferencing Attendant application
  • Conferencing Announcement application
  • Dial-in Conferencing Settings webpage
  • At least one Lync Server 2013 Mediation Server and at least one PSTN gateway

You deploy these components when you use the Topology Builder to define and publish your topology and then deploy a Front End pool or a Standard Edition server. If you are deploying Enterprise Voice, you should deploy it before you configure dial-in conferencing. If you are not deploying Enterprise Voice, you can deploy a Mediation Server and a public switched telephone network (PSTN) gateway when you deploy your Front End pool or Standard Edition server.

noteNote:
If you are upgrading from Office Communications Server 2007 R2 to Lync Server 2013, deploy dial-in conferencing in every pool that you plan to use to host Lync Server 2013 conferences. For details about migrating dial-in conferencing, see Migration from Office Communications Server 2007 R2 to Lync Server 2013.

This section assumes that you have done the following:

  • Applied the latest updates to your Office Communications Server 2007 R2 environment, if you are migrating to Lync Server 2013.
  • Used Topology Builder to design and configure your topology. While specifying the Conferencing workload, you selected the dial-in conferencing option. For details about defining your topology, see Defining and Configuring the Topology in the Deployment documentation.
  • Published your topology, and set up the Front End pool or Standard Edition server. For details about publishing the topology and installing Lync Server 2013, see Deploying Lync Server 2013 in the Deployment documentation.
    noteNote:
    When you install your published topology, the Dial-in Conferencing Settings webpage is installed on the Front End Server or Standard Edition server as part of Web Services.
    importantImportant:
    If you change the path for the File Store in Topology Builder after you deploy Lync Server 2013, you need to restart the Conferencing Attendant and Conferencing Announcement applications to use the new path.
  • Deployed Enterprise Voice. If you are not deploying Enterprise Voice, you either collocated a Mediation Server on the Enterprise Edition Front End Server or the Standard Edition server, or you deployed a stand-alone Mediation Server, and you deployed a PSTN gateway. For details about deploying Enterprise Voice, see Deploying Enterprise Voice in the Deployment documentation. For details about installing a stand-alone Mediation Server and PSTN gateway, see Deploying Mediation Servers and Defining Peers in the Deployment documentation.

The following flowchart shows the steps that you must perform before you can configure dial-in conferencing and the steps that you perform to configure dial-in conferencing.

Dial-in Conferencing Deployment flowchart

To configure dial-in conferencing, you need to use the following administrative tools:

  • Lync Server 2013 Control Panel
  • Lync Server Management Shell

You use these administrative tools to configure dial-in conferencing settings, and the dial plans, policies, and other settings that dial-in conferencing requires.

Configuring dial-in conferencing requires any of the following administrative roles, depending on the task:

  • CsVoiceAdministrator   This administrator role can create, configure, and manage voice-related settings and policies.
  • CsUserAdministrator   This administrator role can enable and disable users for Lync Server and assign existing policies, such as conferencing policies and PIN policies, to users.
  • CsAdministrator   This administrator role can perform all of the tasks of CsVoiceAdministrator and CsUserAdministrator.
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.