2- Skype for Business Edge server deployment
and Hybrid integration with Skype for Business
Online
http://www.moh10ly.com/blog/VoIP/skype4business/skype-for-business-edge-server-deploymen
t-and-hybrid-integration-with-skype-for-business-online
In the last Skype for Business post I have upgraded my Lync 2013 to Skype for Business
(Click here to go to that post). in this article I am going to install Edge server for Skype for
Business to the same Lync Environment where I have done the Upgrade to Skype for Business.
Configuring Edge Server
Setup NETBIOS
In order to configure Skype 4 Business Edge, we'll have to change the Netbios to give it the name
of our Domain but we won't join it to the domain.
Setup NICs
Edge Server must have 2 NICs, one Local NIC will point out to the Front end server but must not
have Default gateway so traffic can only flow through the DMZ out to the internet and back in.
but still it must be able to ping to the FE from Edge and vice versa.
DMZ network can have 1 DMZ address (Public Address to be NATTED to) or 3 DMZ addresses for
public IP addresses with standard HTTPS ports.
Configure Hostnames
Edit the Edge server's host file to include Lync FE and DC's IP addresses and Hostname
Install Prerequisites
Microsoft .Net Framework 3.5
Now I will go back to Skype for Business FE server, I'll launch the topology builder and add new
Edge server
I will add the first Edge pool which contains of a single Edge server
Next, you will have to choose if you want to enable federation with partners or other service
providers …e.g. (Google)
I am intending to use a single Public IP address with a different ports (nonstandard) since this is a
lab. For production it's recommended to use 3 public IP addresses for Access Edge, AV and
WebConf services.
Next I will choose the last option which says that the Edge pool is translated by NAT. I will
configure my firewall to NAT ports to the Edge's DMZ IP addresses from the Public so I am
choosing this option.
This is the FQDN's the default configuration .. It'll only use a single FQDN for all services if you're
going to use a single public IP address with a different ports.
IMPORTANT NOTE
When you use a single IP address with a different ports, the Access Edge port will normally
change to 5061 (Not 443 like in the _sip._tls.domain.com) SRV record which will cause failure if
you forgot to change this port to match the one in your Topology's Access Edge settings.
Next I'll have to enter my Edge server's Local IP address.
Next I will be asked to enter the DMZ's IP address which the wizard calls (Private External IP
address)