Instalar Lync Server 2013 Mediation Server

La implementación de Enterprise voice de Lync 2013 implica que dispondremos de una conexión a una PBX o bien a red pública directamente mediante un (direct) SIP trunk.

Para soportar esta implementación de Lync 2013 server se necesita instalar el rol Mediation server. El mediation server está conectado a la red interna (para conectarse al Lync 2013 Front-End server) y a la red externa (p.e. internet) para conectarse a un proveedor de red pública SIP.

En nuestro laboratorio haremos una conexión SIP trunk a un SBC de ACME.

El primer paso es configurar el Lync 2013 mediation server. Este estará en dominio “LYNC2013.LOCAL” de la red interna. A 2ndNIC is configured with direct internet connectivity so it has a public IP address.

Previamente se deberán instalar en el Lync 2013 Medation Server:

· Windows Management Foundation 3.0 (includo Powershell 3.0). WMF 3.0 es parte de Windows 2013, en Windows Server 2008 R2 SP1 es una descarga separada : http://www.microsoft.com/en-us/download/details.aspx?id=34595

· .NET Framework 4.5 (parte de Windows Server 2012) y se puede descargar en : http://msdn.microsoft.com/en-us/library/5a4x27ek(VS.110).aspx.

· Windows Identity Foundation para soportar autenticación “server to server”. Puede ser descargado en: http://go.microsoft.com/fwlink/p/?linkId=204657.

Instalación y configuración del mediation server

Primero se crea en Nuevo mediation en la topología. Ir al primer Lync Front-End server y abrir Topology Builder > download the topology from existing deployment y salvar la topología en el disco duro local.

Ir a Mediation pools bajo Lync Server 2013, click derecho en Mediation pools y seleccionar New Mediation Pool. Como los mediation se pueden agrupar en un pool introducer el nombre del Pool FQDN (pool.exchangelabs.nl) y seleccionar multiple computer pool o un solo servidor según queramos implementar uno u otro.

Tendremos inicialmente solo un mediation server en el pool, introducir local computer FQDN (p.e. POOLFE1.LYNC2013.LOCAL)

El Mediation pool apunta como siguiente paso al lyncpool, en nuestro caso POOLFE1 como next hop server, seleccionar Next hop pool.

Y como siguiente paso externamente será el SBC:

Click Finish to end the New Edge Pool wizard and to save all information in the local file. The configuration is now ready to be published into the CMS:

The mediation pool with the first mediation server is now stored in the configuration database and we can now continue with installing the actual Lync 2013 mediation server.

The installation of the Lync 2013 mediation server is not very different than other Lync server roles. Install the Lync 2013 core components from the DVD and once installed start the Deployment Wizard. In the Deployment Wizard select Install or Update Lync Server System.

Step 1: install Local Configuration Store and select Retrieve directly from the Central Management Store will install an instance of SQL Express on the mediation server and the contents of the CMS database will be copied into this SQL Express instance.

And Step 2: Setup or Remove Lync Server Components will install the actual Lync server 2013 Mediation Server.

Step 3: Request, Install or Assign Certificates will let your request an internal SSL certificate using the Active Directory Certificate Authority. Click Run and on the certificate wizard click Request. The certificate wizard is started, select Send the request immediately to an online certification authority (this is the default) and select the CA that will issue the certificate (it will find the CA in Active Directory):

Follow the wizard, enter a friendly name (something like Lync Internal Certificate) , enter the name of the organization and the department and enter the country, state/province and city/locality information. The wizard will automatically come up with the name of the mediation pool as the Subject Name (i.e. mediation.exchangelabs.nl) and the local FQDN in the Subject Alternative Names field. If needed you can add additional names for the Subject Alternative Names field.

When the wizard is finished an SSL certificate is automatically requested, issues and downloaded to the local certificate store of the mediation server.

When you click Finish the Certificate Assignment wizard is automatically started. Nothing to configure here, just informational windows. Finish the wizard and close the certificate wizard.

Select Step 4: Start Services to start the Lync 2013 mediation services on this server and use Service Status (Optional) to check if the services are running. There are only three services:

· Lync Server Mediation;

· Lync Server Centralized Logging Service;

· Lync Server Replica Replicator Agent;

Note. Make sure you got your name resolution ok so all servers can find each other, especially when using both external names (mediation.exchangelabs.nl) and internal names (medation01.wesselius.local). Also have a look at the binding order of both network interfaces. If set in the wrong order the mediation server will look for the front-end pool via the external interface (since this is published via the TMG server) instead of the internal network interface!

When you logon to the Front-End server and open the Lync Control Panel you’ll that the Mediation Server is up-and-running and that replication is running fine.

¡Ya tenemos conectado el Mediation Server con un SIP trunk!

Configuring the SIP trunk

El SIP trunk se usará contra el SBC de ACME.

Se pueden configurar multiples SIP trunks en el Mediation Server contra diferentes proveedores de servicios. La señalización entre servidor y proveedor usa el Puerto 5060 (TCP), usado para iniciar llamadas entrantes y salientes. Además el Mediation Server usa los puertos 60.000~65.536 (UDP) para audio stream. Se deben abrir estos puertos en el firewall entre el Mediation Server y el servidor de SIP (en nuestro caso el SBC).

