Topic Last Modified: 2010-07-18
Follow the steps in this topic to use Topology Builder to define a standalone Mediation Server pool at a site for which you did not previously deploy Enterprise Voice. The steps in this topic also specify how to configure SIP listening ports on the Mediation Server by running Communications Server Management Shell.
If you already deployed Mediation Servers collocated on the Front End pools or Standard Edition Servers at this site, you can skip this topic as well as Install the Files for Mediation Server, and instead, continue to Configuring Trunks and Translation Rules.
Note: |
---|
This topic assumes that you have set up at least one internal Enterprise pool or Standard Edition Server as described in Defining a Front End Pool and Publishing a Topology. This topic also assumes that you have defined at least one peer with which you will associate the Mediation Server in order to provide PSTN connectivity as described in Define a Peer of the Mediation Server for a Site. |
You can define a topology using an account that is a member of the Administrators group.
To add a Mediation Server
-
Open Communications Server Topology Builder.
-
In Communications Server Topology Builder, in the console tree, expand the name of the site for which you want to define a Mediation Server.
-
In the console tree, right-click the Mediation Servers node, and then click Define Mediation Server.
-
In the Define Mediation Server Pool dialog box, type the Mediation Server pool FQDN.
-
Under Select the Pool to be used as the next hop, click the FQDN of the Front End pool that will use this Mediation Server pool.
-
Optionally, under Select Edge Pool used by this Mediation Server, click the FQDN of the Edge Server pool that will use this Mediation Server pool to provide PSTN connectivity to external users enabled for Enterprise Voice.
-
Click Next.
-
Click Add, type the FQDN of a computer to add to this Mediation Server pool, and then click OK. Repeat this step for all other Mediation Servers that you want to add to this Mediation Server pool.
-
Click Next.
-
In the list of peers that have been defined for the site, for all peers that you want to use with this Mediation Server pool, select the Used check box.
-
For the peer to which you want this Mediation Server pool to route calls from Microsoft Office Communications Server 2007 R2 Enterprise Edition or Standard Edition Servers to the PSTN, select the Default check box.
Note: Before you proceed to the next step, ensure that the Mediation Server pool and any computer that you added to the Mediation Server pool are running using the FQDNs that you specified. -
Next, follow the procedures in “Publish the Topology” to add the Mediation Server to the topology. You must publish your topology each time you use Topology Builder to build or modify your topology so that the data can be used to install the files for Communications Server servers. Then continue to the next steps to modify the listening ports on the Mediation Server, if necessary.
-
Open Communications Server Management Shell.
-
By default, the SIP listening ports on the Mediation Server are 5070 for TLS traffic from Communications Server, 5067 for TLS traffic from peers (gateways, PBXes, or SBCs). Optionally, run the following cmdlet to modify the SIP listening ports on the Mediation Server (replacing the value of the parameters with the service identity and ports for your topology):
Copy Code Set-CsMediationServer medsvr.contoso.net –SipServerPort 5061 –SipClientTlsPort 5062
The –SipServerPort parameter specifies the listening port for SIP messages from Communications Server and the –SipClientTlsPort specifies the listening port for SIP messages from the gateway that are sent using the TLS transport protocol.Obtain the value for the –Identity parameter by running:
Copy Code Get-CsService
Next, install the files on each Mediation Server in the pool by following the procedures in “Install the Files for Mediation Server”.