Forum Discussion
boneyard
MVP
MVPLync iApp - only reverse proxy for Lync Web Services
if i just want to do reverse proxy for internet based clients. then i need to follow the "Using a single BIG-IP LTM as a reverse proxy for Lync Web Services" chapter. it makes two remarks about what you be turned on / off
1) Yes to "Would you like to create a BIG-IP virtual server to act as a reverse proxy for Lync external web services?"
2) No to "Are you deploying a reverse proxy as part of your Edge topology?"
well 2 is a bit unclear for me as you first need to enable either the front end or director server part. but does that mean you have to also enable fill in and use that front end / director server part? because if i understand the situation and the further text in the chapter fine then it is just a matter of replacing the single IP from the "What is the port 443 virtual server IP address that forwards traffic to the Front End Servers? " question into the front end server IPs. can't imagine i need all the further front end or director server part.
marvn_58503Nimbostratus
Short answer - If you aren't using the up-to-date iApp, grab it, as that actually separates out the Reverse Proxy section. It sounds like question 2 above reflects the older version where it insisted you had to deploy Edge External load balancing within the iApp first to dig through to the question.
Long answer - Lync reverse proxy works like this.
On your internal load balancer, if you have more than one FE/DIR you may be load balancing the pools. You should deploy your "internal reverse proxy interface" to point at these servers. If you do not use your load balancer on this, it doesn't matter.
On your external load balancer, you should find the section "Would you like to create a BIG-IP virtual server to act as a reverse proxy for external Lync web services?" and state yes. You can point this at your 4443 listener on your internal FE load balancer pool, or you can point it directly at your FE server if you just have the one.