Share via

  • Article

Create a Voice Route to the Legacy Mediation Server using Lync Server Management Shell

 

Topic Last Modified: 2013-02-24

In order to use the Mediation Server that is used by Microsoft Office Communications Server 2007, you must configure Microsoft Lync Server 2010 to use this server.

If a voice route and voice policy existed in the legacy pool, after you merge Office Communications Server 2007 with Lync Server 2010 and run the Import-CsLegacyConfiguration cmdlet, the Lync Server 2010 pilot pool now has all the necessary configuration information to do the following:

  • Route outbound calls through the legacy Office Communications Server 2007 Mediation Server

  • Route inbound calls from the legacy pool to the Lync Server 2010 pool

Note

Lync Server 2010 Mediation Server features are not functional until you configure all Mediation Server components, which occurs later in this document. For details about configuring Lync Server 2010 Mediation Server, see Migrate Mediation Server (Office Communications Server 2007 Migration).

Note

For details about finding qualified public switched telephone network (PSTN) gateways, IP private branch exchanges (IP-PBX), and SIP trunking services that work with Lync Server 2010, see "Microsoft Unified Communications Open Interoperability Program" at https://go.microsoft.com/fwlink/p/?LinkId=206015.

To enable the Lync Server 2010 pilot pool to use the legacy Mediation Server, you must have a voice route and voice policy configured that point to the legacy Mediation Server. If you do not have a legacy voice route or voice policy, follow the procedure to configure these settings by using Lync Server 2010 Control Panel or by using the Lync Server Management Shell.

Note

The procedure that follows should be performed after the latest gateway firmware has been installed.

To create a voice route to the legacy Mediation Server by Using Lync Server Management Shell

  1. Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or that is assigned to the CsVoiceAdministrator administrative role.

  2. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

  3. Get the FQDN of the legacy Mediation Server by running the following command:

    Get-CsService -MediationServer

    The Identity parameter contains the name of the legacy Mediation Server. In this example, the value is MediationServer:medsvr01.contoso.net

  4. Next, verify that a voice policy exists for the legacy Mediation Server by running the following command:

    Get-CsVoicePolicy

    The PSTNUsages parameter should not be empty, but return a value of {Local} or the name of any custom PSTNUsage created on the legacy Mediation Server.

  5. After you verify that a legacy Mediation Server exists and it has a voice policy, create a route in the Lync Server 2010 pool that points to this legacy Mediation Server.

    The following code defines a generic voice route that routes any outbound calls from the Lync Server 2010 pool to the legacy Mediation Server.

    New-CsVoiceRoute -Name W12PSTNRoute -NumberPattern ".*" -PstnUsages Local -PstnGatewayList @{Add="MediationServer:medsvr01.contoso.net "}

  6. Finally, run the following command to set the default voice route for this pool.

    Set-CsVoiceRoute -Identity W12PSTNRoute -Priority 0

  7. Run the Get-CsVoiceRoute cmdlet to verify the voice route settings.

    For this example, the Identity parameter should be set to W12PSTNRoute. PSTNUsages should be set to {Local} and the PSTNGatewayList parameter should point to the FQDN of the legacy Mediation Server, Mediation:medsvr01.contoso.net.