Connect Pilot Stack to Legacy Mediation Server

Topic Last Modified: 2011-04-06

In order to use the Mediation Server that is used by Microsoft Office Communications Server 2007, you must configure 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). For details about finding qualified public switched telephone network (PSTN) gateways, IP-PBXs, and SIP trunking services that work with Lync Server 2010, see "Microsoft Unified Communications Open Interoperability Program" at http://go.microsoft.com/fwlink/?LinkId=206015.

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).
For details about finding qualified public switched telephone network (PSTN) gateways, IP-PBXs, and SIP trunking services that work with Lync Server 2010, see "Microsoft Unified Communications Open Interoperability Program" at http://go.microsoft.com/fwlink/?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, complete the following steps to configure these settings by using Lync Server 2010 Control Panel or the Lync Server Management Shell.

To create a voice route to the legacy Mediation Server by using Lync Server Control Panel

Log on to the computer with an account that is a member of the RTCUniversalServerAdmins group or is assigned to the CsVoiceAdministrator administrative role.
Open a browser window, and then enter the Admin URL to open the Lync Server Control Panel. For details about the different methods you can use to start Lync Server Control Panel, see Open Lync Server Administrative Tools.
On the Select URL page, select the Standard Edition server or Front End pool that corresponds to your pilot stack deployment.
Click Voice Routing, and then click the Route tab.
Click New to create a new voice route.
Fill in the following fields:
- Name: enter a descriptive name for the voice route. For this document, we will use W12PSTNRoute.
- Description: enter a short description of the voice route.
Skip all remaining sections until you reach Associated gateways, and then click Add. Select the default gateway listed, and then click OK.
Under Associated PSTN Usages, click Select.
From the Select PSTN Usage Record page, select the legacy Mediation Server FQDN, and then click OK.
From the New Voice Route page, click OK to create the Voice Route.
From the Voice Routing page, select Route.
Move the newly created route to the top of the list, and then click Commit.

For details about creating a Voice Route to the legacy Mediation Server by using the Lync Server Management Shell, see Create a Voice Route to the Legacy Mediation Server using Lync Server Management Shell.