Dial-in conferencing requires the following Communications Server 2010 components:

• Application service
  
  
• Conferencing Attendant
  
  
• Conferencing Announcement
  
  
• Dial-in Conferencing Settings Web page
  
  
• At least one Communications Server 2010 Mediation Server and at least one PSTN gateway
  
  

You deploy these components when you use Communications Server 2010 Planning Tool and Topology Builder to define and publish your topology and then deploy an Enterprise 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 PSTN gateway when you deploy your Enterprise pool or Standard Edition Server.

Note:
If you are upgrading from Office Communications Server 2007 R2 to Communications Server 2010, deploy dial-in conferencing in every pool that will host a Communications Server 2010 conference. For details, see Migration from Communications Server 2007 R2 to Communications Server 2010.

This section assumes that you have done the following:

• Applied at least Cumulative Update 5 (CU5) to your Office Communications Server 2007 R2 environment, if you are migrating to Communications Server 2010.
  
  
• Used the Planning Tool to configure your topology. While specifying the Conferencing workload, you selected the dial-in conferencing option. For details about defining your topology, see Design a Topology in the Planning Tool.
  
  
• Exported your topology into Topology Builder, published the topology, and set up the Enterprise pool or Standard Edition Server. For details about publishing the topology and installing Communications Server 2010, see Deploying an Enterprise Edition Pool.
  
  

  Note:
  When you install your published topology, the Dial-in Conferencing Settings Web page is installed on the Front End Server or Standard Edition Server as part of Web Services.

  Important:
  If you change the path for File Store in Topology Builder, 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 the Enterprise Voice Workload. For details about installing a stand-alone Mediation Server and PSTN gateway, see Deploying Mediation Servers and Defining Peers.
  
  

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 Permissions

Configuring dial-in conferencing uses the following administrative tools:

• Communications Server Control Panel
  
  
• Communications 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 Communications 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.
  
  

See Also

Concepts

Deploying the Enterprise Voice Workload

Other Resources

Dial-In Conferencing in Communications Server 2010
Deploying an Enterprise Edition Pool

---

Deploying dial-in conferencing