Поділитися через

Deploying Enterprise Voice in Lync Server 2013

  • Стаття

 

Topic Last Modified: 2012-10-03

Lync Server 2013, Enterprise Voice is part of the Lync Server 2013 infrastructure.

Deploying Enterprise Voice requires that you:

  1. Review the Planning for Enterprise Voice in Lync Server 2013 section of the Planning documentation.

  2. Finalize plans for features and components to deploy with this workload.

  3. Run Planning Tool to design a topology that reflects your deployment decisions.

  4. Open the topology design in Topology Builder, as described in Defining and configuring the topology in Lync Server 2013 in the Deployment documentation.

    Note

    Installation of Topology Builder is part of the deployment process for the internal pool. For details, see Install Lync Server 2013 administrative tools in the Deployment documentation.

Additionally, you must have already deployed Lync Server, Enterprise Edition at central sites and branch sites that correspond to the reference topology that you choose to deploy. You can’t deploy Enterprise Voice components until you have defined, published, and installed files for at least one internal pool, and you must use Topology Builder to define and publish an internal pool.

To view reference topologies with examples of where Enterprise Voice server roles can be deployed (and their relationship to one another and other Lync Server 2013 server roles), see Reference topologies in Lync Server 2013 in the Planning documentation.

To view a reference topology that illustrates and explains a sample call admission control deployment, including network regions, network sites, and subnets, see Example: Gathering your requirements for call admission control in Lync Server 2013 in the Planning documentation.

Important

To deploy Enterprise Voice at a central site, continue reading the topics in this section. To deploy Enterprise Voice at a branch site, skip to Deploying branch sites in Lync Server 2013 in the Deployment documentation.

This section includes procedures for deployments in which a Mediation Server is collocated on each Front End Server or Standard Edition server, as recommended, and also for deployments with a stand-alone Mediation Server pool.

You can skip the following content if you used Topology Builder to define and publish a topology that collocates a Mediation Server on each Front End Server or Standard Edition server, because Deployment Wizard already automatically installed the files for Mediation Server when you installed files for your Front End Server pool or Standard Edition server:

If you used Topology Builder to define and publish a Mediation Server in a stand-alone pool, you can use the following content:

In This Section