In an earlier blog post I wrote about Using an F5 LTM Load Balancer for Reverse Proxy with Lync 2013. This works fine for the domains that you have entered when configuring the Lync 2013 iApp in the F5.
If you have multiple SIP domains and thus multiple Simple URLs like meet.contoso.com, meet.fabrikam.com and meet.alpineskihouse.com it doesn’t work out-of-the-box and your Lync client will fail using these URL’s.
To get this working you have to manually configure the Lync Revese Proxy iRule in the F5. To do this you first have to disable Strict Updates, otherwise updating the iRule will fail (for security reasons this makes sense).
When Strict Updates is disabled navigate to the proper iRule as shown in the following figure:
You’ll notice that the initial FQDN’s are configured here, in our example for lyncweb, meet, dialin and lyncdiscover. To get this working for other URL’s just add the other domains and you’re done (and don’t forget the lyncdiscoverinternal name).
When done, don’t forget to enable Strict Updates again, just in case…
For a couple of week one of my customer was complaining about little hickups in their Lync 2013 environment. It was working, but every now and then they had these strange little issues. When I moved my own accounts to Lync Online I was not able to federate with this customer anymore so it was time to start investigating.
Continue reading Lync 2013 Replication not working
During a migration project I ran into a nasty issue where I was not able to perform any outbound calls via the mediation server and the SIP trunk. As soon as I entered a phone number in my Lync 2013 client and hit the ‘dial’ button the call failed, immediately.
Continue reading A call to a PSTN number failed due to non availability of gateways in Lync 2013
Ok, I couldn’t resist it… In my previous blog I wrote about publishing Lync services using a Kemp Load Master. Since I’m not married to Kemp (although you might think differently, and so does Marco 😉 I also have an F5 LTM up-and-running in my lab. Time to have a closer look at the F5 when it comes to reverse proxy with Lync 2013.
Again, in my lab I have a Lync 2013 Enterprise Edition, in the perimeter network I have a Lync 2013 Edge Server, but I will use an F5 LTM load balancer.
Continue reading Using an F5 LTM Load Balancer for Reverse Proxy with Lync 2013
In my previous blog I wrote about publishing Lync services using IIS/ARR as a replacement for TMG 2010. It is also possible to use a hardware load balancer to publish these Lync web services to the internet. In this blog I’ll talk about using a Kemp LoadMaster LM2600 for publishing Lync web services.
In my lab I have a Lync 2013 Enterprise Edition, in the perimeter network I have a Lync 2013 Edge Server, but instead of IIS/ARR I now have a hardware load balancer.
Continue reading Using a Kemp Load Balancer for Reverse Proxy with Lync 2013