Pages

Saturday, 7 February 2015

Installing a Lync Server 2013 lab with PBX and PSTN using Asterisk

For this lab I will be using the following:

- x1 Windows Server 2012 VM with 4GB of RAM (Lync1 / Lync Frontend)
- x1 Windows Server 2012 VM with 4GB of RAM (DC01 / Domain Controller with AD Certificate Services)

- LS-E-8308.0-enUS.iso

We will firstly install the prerequisites for Lync:
Import-Module ServerManager
Add-WindowsFeature RSAT, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Scripting-Tools, Web-Windows-Auth, Web-Asp-Net, Web-Log-Libraries, Web-Http-Tracing, Web-Stat-Compression, Web-Default-Doc, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Errors, Web-Http-Logging, Web-Net-Ext, Web-Client-Auth, Web-Filtering, Web-Mgmt-Console, Web-Asp-Net45, Web-Net-Ext45, Web-Dyn-Compression, Web-Mgmt-Console, Desktop-Experience, Windows-Identity-Foundation, NET-WCF-Services45, NET-WCF-HTTP-Activation45

We will also install Microsoft Silverlight as the Lync administration interface is based on this.

We will now run the installer from our ISO, follow the setup instructions (e.g. prepare AD schema, dependencies etc.)


Once the Active Directory Preparation stage has finished the final step is to then populate the appropriate administrative users for Lync in the "CSAdministrators" security group:


We will not go back to the main installation menu and select the "Prepare first Standard Edition" button in the top right-hand corner:


 Now we will setup the relevant zone records in A.D. We will firstly create a SVR record to identify the SIP service offering as below:


And also the following A records that are used as part of the Lync offering:
meet - <frontend server ip>
admin - <frontend server ip>
dialin - <frontend server ip>


Now back on the Lync installer we will now select "Install Administrative Tools" in the top right hand corner of the view - this will install the Topology Builder (that allows you to create the foundations of your Lync system.) Now launch the Lync Topology Builder and we will create a new topology:







Follow the rest of the Wizard, by choosing the relevant domains, sites etc. It is also worth noting that Lync does not utilize Active Directory Sites and Services internally and rather has it's own sites system.

You should now be presented with the "New Front End Pool" wizard as below:





 We will enter the FQDN for the front end server - in this case the current server (Lync1):





 We will also install the features chosen below (Enterprise Voice refers to the ability to perform calls outside of your organization e.g. to a PSTN):



We will also have the option to install the Mediation Server on the same box as the frontend - which in this case we will as we are working with a lab - although for performance and quality reasons in a live environment you might prefer to install this role on an additional server.
(The mediation server translates all of the signalling between the Enterprise Voice and PBX, more information can be found here: https://technet.microsoft.com/en-us/library/gg398399.aspx )





It is also worth noting that Lync Standard only supports local user storage on an instance of SQL Express, if you wanted to setup clustering or place the database on a specific host you would have to purchase the enterprise edition.

The rest of the Wizard is pretty self-explanatory - upon completing it you should have view similar to the following:


 

 We will then select the root element in the tree (Lync Server) and select "Action" and "Edit Properties", we will then select "SIP Domain" from the left tab and enter https://admin.<domain-name> within the "Administrative Access URL":



We can now finally publish our Topology: Action >> Publish Topology (Although mine had a few errors, these were only file permission issues associated with the file share we specified in the earlier wizard that were easily resolved):



And then install the Lync server through the Deployment Wizard ("Install Lync Server" from the main menu - following steps 1 to 4):






During Step 3 you are required to specify the Root CA, so we point it too our Enterprise Root CA in AD:




Finally we can launch the "Lync Server Control Panel" from the start menu:






For non-Lync devices i.e. pure SIP, you can use http://www.kaplansoft.com/teksip/lyncproxy.html
http://www.beardy.se/how-to-set-up-a-sip-trunk-in-the-asterisk-pbx

No comments:

Post a Comment