Lync 2010 Deployment Guide (Edge role with 3 IP addresses)

Now that I have verified Edge configuration with singe IP address, let’s look now a configuration with three separate IP addresses would look like.

***One so misleading message! It should read “If the external IP address of the AV interface of this pool is translated by NAT…”

***Because we will use unique IP addresses for each service, we can safely leave the default ports here.

***Alert! This is the MOST often omitted OR misunderstood part. It should read “Because the external IP address of the Edge’s AV interface is translated by NAT…”. Here we will enter the Public routable IP address which will be mapped to the internal IP, assigned to AV service.

 

Looks good and so I can proceed with the steps described in earlier posts to publish the topology, expert it to .zip file, import it to my edge, configure the firewall, and make the changes necessary in my public DNS.

Lync 2010 Deployment Guide (adding Edge Role - part II)

Of course, first we must add our Edge server in Topology Builder first and publish the topology.

*** Note that is used here the internal FQDN (edgeint.drago.local)

Here we use the DMZ IP address which we will later map to Public IP address on our firewall

…and now we enter the Public IP address mapped to 10.20.50.50

The next hop is out only Lync FE server in the deployment.

…and mark our pool for external media traffic.

Let’s recap what we have done so far, because this is VERY important and misunderstanding this ultimately will lead to problems later!

• 1.        Our internal server FQDN is exdgeint.drago.local
• 2.       The internal IP address (typically in DMZ) is 10.20.50.5
• 3.       The Federation is enabled, thus we MUST have _sipfederationtls._tcp.drago.ws SRV record pointing to the A Record of sip.drago.ws (75.91.122.236) in our Public DNS
• 4.       ***ALERT*** this is the IP address of the A/V service, where the media will flow later. This is the major pain point of every deployment where voice problems via the edge are observed.
• 5.       This is the port via which the Edge will receive Configuration update
• 6.       The next hope for this Edge server. If this server is not functional, our Edge will be pretty much useless
• 7.       The external FQDN used for External access (port 5061) and Federation (port 5061). This is my first deployment with single IP address, so we will see how it goes later.
• 8.       The IP address we will S-NAT and D-NAT to 75.91.122.236
• 9.       The Edge Access Port (will be used from external Lync clients to sign-in)
• 10.   Note that the port is different
• 11.   …and so this one

 Now we will publish the Topology. 

This will make all other servers (besides the Edge) aware of the change (new server added).