Para configurar el SIP trunk, logarse en el Front-End Server y abrir el Topology Builder. Download the latest topology del CMS y guardarla en el disco duro.

En Topology Builder, expander Mediation pools y seleccionar properties del mediation pool (mediation.exchangelabs.nl). En las propiedesdes de PSTN Gateway , marcar el cuadro Enable TCP port y cambiar el Puerto TCP port al 5060 (por defecto es 5068!), pero esto dependerá de con que puerto trabaje el proveedor de servicios!

Click OK to continue. In the Topology Builder, expand the Shared Components, right-click PSTN gateways and select New IP/PSTN Gateway. In the Define New IP/PSTN Gateway enter the IP address of the PSTN Gateway, this is the IP address of the server (or Session Border Controller, SBC) at the SIP trunk provider. This is provided to you by the provider when you signed up for the service.

Side note. I have entered the IP address instead of the FQDN. Initially I used the FQDN and this worked fine for outbound calls, but during inbound calls the mediation server got confused and this resulted in a message like “the number you have dialed is not responding”. During troubleshooting with the OCSLogger and Snooper I found “SIP/2.0 400 Bad Request” and “10013;reason=”Gateway peer in inbound call is not found in topology document or does not depend on this Mediation Server”” in the log files.

For the communication between the mediation server and the SIP trunk provider I limit the service usage to the external network interface of the mediation server.

When the PSTN Gateway is created in the topology a SIP trunk is automatically created in the Topology Builder. Depending of your SIP trunk provider you may have to change the SIP Transport Protocol from TLS to TCP. In our environment the listening port also has to be changed from 5066 to 5060.

The wizard is now finished and when you click OK you will return to the Topology Builder and you can publish the topology to the CMS.

Configuración de enrutamientos de voz (voice routing)

Una vez se haya replicado la configuración del CMS con todos los servidores, puede tardar unos minutos. También se puede forzar la replicación ejecutando desde power shell de lync el siguiente commando:

Gpupdate /force

Abrir el Lync 2013 Control Panel y comprobar la nueva configuración:

El siguiente paso será configurar la ruta de Voz y el Dialing Plan.

En la parte izquierda de la pantalla seleccionar Voice Routing, en la pestaña Route borrar la ruta que aparece por defecto default LocalRoute y crear una nueva ruta. Dar un nombre a la nueva ruta. En la sección associated trunks pulsar Add y select the trunk que se creó en el paso anterior.

Pulsar OK y desplazarse hasta hasta la parte inferior de la pantalla, en Associated PSTN Usages seleccionar Long Distance.

Pulsar OK dos veces y click en Commit, seleccionar Commit All y en Uncommitted Voice Configuration Settings pulsar OK y Close.

En un Dialing Plan de Lync la numeración marcada por los usuarios se transforma a format E.164. Por ejemplo, se puede marcar un número interno 2131 y convertirlo automaticamente al formato +34917322131. O un número nacional 91231604557 se convierte a +3491231604557.

En voice routing seleccionar la pestaña dial plan y abrir global plan. Por defecto tiene una sóla regla de normalización. Desplazarse hasta associated normalization rules y hacer click en New y rellenar las propiedades.

En la parte inferior, en dialed number to test introducir un número de teléfono y al pulsar Go vemos el número en formato E.164 en el que se transformará.

OK dos veces y commit. Seleccionar commit all y OK. Cerrar la nueva ventana Successfully published voice routing configuration.

Por último se configurará una Política de Voz (Directivas de Voz). En el menú Voice Routing seleccionar la pestaña Voice Policy y abrir Global Policy. En associated PSTN usages click select and select the Long Distance PSTN Usage Record that was configured in the previous steps.

Click OK, click Commit, select Commit All, click OK and on the Successfully published voice routing configuration click Close.

The Lync enterprise voice configuration is now complete and we can enterprise voice enable users in the Lync 2013 control panel. In the Lync control panel select a user and open its properties. In the Telephony drop down box select Enterprise Voice and in the Line URI enter a telephone number (in the SIP trunk range of course). This phone number should be in the tel:+31201234567 format.

When you logon with the Lync client (works with Lync 2010 and Lync 2013 clients) you’ll see a new phone button in the menu ribbon with a dial pad. You should now be able to make phone calls via the SIP trunk.

Summary

In the previous posting I explained how to setup a Lync front-end server, and edge server and how to configure a SIP trunk using a mediation server. One more option remains, the Exchange Unified Messaging role to have voicemail functionality. This will be subject a future blog post.

On the Lync team blog there’s also an excellent blog post written by Brian Ricks on how to configure a IntelePeer SIP trunk on Lync Server 2010, including more detailed information on create multiple (US based) normalization rules:

http://blogs.technet.com/b/drrez/archive/2011/04/21/configuring-an-intelepeer-sip-trunk-solution-in-lync-server-2010.aspx